Hi,

I'm connecting to a Web Service in order to get a message which I'm using in
my orchestration. I would like to know how BizTalk (soap adapter in
particular) handels the situation when the web service server is down. Is
this logged somewhere, for example in the application log? I need to know
that in order to build some error-handling procedure.

Greatfull for your answer,

theo

[ Post a follow-up to this message ]

You can program a retry, that might help you get less errors and then at the
end of a timeout.

The WS shouldnt fail the schedule if its not available, so you need to
compensate on your own. You have alot of flexibility on how to error handle
whether be it the event log, email et al.



"Theo" <Theo@discussions.microsoft.com> wrote in message
news:F386124E-6F3E-4C1F-A9A7-C4BF6468B5B8@microsoft.com...
> Hi,
>
> I'm connecting to a Web Service in order to get a message which I'm using
> in
> my orchestration. I would like to know how BizTalk (soap adapter in
> particular) handels the situation when the web service server is down. Is
> this logged somewhere, for example in the application log? I need to know
> that in order to build some error-handling procedure.
>
> Greatfull for your answer,
>
> theo

[ Post a follow-up to this message ]

If you have a retry in the SOAP send port that you are using to call the web
service, each time the web service is called, and fails, you will get a
warning in the event log of the machine that attempted the call (i.e. must
be running an instance of the host that the SOAP handler is running under).
When the retry schedule expires, you'll get an error logged in the event
log - so the event log should have a series of warnings, then an error for
each failure.

The orchestration will be dehydrated in between the retries, and suspended
(not resumable) once all retries have failed.

"BA" <biztalk.architect@gmail.com> wrote in message
news:1111576308. 58ee889b3d7a34a90e143e1b1b55de87@teranew
s...
>
> You can program a retry, that might help you get less errors and then at
the
> end of a timeout.
>
> The WS shouldnt fail the schedule if its not available, so you need to
> compensate on your own. You have alot of flexibility on how to error
handle
> whether be it the event log, email et al.
>
>
>
> "Theo" <Theo@discussions.microsoft.com> wrote in message
> news:F386124E-6F3E-4C1F-A9A7-C4BF6468B5B8@microsoft.com... 
using[vbcol=seagreen] 
Is[vbcol=seagreen] 
know[vbcol=seagreen] 
>
>

[ Post a follow-up to this message ]