May
22
2012
22
2012
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)
—————-
Activity:
While performing SQL server upgrade to SP4, it got successful for database engine but failed for client components with above error description
—————-
Analysis:
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, http://support.microsoft.com/kb/940971
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, http://social.msdn.microsoft.com/forums/en-US/sqlsetupandupgrade/thread/16aa4ae8-c921-4a50-bfef-1dd91a785667 ,
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 http://support.microsoft.com/kb/205069 and http://support.microsoft.com/kb/916926, 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, http://blogs.msdn.com/b/distributedservices/archive/2009/04/01/instructions-to-reinstall-the-microsoft-distributed-transaction-coordinator-msdtc-service.aspxand 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,

Related Posts
Leave a comment
Subscribe to this blog via Email
Old Posts
- November 2017 (3)
- October 2017 (4)
- September 2017 (2)
- May 2017 (1)
- April 2017 (1)
- July 2016 (3)
- May 2016 (1)
- April 2016 (1)
- February 2016 (2)
- January 2016 (1)
- October 2015 (1)
- September 2015 (1)
- August 2015 (1)
- July 2015 (2)
- June 2015 (3)
- April 2015 (1)
- March 2015 (1)
- December 2014 (1)
- September 2014 (2)
- April 2014 (1)
- January 2014 (3)
- October 2013 (2)
- September 2013 (2)
- August 2013 (4)
- July 2013 (1)
- June 2013 (2)
- May 2013 (5)
- April 2013 (3)
- March 2013 (1)
- February 2013 (9)
- January 2013 (11)
- December 2012 (14)
- November 2012 (3)
- October 2012 (4)
- July 2012 (2)
- June 2012 (3)
- May 2012 (2)
- April 2012 (8)
- March 2012 (6)
- February 2012 (3)
- January 2012 (1)
- December 2011 (5)
- November 2011 (8)
- October 2011 (5)
- September 2011 (3)
- August 2011 (3)
- July 2011 (3)
- May 2011 (1)
- November 2010 (1)
Tags
80040e31
ACO5422E
agent not starting
AWE
cache
cluster
connection
datacollector
error
failure
lock pages in memory
maintenance plan
Maintenance plan error
microsoft
Migration
MSDTC
OLEDB error
outlook
RAM
Replication
Script
SQL2000
SQL agent
SQL login
sql server
SQLServer
SQL Server 2000
SQL Server 2005
SQL Server 2005 SP2
SQL Server 2008
SQLServer2008
SQL Server 2008 R2
SQL Server 2012
SQL Server Denali
t-sql
tdp sql v5.5.1
tdp v5.5.1
timeout error
tips
tivoli
Tivoli Data Protection
transactional replication
upgrade
Windows
x64
Calender
M | T | W | T | F | S | S |
---|---|---|---|---|---|---|
« Nov | ||||||
1 | 2 | 3 | 4 | 5 | 6 | 7 |
8 | 9 | 10 | 11 | 12 | 13 | 14 |
15 | 16 | 17 | 18 | 19 | 20 | 21 |
22 | 23 | 24 | 25 | 26 | 27 | 28 |
View Post by Categories
Recent Articles
- Setting up Always ON Availability Group in Multi Subnet Cluster – Recommendations
- Configuring Replication with Always ON Availability Group
- Login failed for user ‘DOMAIN\COMPUTER$’. Reason: Could not find a login matching the name provided. [CLIENT: ]
- Modern Servicing Model (Service Pack and Cumulative Updates) for SQL Server 2017 and onwards
- Fix: SSMS 2012 opening Debug window when pressing F5