1:
Unable to Ping a Node
Possible cause:
1. the web server for the Gateway is down.
2. The Gateway is not configured properly.
3. The application server for the node is down.
4. The Gateway URL is incorrect; verify that the URL is correct.
5. Copy URL in browser address; you should see: \\
1. the web server for the Gateway is down.
2. The Gateway is not configured properly.
3. The application server for the node is down.
4. The Gateway URL is incorrect; verify that the URL is correct.
5. Copy URL in browser address; you should see: \\
2:
Message Instance stays in NEW status.
Possible cause:
1. the pub/sub servers are not booted.
2. The Item is not at the top of the queue. All messages with the same Channel/ Subchannel are in the same queue
3. Run appmsgpurgeall.dms
4. Restart PUBSUB processes
5. Force clean-up from the monitor message -> domain status
6. Test your message by routing it through another channel to make sure that it is not an issue with the channel.
Possible cause:
1. the pub/sub servers are not booted.
2. The Item is not at the top of the queue. All messages with the same Channel/ Subchannel are in the same queue
3. Run appmsgpurgeall.dms
4. Restart PUBSUB processes
5. Force clean-up from the monitor message -> domain status
6. Test your message by routing it through another channel to make sure that it is not an issue with the channel.
3:
Message Instance stays in WORKING status.
Possible cause:
1. Message Handler has crashed.
2. The Message Handler processing the message is on another machine, and either the machine or the application server domain is down. The Message handler working on the message is "blocked". The service will timeout, and the Message Dispatcher will retry the message.
Possible cause:
1. Message Handler has crashed.
2. The Message Handler processing the message is on another machine, and either the machine or the application server domain is down. The Message handler working on the message is "blocked". The service will timeout, and the Message Dispatcher will retry the message.
4: Cannot find message in Message Monitor
Possible causes:
1. User does not have security for the message channel.
2. The message monitor criteria have filtered out the message.
5: Messages are being processed in an incorrect order
Possible cause:
1. The Channel has been partitioned, and the resulting sub channels do not match what was assumed for the ordering of the messages.
6: Message Instance not created
possible cause:
1. Message is inactive.
Possible causes:
1. User does not have security for the message channel.
2. The message monitor criteria have filtered out the message.
5: Messages are being processed in an incorrect order
Possible cause:
1. The Channel has been partitioned, and the resulting sub channels do not match what was assumed for the ordering of the messages.
6: Message Instance not created
possible cause:
1. Message is inactive.
7:
Publication Contract not created
possible cause:
1. Channel routing rules not set up properly.
possible cause:
1. Channel routing rules not set up properly.
8: Publication Contract stays in NEW status
possible cause:
1. Message Channel paused.
2. Node paused
3. Previous message had a status of RETRY, ERROR, or TIMEOUT.
4. The Publication Contract is not at the top of the queue. All Publication Contracts with the same Channel/ Subchannel and subscribing node are in the same queue
possible cause:
1. Message Channel paused.
2. Node paused
3. Previous message had a status of RETRY, ERROR, or TIMEOUT.
4. The Publication Contract is not at the top of the queue. All Publication Contracts with the same Channel/ Subchannel and subscribing node are in the same queue
9:
Publication Contract stays in WORKING status
possible cause:
1. The publication handler processing the contract is on another machine and either the machine or the domain is down. Processing should continue when the pub/sub system on the other machine comes back up.
10: Subscription Contract not created.
Possible causes:
1. Message Subscription is inactive.
2. Channel routing rules not set up properly.
possible cause:
1. The publication handler processing the contract is on another machine and either the machine or the domain is down. Processing should continue when the pub/sub system on the other machine comes back up.
10: Subscription Contract not created.
Possible causes:
1. Message Subscription is inactive.
2. Channel routing rules not set up properly.
11:
Subscription Contract stays in NEW status.
Possible causes:
1. Message Channel Node or System paused.
2. Message Definition not Active.
3. Previous message had a status of RETRY, ERROR, or TIMEOUT.
4. The Subscription contract is not at the top of the queue. All Subscription Contracts with the same Channel/ Subchannel and subscription owner are in the same queue.
12: All publication Contracts remain in a NEW status.
The queue was blocked from a Publication Contact that was in a status of ERROR from two weeks prior. User did not see the error on the message monitor because he was only looking at today. User entered xx day in and the ERROR publication appeared. Cancelled the error and all subsequent publication contracts processed successfully.
Problem: Subscription Contract stays in STARTED status.
Possible causes:
1. The Subscription Handler has crashed or has been brought down.
13: Subscription Contract stays in WORKING status.
Possible causes:
1. The Subscription Handler has crashed or has been brought down. Check in Application Messaging Gateway Administrator
2. Also look for any errors in App Serv Log
14: Subscription Contract in ERROR status.
Possible causes:
1. Subscription PeopleCode errors
2. Application data errors.
15: Subscription Contract in TIMEOUT status.
Possible causes:
1. Subscription PeopleCode errors
2. If the message works sometimes, and sometimes does not this may be a problem with the application server configuration.
Possible causes:
1. Message Channel Node or System paused.
2. Message Definition not Active.
3. Previous message had a status of RETRY, ERROR, or TIMEOUT.
4. The Subscription contract is not at the top of the queue. All Subscription Contracts with the same Channel/ Subchannel and subscription owner are in the same queue.
12: All publication Contracts remain in a NEW status.
The queue was blocked from a Publication Contact that was in a status of ERROR from two weeks prior. User did not see the error on the message monitor because he was only looking at today. User entered xx day in and the ERROR publication appeared. Cancelled the error and all subsequent publication contracts processed successfully.
Problem: Subscription Contract stays in STARTED status.
Possible causes:
1. The Subscription Handler has crashed or has been brought down.
13: Subscription Contract stays in WORKING status.
Possible causes:
1. The Subscription Handler has crashed or has been brought down. Check in Application Messaging Gateway Administrator
2. Also look for any errors in App Serv Log
14: Subscription Contract in ERROR status.
Possible causes:
1. Subscription PeopleCode errors
2. Application data errors.
15: Subscription Contract in TIMEOUT status.
Possible causes:
1. Subscription PeopleCode errors
2. If the message works sometimes, and sometimes does not this may be a problem with the application server configuration.
16:
"Access denied. Target and source message node password's do not
match." message even when no passwords are defined on target and source
nodes.
Possible cause:
1. Target application server has entry in Distinguished Name field in source node's message properties.
2. Target URL must be defined with https:// on target node in source application server.
Possible cause:
1. Target application server has entry in Distinguished Name field in source node's message properties.
2. Target URL must be defined with https:// on target node in source application server.
17:
Unable to ping a node.
Possible causes:
1. The web server for the Gateway is down.
2. The Gateway is not configured properly.
3. The app server for the node is down.
4. Verify url is correct. Copy url in browser address, should see "PeopleSoft <tools release> Application Messaging gateway".
Possible causes:
1. The web server for the Gateway is down.
2. The Gateway is not configured properly.
3. The app server for the node is down.
4. Verify url is correct. Copy url in browser address, should see "PeopleSoft <tools release> Application Messaging gateway".
