Error :The Messaging Engine failed while executing the inbound map for the message coming from source while using custom functoid

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Error :The Messaging Engine failed while executing the inbound map for the message coming from source while using custom functoid

Viewing 1 reply thread
  • Author
    Posts
    • September 5, 2008 at 12:00 AM #20596
      community-content

        hi,

        i have developed a custom functoid , it works fine when i test the map but when i deploy the solution and try to use the application it’s generating the error below

        A message received by adapter “FILE” on receive location “SampleReceiveLocation” with URI “C:\POCs\Custom.Biztalk.EncryptionFunctoid\SampleApp\IN\*.xml” is suspended.
         Error details: The Messaging Engine failed while executing the inbound map for the message coming from source URL:”C:\POCs\Custom.Biztalk.EncryptionFunctoid\SampleApp\IN\*.xml” with the Message Type “http://SampleApp.Sample#Sample“. Details:”Function ‘ScriptNS1:EncryptData()’ has failed.” 
         MessageId:  {F7BC5CD8-3556-4BE2-BC03-76D574894A74}
         InstanceID: {035B587E-4076-41CC-AEEA-3413A4D00608}

        can any one help me on this issue.

      • September 5, 2008 at 5:25 AM #20604
        community-content

          Are you sure you are using the same input file while testing in Visual Studio vs BizTalk?  Is the file maybe getting updated in a pipeline so it is different when it hits your map?  It might help to debug the XSLT in VS: 

          1. In Visual Studio, validate the map.
          2. Open the output XSLT file (don’t CTRL click, copy and past the location into File -> Open so it will open in the XML editor instead of browser).
          3. Now a new XML menu will appear on the top menu.
          4. Click XML -> Debug XSLT.
          5. You will receive a warning that there is no input file.  Click OK and choose an input file.

          Now you can step through the XSLT just like you were stepping through a C# file.  When an exception occurs, you will be able to see the actual exception details, intead of a masked exception like you would get from Test Map or in a BizTalk app.

          • September 7, 2008 at 11:42 PM #20625
            community-content

               

              hi,

              i tried by debugging the xsl it is generating the error

              Cannot find the script or external object that implements prefix ‘http://schemas.microsoft.com/BizTalk/2003/ScriptNS0’.

              but the custom dll is present in the GAC, i even tried re-deploying the assembly.

               

              • September 8, 2008 at 7:38 AM #20629
                community-content

                  Did you copy the functoid DLL to the functoids folder (C:\Program Files\Microsoft BizTalk Server 2006\Developer Tools\Mapper Extensions)? Other things you can try are:

                  • Reference the custom functoid project from the map project (not sure if this is needed, but it shouldn’t hurt)
                  • Make sure the functoid is in the toolbox
                  • Restart things (VS, BizTalk host instance, BizTalk admin console, Windows)
                  Installing the functoid is a lot of pain and suffering, huh?  It doesn’t get much installing it on other servers either.  I always try to avoid custom functoids when possible.  A scripting functoid that calls an external assembly is usually a good alternative.

          • Author
            Posts
          Viewing 1 reply thread
          • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.