Hi there,

I have an orchestration that takes in a file and does some processing
with it. I am finding however that as soon as the orchestration picks
up the file, the BTSNTSvc.exe process immediately stops then restarts
automatically after a minute or so.

Everything used to work fine, but this is happening all the time now.
The processing takes place within an atomic scope, and I have built a
custom class for the xml document which implements ISerializable (tho'
I am not sure whether this is the cause of anything or not)

I am not sure what is going on and would appreciate any ideas/help if
possible.

Thanks,

danielle

[ Post a follow-up to this message ]

My two cents advice. Clear the Event log if it is full.
I had a simillar situation where BTS services starts and stops. Because in
my BTS project there is lot of event log writing and when it is full, the BT
S
services can not continue.

Thanks,
RR.


"danielle" wrote:

> Hi there,
>
> I have an orchestration that takes in a file and does some processing
> with it. I am finding however that as soon as the orchestration picks
> up the file, the BTSNTSvc.exe process immediately stops then restarts
> automatically after a minute or so.
>
> Everything used to work fine, but this is happening all the time now.
> The processing takes place within an atomic scope, and I have built a
> custom class for the xml document which implements ISerializable (tho'
> I am not sure whether this is the cause of anything or not)
>
> I am not sure what is going on and would appreciate any ideas/help if
> possible.
>
> Thanks,
>
> danielle
>
>

[ Post a follow-up to this message ]

Absolutely. That has got me on a few occasions. Best to configure the event
log so that it can never fill up by getting it to overwrite old events.

--
McGeeky
http://mcgeeky.blogspot.com


"RR" <RR@discussions.microsoft.com> wrote in message
news:367A4178-F1CA-40B0-A498-F77BD782DC22@microsoft.com...
> My two cents advice. Clear the Event log if it is full.
> I had a simillar situation where BTS services starts and stops. Because in
> my BTS project there is lot of event log writing and when it is full, the
BTS[vbcol=seagreen]
> services can not continue.
>
> Thanks,
> RR.
>
>
> "danielle" wrote:
> 

[ Post a follow-up to this message ]

does this happen even when the app log is configured to overwrite events as
needed when the maximum size is reached? were there any error messages that
you saw?

"RR" wrote:
[vbcol=seagreen]
> My two cents advice. Clear the Event log if it is full.
> I had a simillar situation where BTS services starts and stops. Because in
> my BTS project there is lot of event log writing and when it is full, the 
BTS
> services can not continue.
>
> Thanks,
> RR.
>
>
> "danielle" wrote:
> 

[ Post a follow-up to this message ]

Biztalker,

Our organizaztion policy defines "NOT  to over write the events as
needed" . If we configure to overwrite events then, I guess, there should be
bo problem.

Thanks,
RR


"biztalker" wrote:
[vbcol=seagreen]
> does this happen even when the app log is configured to overwrite events a
s
> needed when the maximum size is reached? were there any error messages tha
t
> you saw?
>
> "RR" wrote:
> 

[ Post a follow-up to this message ]

Hi,

Thanks for your responses. We figured out the problem. As part of
calling our .net class, we were assigning our custom principal to the
current thread and when it came to sending out the message, the service
stopped. We ended up keeping a copy of the principal BT entered the
class with, assigned our custom principal, then at the end of the .net
class processing, re-assigned the original principal back to the
current thread. The service happily stayed up after sending out the
message. Quite odd behaviour.

Hope this helps someone,

Danielle

[ Post a follow-up to this message ]

Hi Danielle,

I have a similiar situation where I do some processing, then instantiate
some objects (via COM Interop), do some processing against those objects,
then return back to the orch. More often than not, the BT Service stops then
restarts during this call. I may have the same situation as you experienced.
Could you explain your solution - reassign ing the principal? I'm not that
great with threading, etc - but I believe it's an issue with this COM Intero
p
object running under the BizTalk Parent process and often thought reassignin
g
this to a different thread might be a way to stabilize it. Any ideas?

Thanks for your post.

Dameon
--
Dameon


"danielle" wrote:

> Hi,
>
> Thanks for your responses. We figured out the problem. As part of
> calling our .net class, we were assigning our custom principal to the
> current thread and when it came to sending out the message, the service
> stopped. We ended up keeping a copy of the principal BT entered the
> class with, assigned our custom principal, then at the end of the .net
> class processing, re-assigned the original principal back to the
> current thread. The service happily stayed up after sending out the
> message. Quite odd behaviour.
>
> Hope this helps someone,
>
> Danielle
>
>

[ Post a follow-up to this message ]