Hi,

I'm using BizTalk Server 2006 Developer Edition and the Windows 2003 Server
operating system running on a Microsoft Virtual Server image. I have noticed
that when I try and start the BizTalk Server in-process host instance using
the BizTalk Admin Console, the service is shown as running but in fact it is
not. The Windows System Event log records the following events, approx 30
seconds apart:

Timeout (30000 milliseconds) waiting for a transaction response from the
BTSSvc$BizTalkServerApplication service.

After a while, say 5 minutes, the service does actually start.

Does anyone elsee know why this happens ?? I've used BizTalk 2004 before,
but this is the first time that i've used BizTalk 2006 and Virtual Server, s
o
i'm not sure which one is to blame here. Needless to say, it is very annoyin
g.

Mark.

[ Post a follow-up to this message ]

It seems that the timeout only occurs when I try and stop or start ther host
instance service when the BizTalk Application is not stopped. If I stop
everything, I never get the timeout. If everything is running, I always get
the timeout.

"Mark Abrams" wrote:

> Hi,
>
> I'm using BizTalk Server 2006 Developer Edition and the Windows 2003 Serve
r
> operating system running on a Microsoft Virtual Server image. I have notic
ed
> that when I try and start the BizTalk Server in-process host instance usin
g
> the BizTalk Admin Console, the service is shown as running but in fact it 
is
> not. The Windows System Event log records the following events, approx 30
> seconds apart:
>
> Timeout (30000 milliseconds) waiting for a transaction response from the
> BTSSvc$BizTalkServerApplication service.
>
> After a while, say 5 minutes, the service does actually start.
>
> Does anyone elsee know why this happens ?? I've used BizTalk 2004 before,
> but this is the first time that i've used BizTalk 2006 and Virtual Server,
 so
> i'm not sure which one is to blame here. Needless to say, it is very annoy
ing.
>
> Mark.

[ Post a follow-up to this message ]