Depending on the action you’re performing, you would see a bunch of messages in between the following two lines of error messages: Integration Synchronous Handler: No destination node can be determined for the request on node xxx (158,963) After applying filters for sender specified routing, node transactions, relationship transactions and the PeopleCode event OnRouteSend, a […]
Continue readingPeopleSoft Integration Broker has several settings, which you need to remember. Many a times when an issue remains unresolved for long, I end up thinking – this is such a trivial issue and still I’m unable to resolve it. What did I do the last time? I wrote a post on one such issue some […]
Continue readingA common error especially in PeopleTools 8.53 onwards is “PubConProccessor TransformSend Failed on service operation publication.” The issue happens for service operations, which involve transformation programs like PERSON_BASIC_SYNC, WORKFORCE_SYNC etc. The problem is commonly caused by either a a corrupted routing definition or sometimes by a PeopleTools bug when the routing definition contains 30 char […]
Continue readingRecently I came across an interesting issue where one of the PeopleSoft instancewas showing multiple status for a single PUBSUB enabled PeopleSoft instance. This in turn was causing the dispatcher status to remain inactive and updating or force reset or purge domain status and then reconfigure of the appserver domain did not help either. You […]
Continue readingPeopleSoft Integration Broker is tricky and sometimes when issues arise, it can take you a long time to resolve the issues unless you troubleshoot issues in a logical and systematic way. I will lay out the steps, which you should check. Following these steps will resolve your issue in 99% of the cases. I […]
Continue reading