This post was originally published here

Error Message:

The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on
the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.

The Messaging engine failed to process a message submitted by adapter:WCF-BasicHttp Source
URL:/ExposeOrchWCFService/ExposeOrchWCFService_ProcessPO_prtRcvPO.svc. Details:The published message could not be routed because no subscribers were found. This error occurs if the subscribing orchestration or send port has not been enlisted, or if some of the message properties necessary for subscription evaluation have not been promoted. Please use the Biztalk Administration console to troubleshoot this failure.

Resolution:

Receive Port ID for the tight coupled orchestration with the Receive port is different that the one which was created by WCF Service publising wizard. You need to change Receive Port configuration to Direct.

https://social.msdn.microsoft.com/Forums/en-US/97de9430-89c3-4512-a016-1ee30d92fd20/published-message-could-not-be-routed?forum=biztalkgeneral

https://social.msdn.microsoft.com/Forums/en-US/e1441f35-ef5d-49dc-8173-43b34e2bacac/biztalk-server-errorthe-messaging-
engine-failed-to-process-a-message-submitted-by?forum=biztalkgeneral

Advertisements