BizTalk Exception: This Assembler cannot retrieve a document specification using this type: "http://www.microsoft.com/biztalk/bank#BankQuoteRequest"

BizTalk Exception: This Assembler cannot retrieve a document specification using this type: "http://www.microsoft.com/biztalk/bank#BankQuoteRequest"

 

Exception Info:

Event Type:    Error

Event Source: XLANG/s

Event Category:      None

Event ID: 10034

Date:              2007-5-9

Time:             9:00:55

User:              N/A

Computer:      ---
Description:

Uncaught exception (see the 'inner exception' below) has suspended an instance of service 'LoanBroker.LoanBrokerProcess(2ac683b2-6047-28b7-74d1-2e05c31ae9ad)'.

The service instance will remain suspended until administratively resumed or terminated.

If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.

InstanceId: 77132f50-5516-4415-8f33-60e8ea40167f

Shape name:

ShapeId:

Exception thrown from: segment -1, progress -1

Inner exception: An error occurred while processing the message, refer to the details section for more information

Message ID: {AABCBDA2-8E2D-49A4-99BD-7E6526029040}

Instance ID: {1823B876-D36E-43DB-9EE8-147830E15EDC}

Error Description: There was a failure executing the send pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLTransmit, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "XML assembler" Send Port: "LoanBroker_1.0.0.0_LoanBroker.LoanBrokerProcess_Port_Bank1_d4d7d47079e1d5d2" URI: "http://localhost/bankservice/bank1.asmx" Reason: This Assembler cannot retrieve a document specification using this type: "http://www.microsoft.com/biztalk/bank#BankQuoteRequest". 

 

SOLUTION:

Basically, you are trying to send a message using the Xml pipeline on a send port and Biztalk does not know what schema to match it with.

 

This error occurs when your schema project is not deployed or you have two or more schemas deployed with the same message type (namespace # root node name).

 

If possible, you can use the passthrough pipeline. That would fix the problem. You could allow unrecognized message on the send port, or remove the same message type.