I'm using BizTalk 2004 SP1.
I have created an orchestration which consumes web service. Both send
and receive shapes are wrapped by scope which catches SoapException.
When the web service returns error message the BizTalkServer crashes.
Error message in system log:" The BizTalk Service BizTalk Group :
BizTalkServerApplication service terminated unexpectedly..."

Actually, the web service is a stored procedure exposed as a web
service by SQLXML. The message returned by the service is:


<SOAP-ENV:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:sqltypes="http://schemas.microsoft.com/SQLServer/2001/12/SOAP/types"
xmlns:sqlmessage="http://schemas.microsoft.com/SQLServer/2001/12/SOAP/types/
SqlMessage"
xmlns:sqlresultstream="http://schemas.microsoft.com/SQLServer/2001/12/SOAP/t
ypes/SqlResultStream">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Client</faultcode>
<faultstring>Runtime errors.</faultstring>
<detail>
<sqlresultstream:SqlMessage xsi:type="sqlmessage:SqlMessage"
sqltypes:IsNested="false">
<sqlmessage:Class>16</sqlmessage:Class>
<sqlmessage:LineNumber>11</sqlmessage:LineNumber>
<sqlmessage:Message>There is no data in the
issue</sqlmessage:Message>
<sqlmessage:Number>50001</sqlmessage:Number>
<sqlmessage:Procedure>btImportIssueXML</sqlmessage:Procedure>
<sqlmessage:Server>PAVDEEV</sqlmessage:Server>
<sqlmessage:Source>Microsoft OLE DB Provider for SQL
Server</sqlmessage:Source>
<sqlmessage:State>1</sqlmessage:State>
</sqlresultstream:SqlMessage>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>


Any ideas how to avoid the termination?
Thank you in advance.

[ Post a follow-up to this message ]

Phil,

Did you install SQLExpress on your machine?. If not you just repair the
Biztalk 2004 Installation.

Cheers,
Tamilselvan Subramanian,
Integration Analyst,
IBM Global Services India Ltd

"Phil" wrote:

> I'm using BizTalk 2004 SP1.
> I have created an orchestration which consumes web service. Both send
> and receive shapes are wrapped by scope which catches SoapException.
> When the web service returns error message the BizTalkServer crashes.
> Error message in system log:" The BizTalk Service BizTalk Group :
> BizTalkServerApplication service terminated unexpectedly..."
>
> Actually, the web service is a stored procedure exposed as a web
> service by SQLXML. The message returned by the service is:
>
>
> <SOAP-ENV:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:sqltypes="http://schemas.microsoft.com/SQLServer/2001/12/SOAP/types"
> xmlns:sqlmessage="http://schemas.microsoft.com/SQLServer/2001/12/SOAP/type
s/SqlMessage"
> xmlns:sqlresultstream="http://schemas.microsoft.com/SQLServer/2001/12/SOAP
/types/SqlResultStream">
> 	<SOAP-ENV:Body>
> 		<SOAP-ENV:Fault>
> 			<faultcode>SOAP-ENV:Client</faultcode>
> 			<faultstring>Runtime errors.</faultstring>
> 			<detail>
> 				<sqlresultstream:SqlMessage xsi:type="sqlmessage:SqlMessage"
> sqltypes:IsNested="false">
> 					<sqlmessage:Class>16</sqlmessage:Class>
> 					<sqlmessage:LineNumber>11</sqlmessage:LineNumber>
> 					<sqlmessage:Message>There is no data in the
> issue</sqlmessage:Message>
> 					<sqlmessage:Number>50001</sqlmessage:Number>
> 					<sqlmessage:Procedure>btImportIssueXML</sqlmessage:Procedure>
> 					<sqlmessage:Server>PAVDEEV</sqlmessage:Server>
> 					<sqlmessage:Source>Microsoft OLE DB Provider for SQL
> Server</sqlmessage:Source>
> 					<sqlmessage:State>1</sqlmessage:State>
> 				</sqlresultstream:SqlMessage>
> 			</detail>
> 		</SOAP-ENV:Fault>
> 	</SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
>
> Any ideas how to avoid the termination?
> Thank you in advance.
>
>

[ Post a follow-up to this message ]

Thank you for reply Selvan.

I have installed and already removed SQL 2005 developer beta 2.
Unfortunately, repair of BizTalk 2004 installation and reinstall of
BizTalk SP1 doesn't help.

When I run the same orchestration on another machine BizTalk doesn't
crash.

BTW
Why BizTalk reports errors when it receives SOAP fault message. Web
service just returns a business error which should be caught and
reported in orchestration. I don't want any messages to be suspended
in pipeline in this case. Is it possible to avoid this?

[ Post a follow-up to this message ]