Integration Synchronous Handler: No destination node can be determined for the request on node xxx (158,963)

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 destination node cannot be found.

For example:

In case of SES, you may get a error like:

Integration Synchronous Handler: No destination node can be determined for the request on node xxx (158,963) PT_SEARCH.SESIMPL.MESSAGE.SESRequest.OnExecute  Name:SendRequests  PCPC:1771  Statement:36
Called from:PT_SEARCH.SESIMPL.QueryService.OnExecute  Name:doServices  Statement:463
Called from:PT_SEARCH.SESIMPL.QueryService.OnExecute  Name:ExecuteQuery  Statement:28
Called from:PT_SEARCH.SESIMPL.Query.OnExecute  Name:Execute  Statement:39
Called from:HRS_SEARCH.SearchFramework.JobOpeningSearch.OnExecute  Name:BeginSearch  Statement:60
Called from:HRS_JOB_OPNG_SRCH.Activate  Statement:48

After applying filters for sender specified routing, node transactions, relationship transactions and the PeopleCode event OnRouteSend, a destination node cannot be found.

You may see an error in the appserver log for integration broker issues.

Integration Synchronous Handler: No destination node can be determined for the request on node XXXX. (158,963) DU_IMAGE_NOW.ImageNowAccess.OnExecute Name:ImageNowAccess PCPC:2659 Statement:46
Called from:DU_IMAGE_NOW.ImageNowDocData.OnExecute Name:ImageNowDocData Statement:5
Called from:DU_AD_APPL_LOOKUP.GBL.PostBuild Statement:7

Resolution:

Though the error could be vague and may not make sense, however, it does provide a hint: After applying filters for sender specified routing, node transactions, relationship transactions and the PeopleCode event OnRouteSend, a destination node cannot be found.

If it is a straightaway integration broker issue and you know the service operation name, you can open that service operation and make sure that the target node is active as well as all the routings are active. In case you do not know the service operation name, you can do a trace to find out the service operation getting invoked.

In case of SES, there are 2 services involved: Both these services have the same target node: WSDL_NODE. Most likely cause of this error is that the node may be inactive because of which all the routings would be inactive. Just make sure that all of them are active.

Try the action again and your issue should get resolved.