BizTalk Server Setup - Multi-box install and MSDTC lock-up

Author

Multi-box install and MSDTC lock-up

Nabeel Prior

2004-09-22, 9:55 pm

Hi,

I was called in to a client today to help resolve an installation
problem, and need some help in explaining to the client why the
system got to the state it got to.

The installation is for an environment with 1 SQL and 1 BTS machine,
in an AD domain. The multi-box installation instructions were
followed by the client, up to the point where the Domain Users and
Groups were required in the config framework. Up to this point,
Component Servics could be accessed, but once the config framework
was run with the current domain user as the user for the various
services etc, and error below occurred and the config failed.
Failed to deploy Biztalk System assembly "E:\Program Files\Microsoft
Biztalk Server 2004\Microsoft.Biztalk.GlobalPropertySchemas.dll".
Com+ was unable to talk to the Microsoft Distributed Transaction
Coordinator

Now, when trying to access Component Services (Administrative Tools -
> Component Services), the mmc never loads and the event log for
MSDTC Client gets the following error message every minute or so:
String message: INFORMATIONAL : CSO::Maintain_SSTATE_UP session
Failed ProcID=0xe4c Error =0x80000128 RpcStatus = 0 .

I tried a number of things to resolve this, but no joy. The other
strange thing is that if I try to uninstall / repair BizTalk, the
wizard lists all the affected applications, but when I click Next, it
hangs.

The resolution at this point is that the client will be formatting
the box and re-installing from scratch, making sure to use Domain
Users and Groups. My question, however, is how did MSDTC get locked
like that, and why could we not recover from it, do the Domain
accounts, and try again? For this client, this is quite serious, as
he now has doubt as to the stability of the main product, since the
setup in his mind is not stable.

Kind Regards,

Nabeel Prior

Nabeel Prior

2004-09-22, 9:55 pm

Forgot to mention that both boxes are Windows Server 2003 Enterprise
Kind Regards,

Nabeel Prior

2004/09/16 16:16:35
Nabeel Prior <nabeel@nospam.com> wrote in message
<uHF9Ff$mEHA.2096@TK2MSFTNGP15.phx.gbl>

> Hi,
>
> I was called in to a client today to help resolve an installation
> problem, and need some help in explaining to the client why the
> system got to the state it got to.
>
> The installation is for an environment with 1 SQL and 1 BTS machine,

