Monish Nagisetty's Space

Building connectivity on-premise, in the cloud and beyond

Two Way On Ramp Web Service with Direct binding

Troubles bubbles? Yes…I have encountered some issues with my recent biztalk solution.  The details are below.  I am investigating this further and I will post my findings once I have found the answer.

Win2k3 Std. Ed.
BizTalk Server 2006 Dev. Ed.
SQL Server 2005 Dev. Ed.
SOAP Adapter
ESB Guidance v0.8


I’ve got a loosely coupled web service endpoint that accepts a message of
type “” and returns a message of
type ““.  This WS endpoint is
tied to a BizTalk Request-Response receive location and uses the SOAP
adapter.  Just so you know this is a modified version of the ESB On Ramp
provided in the ESB Guidance.  The one in the guidance is one-way but this
one is two-way.

Any messages submitted into this WS endpoint are processed by the
ESBSetContext pipeline component and then submitted into the messagebox.  I
have got a Solicit-Response send port configured to subscribe to messages
based on certain criteria.  This send port uses the SQL adapter with stored
procedures to perform CRUD operations (Create, Read, Update, Delete).  The
send port has an outbound map set to transform the message to a SQL schema
(stored proc).  Also, the send port has a inbound map to take the output sql
schema back to a canonical schema.

1) I submit a message into the WS endpoint (using the ESBClient Tool). 
2) The message makes it through the WS endpoint and gets processed by
the ESBSetContext pipeline component.  The properties I expect to get promoted go
into the context and then the message gets submitted into the messagebox.
3) The message is picked up by my send port as expected.
4) The outbound map is executed which transforms the message into a SQL
schema message and a stored proc is called.
5) The stored proc returns the expected result and an inbound map is
executed to transform the result back to a canonical message.
6) THIS IS WHERE I HAVE THE PROBLEM.  I would expect that this message is
correlated back to the original WS thread and returned as a SOAP response. 

Why is the EPM (Endpoint Manager) not able to correlate the response?

Here is the error:

    1 <SOAP:Envelope xmlns:SOAP= SOAP:encodingStyle=>

    2     <SOAP:Body>

    3         <SOAP:Fault>

    4             <faultcode>Microsoft BizTalk Server Negative Acknowledgment </faultcode>

    5             <faultstring>

    6                 An error occurred while processing the message, refer to the

    7                 details section for more information

    8             </faultstring>

    9             <faultactor>/Microsoft.BizTalk.ESB.OnRampWSTwoWay/OnRampTwoWay.asmx</faultactor>

   10             <detail>

   11                 <ns0:NACK Type=NACK

   12                 xmlns:ns0=>

   13                     <NAckID>{F028A97D-097F-421D-B6AF-98E6FD422FA6}</NAckID>

   14                     <ErrorCode>0xc0c016b7</ErrorCode>

   15                     <ErrorCategory>0</ErrorCategory>

   16                     <ErrorDescription>

   17                         There is an error in XML document (1,

   18                         41).

   19                     </ErrorDescription>

   20                     <ErrorDetail>

   21                         <CIAssetDetailed

   22            xmlns=urn:Schemas-App-Company:PersonDetailed/v1>

   23                             was not

   24                             expected.

   25                     </ErrorDetail>

   26                 </ns0:NACK>

   27             </detail>

   28         </SOAP:Fault>

   29     </SOAP:Body>

   30 </SOAP:Envelope>


February 15, 2007 - Posted by | BizTalk |

No comments yet.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: