Article ID: 940971 - Last Review: August 25, 2009 - Revision: 3.0
An error message is logged in the Summary.txt file when a SQL Server 2005 service pack, cumulative update or cluster hotfix installation fails: "The Transaction Manager is not available"
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
When you install a Microsoft SQL Server 2005 service pack, cumulative update, or cluster hotfix, the installation fails. When this problem occurs, an error message that resembles the following is logged in the Summary.txt file:
Machine : ServerName Product : Client Components Error : Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server\90\NotificationServices\9.0.242\Bin\microsoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2146233087 Error message: Unknown error 0x80131501 Error description: The Transaction Manager is not available. (Exception from HRESULT: 0x8004D01B)
Note The Summary.txt file is located under the following folder:
Additionally, an error message that resembles the following is logged in the SQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log file:
MSI (s) (9C!38) [17:51:18:649]: Product: Microsoft SQL Server 2005 Tools -- Error 29549. Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server\90\NotificationServices\9.0.242\Bin\microsoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2146233087 Error message: Unknown error 0x8013150 Error description: The Transaction Manager is not available. (Exception from HRESULT: 0x8004D01B) Error 29549. Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server\90\NotificationServices\9.0.242\Bin\microsoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2146233087 Error message: Unknown error 0x8013150 Error description: The Transaction Manager is not available. (Exception from HRESULT: 0x8004D01B)
Note The SQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log file is located under the following folder:
Use one of the following methods, as appropriate for your situation.
Method 1
Make sure that the MS DTC service runs under the NT AUTHORITY\NetworkService account. To do this, follow these steps:
In Control Panel, double-click Component Services.
Under Console Root, expand Component Services, and then expand Computers.
If you are using Windows Server 2008 or Windows Vista, follow these steps:
Expand My Computer, and then expand Distributed Transaction Coordinator.
Right-click Local DTC, and then click Properties.
Note If the MS DTC service runs as a cluster resource, right-click the default MS DTC resource, and then click Properties.
In the Properties dialog box, click the Security tab.
In the Account box under DTC Logon Account, type NT AUTHORITY\NetworkService.
If you are using Windows Server 2003 or Windows XP, follow these steps:
Right-click My Computer, and then click Properties.
In the My Computer Properties dialog box, click the MSDTC tab.
Click Security Configuration.
In the Security Configuration dialog box, in the Account box under DTC Logon Account, type NT AUTHORITY\NetworkService.
Click to select the Network DTC Access check box, and then click to select the following check boxes:
Allow Remote Clients
Allow Remote Administration
Allow Inbound
Allow Outbound
Enable Transaction Internet Protocol (TIP) Transactions
Enable XA Transactions
For more information about these check boxes and about how to enable network access securely for the MS DTC service, visit the following Microsoft TechNet Web site:
Click OK again when you are prompted to restart the MS DTC service.
If the MS DTC service runs as a cluster resource, fail the cluster group that contains the MS DTC service over to each node. After the failover, changes that you made in the previous steps are automatically applied to each node.
Method 2
When the setup is installing components on Node 2, move the Cluster group that contains the MSDTC resource to Node 2.
When the setup is installing components on Node 1, move the Cluster group that contains the MSDTC resource to Node 1.
Make sure that the COM+ subsystem is in a healthy state on the node on which the failure occurred. To do this, follow these steps:
Click Start, click Run, type dcomcnfg in the Open box, and then click OK. The Component Services dialog box should open.
Expand all the nodes in the navigation pane. The COM+ System Application service uses the DTC service to populate these nodes. If you can expand all the nodes, the DTC service is working fine.
As the final verification step, in the Component Services dialog box, right-click COM+ Applications, click New Application, and then click Create Empty Application. Click Next to step through the wizard. If you can create a new Test COM+ application, the COM+ System Application service and the DTC service are working together
Then, move the cluster group back and forth between the two nodes to make sure that there are no problems going online on either of the cluster nodes.
After your tests are finished, remove the COM+ application that you created for testing.
Try to apply the SQL Server 2005 service pack, cumulative update, or cluster hotfix.
For more information about how to modify the default MS DTC resource in Windows Vista or in Windows Server 2008, visit the following Microsoft TechNet Web site:
Back to the top
