Error when transform message to envelope RRS feed

  • Question

  • Hi

    I have one MySQL database from where I collect some data (customers). I send this message to an orchestration, then by using a map I transform it to an envelope schema and then I continue to process further.

    I had the idea to put the map in the receive port. So the envelope schema would be the output of the receive port and the input to the orchestration.

    But when I pass the input message through the map in receive port, I get the following error :

    A message received by adapter "ODBC" on receive location "RcvL_PSP_Customers_ODBC" with URI "ODBC://{CALL ExtractNewCustomers}/" is suspended.
     Error details: The Messaging Engine failed while executing the inbound map for the message coming from source URL:"ODBC://{CALL ExtractNewCustomers}/" with the Message Type "http://CRL.ERP.BizTalk.MasterData.Schemas/PSPCustomers#PSPCustomers". Details:"Document type "" does not match any of the given schemas. " 

    The CRL_InsertLocalizedCustomer is the schema which is used in the envelope.

    I cannot understand how is possible the map to work inside the orchestration and not in the receive port.

    Shall I configure the receive location somehow? any ideas?

    Friday, April 13, 2018 10:40 AM

All replies

  • Does the suspended message validate against the schema in Visual Studio?

    Can you check if you have duplicate schemas deployed for the messagetype -

    Thanks Arindam

    Friday, April 13, 2018 10:58 AM
  • I schema validates and there is only one schema definition.

    I created one orchestration with only this map and there was no problem. I got the envelope correctly.

    But when I put the map in a reeive or send port then I get this error.

    It seems as if Biztalk handles schemas differently if they are inside orchesrtations.

    Friday, April 13, 2018 3:24 PM
  • Hi Chgian,

    What BizTalk version you are on? Can you share the screen of ODBC adapter properties screen shot?


    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.

    Friday, April 13, 2018 4:07 PM
  • Can you check this as well-

    If you have duplicate schemas deployed for the messagetype -

    Thanks Arindam

    Saturday, April 14, 2018 7:11 AM
  • Looks like some misconfiguration in the envelope vs document

    Receive Location detects document as having a target namespace of 

    But the Map created expects another messagetype

    Check if the envelope gets removed from the document
    Have one receive location for stripping the envelope (no mapping)
    A send port wich have a subscription filter for the receive port (no mapping)
    Enable the send port but do not start it, you can examine document and context properties

    You can also enable message body tracking and check your message flow this way

    hth /Peter

    Sunday, April 15, 2018 3:45 PM
  • This is what I thought but I have the same problem even if I put the map in a send port. Never mind, I use orchestration, I will put the map in it.
    Friday, April 20, 2018 3:49 PM