BizTalk: Document specification search failed

Question

Good afternoon everyone

I have a problem with BizTalk orchestration, which is really weird.

The first form of getting my orchestration failed with the following message:

There was a failure executing the receive pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines Source: "XML disassembler" Receive Port: "ReceiveCanonicalPort" Reason: Finding the document specification by message type "http://www.openapplications.org/oagis/9#ProcessInvoice" failed. Verify the schema deployed properly. 

I put together a test document with the first row of lines:

 <?xml version="1.0" encoding="utf-8"?> <ProcessInvoice xmlns="http://www.openapplications.org/oagis/9" releaseID="9.0" targetNamespace="http://www.openapplications.org/oagis/9" > 

I already checked:

I checked the scheme: Target namespace: "http://www.openapplications.org/oagis/9" The root of the node is "ProcessInvoice"

The circuit checks.

My input file validates the circuit.

I checked that the circuit is deployed.

I looked to see if there is another scheme with a duplicate namespace and root node.

I restarted the host instances and redeployed several times.

I tried setting the xass disassembler property "allow unrecognized message" to true. This results in an instance exception being thrown instead of the object. Which, it would seem, indicates that he is not de-serializing it.

I prayed to the great god Boogie.

Any other ideas?

thanks

Answer 1

You must have a different version of this circuit defined somewhere in another assembly.

Are you sure you checked all the possible applications (including BizTalk Application 1)?

The only thing I can think of is maybe you have a redirect assembly in a configuration file that is redirected to a version that does not exist, however I'm not sure that you will even get your observed behavior if that is the case.

Another thing - maybe the older version of the scheme is GAC'd, and the host instance still supports it. Try rebooting.

Hope this helps.