Got the following error when posting to a BizTalk receive location from SOAP-UI, but could have happened with any type of receive location:
<pre> HTTP/1.1 500 Internal Server Error Content-Type: application/xml; charset=utf-8 Server: Microsoft-IIS/8.5 X-Powered-By: ASP.NET Date: Thu, 05 Jul 2018 14:07:37 GMT Content-Length: 2384 <Fault xmlns="http://schemas.microsoft.com/ws/2005/05/envelope/none"><Code><Value>Receiver</Value><Subcode> <Value xmlns:a="http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher"> a:InternalServiceFault</Value></Subcode></Code><Reason><Text xml:lang="en-US"> There was a failure executing the receive pipeline: "MyPipeline, etc... Version=18.104.22.168, Culture=neutral, PublicKeyToken=1234123412341234" Source: "XML disassembler" Receive Port: "rpFrontEnd_TLRGLoadTenderOut_Web" URI: "/TLRG/Shipment/DirectTender.svc" Reason: Finding the document specification by message type "http://myNamespace#MyRootNode" failed. Verify the schema deployed properly. </Text></Reason><Detail><ExceptionDetail </pre>
This was a conversion from old 2010 system to 2013. On the first pass, I had forgotten a map that trimmed all the fields and removed empty nodes. The map used XSLT, and in the XSLT source, it had the wrong namespace from the old system.
Remember MessageType = NameSpace#Root
- Make sure the schema is really deployed (BizTalk Admin console)
- Check your spelling carefully, look for typos.
- If you have a map in the receive location, make sure the map is really running. I.e. does the messageType of the incoming message match the map. If the map doesn’t match, the incoming message will be passed on and could get this error.
- If you have a map, make sure the map has been tested and outputs the correct messageType.
- If you are doing JSON to xml (or any other file format to XML, make sure the pipeline is creating the correct messageType.
- Of course, make sure you restarted your Host Instances
- Check your values in BizTalk Admin before and after each deploy. If you are doing some kind of automated deploy, make sure your bindings for that deploy are current; they maybe resetting some value each time you deploy. In my case, I had a script to export the bindings, but I was actually running a similar script for another project. So everytime I reset the namespace value for the RootNodeNamespace in the JSON pipeline, it was getting reset on each re-deploy.