> in an AD domain. The multi-box installation instructions were
> followed by the client, up to the point where the Domain Users and
> Groups were required in the config framework. Up to this point,
> Component Servics could be accessed, but once the config framework
> was run with the current domain user as the user for the various
> services etc, and error below occurred and the config failed.
> Failed to deploy Biztalk System assembly "E:\Program
Files\Microsoft
> Biztalk Server 2004\Microsoft.Biztalk.GlobalPropertySchemas.dll".
> Com+ was unable to talk to the Microsoft Distributed
Transaction
> Coordinator
>
> Now, when trying to access Component Services (Administrative Tools
-
> MSDTC Client gets the following error message every minute or so:
> String message: INFORMATIONAL : CSO::Maintain_SSTATE_UP session
> Failed ProcID=0xe4c Error =0x80000128 RpcStatus = 0 .
>
> I tried a number of things to resolve this, but no joy. The other
> strange thing is that if I try to uninstall / repair BizTalk, the
> wizard lists all the affected applications, but when I click Next,
it
> hangs.
>
> The resolution at this point is that the client will be formatting
> the box and re-installing from scratch, making sure to use Domain
> Users and Groups. My question, however, is how did MSDTC get
locked
> like that, and why could we not recover from it, do the Domain
> accounts, and try again? For this client, this is quite serious,
as
> he now has doubt as to the stability of the main product, since the

> setup in his mind is not stable.
>
>
>
> Kind Regards,
>
> Nabeel Prior

Mariusz Borsa [MSFT]

2004-09-22, 9:55 pm

Did you try troubleshooting suggested by BizTalk documentation (you have
downloaded the updates of it from Web, haven't you - here's the link:
http://go.microsoft.com/fwlink/?linkid=20616 )? Here's what it says on
WIn2k3erver multibox installations:

Multiple computer configuration using Windows Server 2003 or Windows XP
Problem: If you attempt to run the Configuration Wizard on Windows Server
2003, or Windows XP, and point to a remote SQL server, the configuration
will fail.

Resolution: You must enable network clients DTC access before configuring
BizTalk Server. This is required for the distributed transactions performed
by BizTalk Server components to work.

Important The following procedure must be run on each of the computers in
the multiple computer configuration.

To turn on DTC Access

From the Start menu, double-click Control Panel, double-click
Administrative Tools, and then double-click Component Services.
Expand Component Services, and then expand Computers.
Right-click the computer you need to set, and from the context menu select
Properties.
In the Properties window, select the MSDTC tab.
In the Transaction Configuration area, click Security Configuration.
In the Security Settings area, select the Network DTC Access check box.
In the Security Settings area, check the Network Clients check box.
Click OK on each open dialog box.
Restart your computer to enable the remote DTC option.

Warning This configuration could take up to 15 minutes.

----------------------------------------------------------------------------
----

Problem: If you are using Windows Server 2003 for both client and server
computers, in a multi-domain or workgroup deployment, and the remote
computer is a member of a different domain, you must turn off RPC security
or configuration fails.

Resolution: The following registry key must be created on SQL servers, SSO
master servers and anywhere else the BizTalk Engine is installed.

HKLM\Software\Microsoft\MSDTC\TurnOffRpc
Security = 1 (dword)

Hope this helps
Mariusz Borsa
This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team
--------------------
From: "Nabeel Prior" <nabeel@nospam.com>
Subject: Re: Multi-box install and MSDTC lock-up
> Hi,
>
> I was called in to a client today to help resolve an installation
> problem, and need some help in explaining to the client why the
> system got to the state it got to.
>
> The installation is for an environment with 1 SQL and 1 BTS machine,

> in an AD domain. The multi-box installation instructions were
> followed by the client, up to the point where the Domain Users and
> Groups were required in the config framework. Up to this point,
> Component Servics could be accessed, but once the config framework
> was run with the current domain user as the user for the various
> services etc, and error below occurred and the config failed.
> Failed to deploy Biztalk System assembly "E:\Program
Files\Microsoft
> Biztalk Server 2004\Microsoft.Biztalk.GlobalPropertySchemas.dll".
> Com+ was unable to talk to the Microsoft Distributed
Transaction
> Coordinator
>
> Now, when trying to access Component Services (Administrative Tools
-
> MSDTC Client gets the following error message every minute or so:
> String message: INFORMATIONAL : CSO::Maintain_SSTATE_UP session
> Failed ProcID=0xe4c Error =0x80000128 RpcStatus = 0 .
>
> I tried a number of things to resolve this, but no joy. The other
> strange thing is that if I try to uninstall / repair BizTalk, the
> wizard lists all the affected applications, but when I click Next,
it
> hangs.
>
> The resolution at this point is that the client will be formatting
> the box and re-installing from scratch, making sure to use Domain
> Users and Groups. My question, however, is how did MSDTC get
locked
> like that, and why could we not recover from it, do the Domain
> accounts, and try again? For this client, this is quite serious,
as
> he now has doubt as to the stability of the main product, since the

> setup in his mind is not stable.
>
>
>
> Kind Regards,
>
> Nabeel Prior

Nabeel Prior

2004-09-22, 9:55 pm

Thanks Mariusz,

I have read this documentation, and did try the suggestions, but the
problem was that the config had already failed because these things
were not followed by the client. They are now going to make sure
that they follow the guidline correctly. But the question I have is
why did Component Services and BTS remove / repair hang the way it
did, when before the config was run the Component Services worked
100%?

Kind Regards,

Nabeel Prior

2004/09/17 01:43:23
"Mariusz Borsa [MSFT]" <mborsa@online.microsoft.com> wrote in message
<YkKFwbEnEHA.3212@cpmsftngxa06.phx.gbl>

>
& #123;\rtf1\ansi\ansicpg1252\deff0\deflan
g1033{\fonttbl{\f0\fnil\fprq2\fcharset0
MS Sans Serif;}}
> \viewkind4\uc1\pard\f0\fs20 Did you try troubleshooting suggested
by BizTalk documentation (you have downloaded the updates of it from
Web, haven't you - here's the link: http://go.microsoft.
com/fwlink/?linkid=20616 )? Here's what it says on WIn2k3erver
multibox installations:
> \par
> \par Multiple computer configuration using Windows Server 2003 or
Windows XP
> \par Problem: If you attempt to run the Configuration Wizard on
Windows Server 2003, or Windows XP, and point to a remote SQL server,
the configuration will fail.
> \par
> \par Resolution: You must enable network clients DTC access before
configuring BizTalk Server. This is required for the distributed
transactions performed by BizTalk Server components to work.
> \par
> \par
> \par Important The following procedure must be run on each of the
computers in the multiple computer configuration.
> \par
> \par To turn on DTC Access
> \par
> \par From the Start menu, double-click Control Panel, double-click
Administrative Tools, and then double-click Component Services.
> \par Expand Component Services, and then expand Computers.
> \par Right-click the computer you need to set, and from the context
menu select Properties.
> \par In the Properties window, select the MSDTC tab.
> \par In the Transaction Configuration area, click Security
Configuration.
> \par In the Security Settings area, select the Network DTC Access
check box.
> \par In the Security Settings area, check the Network Clients check
box.
> \par Click OK on each open dialog box.
> \par Restart your computer to enable the remote DTC option.
> \par
> \par Warning This configuration could take up to 15 minutes.
> \par
> \par
> \par ---------------------------------------------------------------
-----------------
> \par
> \par Problem: If you are using Windows Server 2003 for both client
and server computers, in a multi-domain or workgroup deployment, and
the remote computer is a member of a different domain, you must turn
off RPC security or configuration fails.
> \par
> \par Resolution: The following registry key must be created on SQL
servers, SSO master servers and anywhere else the BizTalk Engine is
installed.
> \par
> \par HKLM\\Software\\Microsoft\\MSDTC\\TurnOf
fRpcSecurity = 1
(dword)
> \par
> \par
> \par
> \par Hope this helps
> \par Mariusz Borsa
> \par This posting is provided "AS IS" with no warranties, and
confers no rights.
> \par
> \par EBusiness Server Team
> \par \pard\li720 --------------------
> \par From: "Nabeel Prior" <nabeel@nospam.com>
> \par Subject: Re: Multi-box install and MSDTC lock-up
> \par > Hi,
> \par >
> \par > I was called in to a client today to help resolve an
installation
> \par > problem, and need some help in explaining to the client why
the
> \par > system got to the state it got to.
> \par >
> \par > The installation is for an environment with 1 SQL and 1 BTS
machine,
> \par
> \par > in an AD domain. The multi-box installation instructions
were
> \par > followed by the client, up to the point where the Domain
Users and
> \par > Groups were required in the config framework. Up to this
point,
> \par > Component Servics could be accessed, but once the config
framework
> \par > was run with the current domain user as the user for the
various
> \par > services etc, and error below occurred and the config failed.

> \par > Failed to deploy Biztalk System assembly "E:\\Program
> \par Files\\Microsoft
> \par > Biztalk Server 2004\\Microsoft.Biztalk.GlobalPropertySchemas.
dll".
> \par > Com+ was unable to talk to the Microsoft Distributed
> \par Transaction
> \par > Coordinator
> \par >
> \par > Now, when trying to access Component Services
(Administrative Tools
> \par -
> \par > > Component Services), the mmc never loads and the event log
for
> \par > MSDTC Client gets the following error message every minute
or so:
> \par > String message: INFORMATIONAL : CSO::Maintain_SSTATE_UP
session
> \par > Failed ProcID=0xe4c Error =0x80000128 RpcStatus = 0 .
> \par >
> \par > I tried a number of things to resolve this, but no joy. The
other
> \par > strange thing is that if I try to uninstall / repair BizTalk,
the
> \par > wizard lists all the affected applications, but when I click
Next,
> \par it
> \par > hangs.
> \par >
> \par > The resolution at this point is that the client will be
formatting
> \par > the box and re-installing from scratch, making sure to use
Domain
> \par > Users and Groups. My question, however, is how did MSDTC
get
> \par locked
> \par > like that, and why could we not recover from it, do the
Domain
> \par > accounts, and try again? For this client, this is quite
serious,
> \par as
> \par > he now has doubt as to the stability of the main product,
since the
> \par
> \par > setup in his mind is not stable.
> \par >
> \par >
> \par >
> \par > Kind Regards,
> \par >
> \par > Nabeel Prior
> \par \pard
> \par
> \par }