Error message on installing SQL Server 2005 service pack, hotfix, or cumulative update: “The Transaction Manager is not available”

Error Description from SUMMARY.txt file of service pack upgrade :
Machine : < ;server_name>;
Product : Client Components
Error : MSP 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 0x80131501
Error description: The Transaction Manager is not available. (Exception from HRESULT: 0x8004D01B)
Other errors logged in Windows Event logs:
System Log Error:
7024: The Distributed Transaction Coordinator (MS DTC) service terminated with service specific error 3221229584 (0xC0001010).
Application Log Errors:
4111: The MS DTC service is stopping.
4163: MS DTC log file not found. After ensuring that all Resource Managers coordinated by MS DTC have no in-doubt transactions, please run msdtc –resetlog to create the log file
4185: MS DTC Transaction Manager start failed. Loginit error 0x3.
2445: DTC Security Configuration values (OFF = 0 and ON = 1): Network Administration of Transactions = 0, Network Clients = 0, Inbound Distributed Transactions using Native MSDTC Protocol = 0, Outbound Distributed transactions using Native MSDTC Protocol = 0, Transaction Internet Protocol (TIP) = 0, XA Transactions = 0
4112: Could not start the MS DTC Transaction Manager.
System Details:
SQL Server 2005 SP2 (Ent. Ed. 32 bit) on Windows 2003 SP2 (Ent. Ed. 32 bit)
While performing SQL server upgrade to SP4, it got successful for database engine but failed for client components with above error description
At first glance the error reflected that there is issue with transactional manager i.e. MSDTC and found a relevant KB article to fix the issue,
This article talk about configuring DTC component on server, but when we tried, it didn’t worked out.
On further searching came across various forums which talks about the failure and it is due to Net Framework 2.0 , pfb the details, ,
This forum suggested to repair Net Framework 2.0, or install Net Framework 2.0 SP1 or go for better Net Framework 3.5 as it includes all features of 2.0. But after repairing and installing 3.5 framework as well it didn’t worked out. Although someone suggested to uninstall and reinstall dot net components but I didn’t do that due to certain restrictions and hence I searched further for other windows event id’s error related solution.
Further on investigation for error “Event ID: 7024 – The Microsoft Distributed Transaction Service Does Not Start and Error 3221229584”, got a reference KB article and, it talks about how to configure and reset MSDTC log, i.e. using command, msdtc.exe -resetlog
But on doing it also, it was throwing following error,
Event ID: 4135
Description: Failed to create/reset the MS DTC log file.
Verification done by me: On checking log file location, found it at correct place i.e. %windir%system32Msdtc
For your easy reference, Log file location of MSDTC,
On Windows 2000 and below: %windir%system32DTCLog
On Windows 2003 and above: %windir%system32Msdtc
Final Solution which was left for me is to reinstall MSDTC using following article, uninstall/reinstall .net 2 component.
Now, I am left with reinstall approach, i.e. first try for dot net components and if not work out then MSDTC, will update this post once I get any success 🙂 if no updates then assume no success. If in case you have any alternate solution then do leave comment, I will try to implement same.
Other useful references:
For fixing such issues on cluster environment,
Check Information of all Event log numbers,
Managing MTS transactions (details of DTS working, etc)
MSDTC log file location and related details,
How to change location of MSDTC log file using various methods,
How to –>;
•Log on to node hosting DTC resource as an admin
•Run ‘dcomcnfg’
•Navigate to Component Services >; Computers >; My Computer in the MMC console
•Right-click “My Computer” and select “Properties”
•Change log size, but note that doing so will reset the log entirely and restart the DTC service after you’ve clicked ‘OK’ or ‘Apply’
Other references which helped in troubleshooting,
Download PDF

Related Posts

About the Author: Nitin Garg

Indian born, trekker, biker, photographer, lover of monsoons... I love to blog the topics I research and find useful for self or online community to save time and energy :) Everything you read on my blog is my own personal opinion!

Leave a comment

Subscribe to this blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 265 other subscribers

Translate this blog!



February 2021
« Nov    

View Post by Categories

%d bloggers like this: