Publication Process Problems

Publication Process Problems
Possible publication process problems include:


Publication contract is not created.
Publication contract is in NEW status.
Publication contract stays in RETRY status.
Publication contract is in WORKING status.
Publication contract is in TIMEOUT status.
Publication contract is in ERROR status.
Pub Contract Is Not Created
No publication PeopleCode exists.
Publication PeopleCode is incorrect.
No outbound routings exists for the service operation.

Pub Contract Is in NEW Status
Sending queue is paused.
Publication Dispatcher crashed or was brought down.
Sending node is paused.
Previous service operation had a status of Retry, Error, or Timeout.
Sending domain is not active.
After an unsuccessful ping, a row may be added to the table PSNODESDOWN; which will hold up the message queue; query the table PSNODESDOWN.

Pub Contract Stays in RETRY Status
The remote node cannot be pinged successfully; the publication contract will be processed when the remote node comes back up.
No publication handler is available, either because it crashed or it was brought down.
Receiving Node URL is incorrect in integrationGateway.properties file.

Pub Contract Is in WORKING Status
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.
Single threading on the application server is slowing processing.

Pub Contract Is in TIMEOUT Status
An exception occurred on the target application server (look in APPSRV.LOG file for details); verify that:
The reply is incorrectly routed; check Gateway for correct machine address of target node.
Bad XML syntax.

Pub Contract Is in ERROR Status
Receiving node user profile not authorized to service operation.
Inbound routing is not set up on the receiving system.
Service operation is not active on the receiving system.
Service operation has not been granted security access on the receiving system.
The source node is not defined in the target database.
Handler PeopleCode is bad.
Remote application server is down.
Receiving Node is not defined in the integrationGateway.properties file.
Receiving PeopleSoft node has not been added to single signon.
Service operation version on target is not active.