Common PeopleSoft Integration Broker Issues–Part 5

Access denied. No password defined on source message node.

Possible cause:
 
In 8.1x Source Message Node properties has entries in 'Password' and 'Re- verify Password'.
Solution: Blank these fileds and ping the source node it worked fine.


Page cannot be displayed message when attempting to bring up Gateway or gateway Administration page. 
 
Possible cause:
 
3. Make sure Apache/ Jserv started.
4. Make sure aliases are correct in zone.properties

Ping failed, Application server log message saying cannot find JVM.

Resolution:  The application server was on a different machine as the web server.  The Sun JRE 1.2 was downloaded on the web server machine.  Sun JRE 1.2 was re-downloaded on the application server machine and the setting JavaVM Shared Library in psappsrv.cfg file was set to point to the location of this JRE.

All attempted publishing messages from PIA resulted in the following error message

Resolution:  When the upgrade was performed to the production database the following people tool tables had no data in them. 
PSAPMSGPUBINST  (channel names and latest pubid)
PSAPMSGPUBCSYNC (channel names and update timestamp)
PSAPMSGPUBSYNC (channel names and update timestamp)
PSAPMSGSUBCSYNC (channel names and update timestamp)


Additional Notes:

1. Problem: Message instance/Publication Contract sits in NEW status for over 15 minutes with no other messages in progress.
 
Possible Causes:
I. Incorrect Gateway URL defined on Message Node.
II. Message nodes not used in any of the messages should not contain an URL. 
Example:  PSFT_CR which does not have an URL defined.
Actions:  Check URL on Gateway and ping message node.

2. Problem: Publication Contract sits in NEW status status for over 15 minutes with no other messages in progress.
 
Possible Causes:
 
I. Publishing Application Server down.
II. Publishing Pub/Sub processes not configured on App Server domain.
III. Message Channel Paused.
IV. Incorrect Gateway URL defined on Message Node.
V. Node paused.
VI. Previous Message had errors or timed out.
VII. No Publication PeopleCode exists, or PeopleCode is incorrect.
Actions:  Check listed system components, then resubmit message.

3. Problem: Publication Contract sits in WORKING status for over 15 minutes with no other messages in progress.
 
Possible Causes:
 
I. Single threading on the application server is making things slow…if the Pub/Sub processes are running
II. Pub/Sub processes not responding
Actions:  Add more handlers and reboot app server.

4. Problem: Publication Contract is in TIMEOUT status
 
Possible Causes:
 
I. Subscribing Application Sever down.
II. Subscribing Node is Paused.
III. Message Node URL is incorrect.
IV. No Subscription PeopleCode exists on Subscribing system, or Subscription PeopleCode is incorrect.
Actions:  Check listed system components, then resubmit message.

5. Problem: Publication Contract is in ERROR status
 
Possible Causes:
I. Message Node URL is incorrect.
II. Subscription PeopleCode is bad.
Actions:  Check listed system components, if fix is made then resubmit message.  Otherwise go to Resolution of Messages in Error status section.

6. Problem: Publication Contract is in RETRY status
 
Possible Causes:
III. “PS” Password changed on Gateway
Actions:  Check  ~/Gateway.administration and apply password updates to PS ID.

Subscription Process

1. Problem: Subscription Contract sits in NEW status for over 15 minutes with no other messages in progress.
 
Possible Causes:
 
I. Application Server down.
II. Pub/Sub processes not configured on App Server domain.
III. Message definition not active.
IV. Message channel paused.
V. Node paused.
VI. Previous Message had errors or timed out.
VII. If you’re missing a row in PSAPMSGSUBPRCID, do the following:
insert into PSAPMSGSUBPRCID values(0)  [This should never happen]
Actions:  Check listed system components.  Reboot Pub/Sub services if necessary.

2. Problem: Subscription Contract sits in STARTED status status for over 15 minutes with no other messages in progress.
 
Possible Causes:
 
I. Subscription Handler down
Actions:  Check listed system components, then resubmit message.

3. Problem: Subscription Contract sits in WORKING status status for over 15 minutes with no other messages in progress.
 
Possible Causes:
 
I. No Subscription PeopleCode exists
II. Subscription Handler crashed while processing message.
Actions:  Check listed system components.   Reboot Pub/Sub services if necessary.

4.Problem: Subscription Contract in ERROR status
 
Possible Causes:
 
I. Subscription PeopleCode errors.
II. Application Data errors.
Actions:  First resubmit message.  If it fails then go to” Resolution of Messages in Error status” section (below.)

5. Problem: Subscription Contract is in EDIT status

Possible Causes:
I. Message was edited and has yet to be resubmitted for processing.
Actions:  Normally this status only applies when an error is being reconciled by support personnel.

6. Problem: Subscription Contract is in RETRY status

Possible Causes:
I. Subscription PeopleCode is empty.
Actions:  This applies when a message has been resubmitted.

7. Problem: What happens when your message is routed to Both  (Publish & Subscribe) and the message instance is DONE, but  no subscription contract is created?   
Possible Causes:
I. Check your message subscription properties to make sure that the Local Publication ‘Invoke for local publication’ is turned on.
Actions:  This should never happen.  Escalate to IS support.