Sei sulla pagina 1di 4

Integration Broker 8.

40 -- Troubleshooting Guide

Publication Process
Problem: Publication Contract not created Possible Cause: 1. No Publication PeopleCode exists or PeopleCode is incorrect. Check OnRouteSend PeopleCode event from the message definition. . !xplicit routing specified instead of "mplicit on Node definition. #. No outbound transactions specified on Remote Node defintion. $. Check the PSNO%!S%O&N table. 'ake sure there are no ro(s in it. Problem: Publication Contract sits in N!& status Possible Causes: 1. 'essage Channel is P)*S!% . Publication %ispatcher has crashed or has been brought do(n. #. Node is P)*S!% $. Previous message had a status of R!+R,- !RROR- or +"'!O*+. .. )fter unsuccessful P"N/- please 0uer1 to make sure that no ro( (as added to PSNO%!S%O&N2 other(ise it (ill hold up the message 0ueue. 3. "ncorrect /ate(a1 *R4 defined on 'essage Node. 7. See Solution "% 200778756 Integration Broker: Master Solution for Messages stuck in New status Problem: Publication Contract sta1s in R!+R, status Possible Causes: 1. +he remote node cannot be 5pinged6 successfull1. +he publication contract (ill be processed (hen the remote node comes back up. . No publication handler available- either because it7s crashed or it has been brought do(n

Problem: Publication Contract sits in &OR8"N/ status Possible Causes: 1. +he publication handler processing the contract is on another machine and either the machine or the domain is do(n. Processing should continue (hen the pub9sub s1stem on the other machine comes back up. . Single threading on the application server is making things slo(:if the Pub9Sub processes are running #. Publication ;andler has crashed- or been brought do(n. Problem: Publication Contract is in +"'!O*+ status Possible Causes: 1. +ransaction is not setup in the target node definition. Check )PPSR<.4O/ file for probable cause. . Subscribing Node is Paused. #. 'essage Node *R4 is incorrect. $. No Subscription PeopleCode exists on Subscribing s1stem- or Subscription PeopleCode is incorrect. PeopleSoft, Inc. Proprietary & Confidential Integration Broker 8.40 Trou le!"ooting #uide Page 1 of 4 01$0%$14 1%&4' (1$P1

