none
Biztalk Server error:The Messaging engine failed to process a message submitted by adapter:WCF-Custom Source RRS feed

  • Question

  • I am getting the below error, Any suggestion or link how to understand the root cause of this issue and how to fix it now or in future (if it happened again) is greatly appreciated.

    The Messaging engine failed to process a message submitted by adapter:WCF-Custom Source URL:mssql://LocalHost//TEST?. 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.

    At first this error message looks self explanatory, but I had no success afte trying many ways to troubleshoot this issue.

    My application is doing very basic thing (please see details below) and was working fine but suddenly I am getting this error.

    I am not sure why I am getting this error as clearly I have a send port which is subscribed to the received message. Also the send port is enlisted and in start mode. I restarted the Host Instance few time but no luck. I also recreated the application from scratch but still received the same error.

    Is there any way to know why it Biztalk Server is not able to recogonize the send port?

    My application picks a HL7 text file and insert the data from it to SQL table. I have the following configurations:

    1. One Receive Port - To pick text file using BTAHL7 receive pipeline

    2. One Receive Location tied to the port in #1

    3. One Send Port which is based on WCF SQL adapter, it has two more configurations:

    3a. Filter set to BTAHL7Schemas.MSH5_1 == TestReceive

    3b. Outbound Map set to Map1 where Map1 is  mapping between source schema "ADT_A04_231_GLO_DEF.xsd" and "TableOperation.dbo.Patient.xsd"


    • Edited by webtesP Tuesday, May 1, 2012 3:17 AM
    Tuesday, May 1, 2012 3:16 AM

Answers

  • Thanks for your responses. I was able to fix my issue by creating another send port which uses filter for http://...#InsertResponse.

    As after looking at the suspended message I saw mention of http://...#InsertResponse and hence got the clue from there.

    Wednesday, May 2, 2012 1:41 AM

All replies

  • check if BTAHL7Schemas.MSH5_1  is getting promoted.

    cant you filter based on messagetype or receive port?


    KiranMP

    Tuesday, May 1, 2012 9:50 AM
  • check if BTAHL7Schemas.MSH5_1  is getting promoted.

    cant you filter based on messagetype or receive port?


    KiranMP

    How do I check if BTAHL7Schemas.MSH5_1  is getting promoted?

    It was working all along using this filter but I can try to use different filter.

    Tuesday, May 1, 2012 11:30 AM
  • you can check message context of the suspended message to see if property is getting promoted.

    KiranMP

    Tuesday, May 1, 2012 12:08 PM
  • Try simplifying the send port filter to BTS.ReceivePortName = "<name of receive port>". If that works, your existing filter is the problem and the HL7 property isn't being promoted as you expected.
    Tuesday, May 1, 2012 12:35 PM
  • Thanks for your responses. I was able to fix my issue by creating another send port which uses filter for http://...#InsertResponse.

    As after looking at the suspended message I saw mention of http://...#InsertResponse and hence got the clue from there.

    Wednesday, May 2, 2012 1:41 AM