BizTalk server writes error messages to the application log. Common error messages and their meanings are listed below.
The Messaging engine failed to process a message submitted by adapter:FILE Source URL:c:\DynamicSOAPAPI\In\*.xml. 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. Use the Biztalk Administration console to troubleshoot this failure.
Cause: This error can be very confusing as there are at least a couple of different reasons this message can appear in application log. One reason can be the ports are not connected to each other so after receive port has picked up the file, there is no one to forward it to. Refer to Connect the Ports to Receive Messages. Another reason can be that the message format in the input file is different from the message format of the receiver.
The adapter failed to transmit message going to send port "WcfSendPort_DynamicSOAPAPIService_DynamicSOAPAPIPort" with URL "http://es094:8080/ecosys/api/soap11/DynamicSOAPAPI/". It will be retransmitted after the retry interval specified for this Send Port. Details:"System.ServiceModel.Security.MessageSecurityException: The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'BASIC realm="EcoSys Web Service API"'. ---> System.Net.WebException: The remote server returned an error: (401) Unauthorized.
Cause: This appears as an error in the application logs. The most likely reason for this is that service request is not providing credentials for Basic HTTP Authentication. Refer to Configuring Authentication to make sure it is configured correctly. It has been seen that configuration does not save correctly first time so make sure its configured correctly.