.. )n exception occurred on the target application server =look in )PPSR<.4O/ file for details> verif1 the follo(ing: a. Source node defined in target database b. <erif1 correct pass(ord on node- target and source =if using pass(ords> c. 'essage or Channel not defined in target database d. "ncorrectl1 routed repl1. Check /ate(a1 for correct machine address of target node e. No target local node defined f. ?ad @'4 s1ntax Problem: Publication Contract is in !RROR status Possible Causes: 1. 'essage Node *R4 is incorrect. Check the Primar1 *R4 value on the remote node definition. . Subscription PeopleCode is bad.

ubscri!tion Process
Problem: Subscription Contract not created. Possible Causes: 1. 'essage Subscription is inactive. )ctivate from message definition. . +ransactions not set up properl1.

Problem: Subscription Contract sits in N!& status Possible Causes: 1. )pplication Server do(n. . Pub9Sub processes not configured on )pp Server domain. #. +he Subscription %ispatcher has crashed or has been brought do(n. $. 'essage definition not active. .. 'essage channel paused. 3. Node paused. A. Previous 'essage had errors or timed out. B. "f 1ou7re missing a ro( in PS)P'S/S*?PRC"%- do the follo(ing: insert into PSAPMSGSUBPRCID values(0) 9 If !essage is "u#lis$ing locall%& c$eck t$e 'enerate Su#scri"tion (rocess Instance c$eck#o) in t$e Su#scri"tion "ro"erties

Problem: Subscription Contract sits in S+)R+!% status Possible Causes: 1. Subscription ;andler do(n . "f there is a Component "nterface called in the Subscription PeopleCode- make sure the target component online is valid. Problem: Subscription Contract sits in &OR8"N/ status Possible Causes: 1. No Subscription PeopleCode exists . Subscription ;andler crashed (hile processing message.

PeopleSoft, Inc. Proprietary & Confidential Integration Broker 8.40 Trou le!"ooting #uide

Page ' of 4 01$0%$14 1%&4' (1$P1

Problem: Subscription Contract in !RROR status Possible Causes: 1. 'essage channel propert1 if COR%!R!%7 (ill allo( subscription contracts to go in random order. +his (ill cause D*44S,NC message to error out (hen the +ransaction (as subscribed before the ;eader. . Subscription PeopleCode errors. #. )pplication %ata errors. $. <erif1 autonumber se0uence

Problem: Subscription Contract is in !%"+ status Possible Cause: 1. 'essage (as edited and has 1et to be resubmitted for processing. Problem: Subscription Contract is in R!+R, status Possible Causes: 1. Subscription PeopleCode is empt1. . 'essage %efinition on target node is not active

"ther Possible Problems


Problem: Cannot find message in 'essage 'onitor Possible Causes: 1. *ser does not have securit1 for the message channel. Check Permission 4ists. . +he 'essage 'onitor criteria have filtered out the message. Problem: 'essages are being processed in an incorrect order Possible Cause: 1. +he Channel has been partitioned- and the resulting subchannels do not match (hat (as assumed for the ordering of the messages. . *norderd processing is activated in the Channel definition. Problem: 'essage "nstance not created Possible Cause: 1. 'essage is inactive. . %uplicate Pub"% on the publication database. Check appsrv.log for this error. Problem: 'essage "nstance sta1s in N!& status. Possible Causes: 1. +he )pplication server is do(n. . Pub9Sub services not configured on )pplication Server domain. #. +he 'essage %ispatcher has crashed or has been brought do(n. $. +he "tem is not at the top of the 0ueue. )ll messages (ith the same Channel9 Subchannel are in the same 0ueue .. Channel is paused.

PeopleSoft, Inc. Proprietary & Confidential Integration Broker 8.40 Trou le!"ooting #uide

Page ) of 4 01$0%$14 1%&4' (1$P1

Problem: 'essage "nstance sta1s in S+)R+!% status. Possible Causes: 1. )ll 'essage ;andlers have crashed or have been brought do(n. Processing (ill resume (hen 'essage handlers come brought back up . +he 'essage dispatcher processing the message is on another machine- and either the machine or the application server domain is do(n. Problem: 'essage "nstance sta1s in &OR8"N/ status. Possible Causes: 1. 'essage ?roker ;andler has crashed. . +he 'essage ;andler processing the message is on another machine- and either the machine or the application server domain is do(n. +he 'essage handler (orking on the message is 5blocked6. +he service (ill timeout- and the 'essage %ispatcher (ill retr1 the message. Problem: '1 Publish=> PeopleCode finishes successfull1- but there is no message in the 'essage 'onitor. Possible Causes: 1. +he 'essage %efinition is "n)ctive. Problem: *nable to ping a node. Possible Causes: 1. +he (eb server for the /ate(a1 is do(n. . +he /ate(a1 is not configured properl1. #. +he app server for the node is do(n. $. <erif1 *R4 is correct. Cop1 *R4 in bro(ser address- should see:

PeopleSoft Integration Gateway


PeopleSoft *i!tening Connector Statu!& (CTI+,

Problem: 'essage Channels delivered in P)*S!% status. )C+"ONER!)SON )"R4"N!E+8+ ?*%/!+EPOS"+"ON !@POR+ECO'P4")NC!EOR%!RES+)+*S 'C++S+ P),E)N%ER!'"+ P*RC;)S!ER!F*"S"+"ON F*)4"+,E%)+)ES*?'"+ F*)4"+,E%)+)E*P%)+! +R!!E')"N+ #i$: Change the status to CR*NN"N/7 in order for the messages to process from CN!&7 to C&OR8"N/7.

PeopleSoft, Inc. Proprietary & Confidential Integration Broker 8.40 Trou le!"ooting #uide

Page 4 of 4 01$0%$14 1%&4' (1$P1