Hi,

I have a simple orchestration which seems to have gone pear shaped today.
Fortunately it is just a test system.

An orchestration is triggered via a file drop which in turn calls a stored
procedure using the SQL Adapter. The orchestration then puts the results of
the stored procedure in another file location.

When I drop a file everything seems to work fine, but if I check the event
log I see that there is a suspended message even though the new output file
has been created. If I trace the database using SQL Profiler I see that the
stored procedure has actually been called twice. I then have to restart the
BizTalk host in order to run it again.

Has anybody experienced this type of thing before?

Cheers,
Gary

[ Post a follow-up to this message ]

Hello Gary,

Try and start the SubscriptionViewer from the sdk.

See how many subscriptions you have for the given document.

Perhaps, you have serveral different orchestrations, endports etc. subscribi
ng
for the same document ?
The subscription viewer will tell you.

Best regards
Michael Høtoft


> Hi,
>
> I have a simple orchestration which seems to have gone pear shaped
> today. Fortunately it is just a test system.
>
> An orchestration is triggered via a file drop which in turn calls a
> stored procedure using the SQL Adapter. The orchestration then puts
> the results of the stored procedure in another file location.
>
> When I drop a file everything seems to work fine, but if I check the
> event log I see that there is a suspended message even though the new
> output file has been created. If I trace the database using SQL
> Profiler I see that the stored procedure has actually been called
> twice. I then have to restart the BizTalk host in order to run it
> again.
>
> Has anybody experienced this type of thing before?
>
> Cheers,
> Gary

[ Post a follow-up to this message ]

Hi Michael,

Thanks for that. I have checked and only have one subscription for the
message type. I think I may have problems with my set up as all sorts of
weird and wonderful things are happening, i.e. HAT crashing as timeouts are
occurring on the message box database, hosts not stopping properly etc.

As it is a development box I think a rebuild is in order.

Thanks again,
Gary

"Michael Høtoft" wrote:

> Hello Gary,
>
> Try and start the SubscriptionViewer from the sdk.
>
> See how many subscriptions you have for the given document.
>
> Perhaps, you have serveral different orchestrations, endports etc. subscri
bing
> for the same document ?
> The subscription viewer will tell you.
>
> Best regards
> Michael Høtoft
>
> 
>
>
>

[ Post a follow-up to this message ]