in

jetlounge

the minty fresh blog that whitens your teeth!


Syndication


Error During Install of SQL Server 2005 : Transaction Manager is not available

by David Leibowitz | January 18, 2008 | Comments: 24

I was installing SQL Server 2005 with all the trimmings (including Notification Services) onto my WinXP Pro machine. During the install step for Notification Services I received a nasty error that looked exactly like this (only less blurry):


The text of the error message is:

Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server\90\NotificationServices\9.0.242\Bin\micosoft.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)


The error Seems to be from either a failed MSDTC installation or inability to start the service. To fix during setup (you don't need to cancel and restart), do the following:


1. Drop to a Command Prompt and execute:

msdtc -install

2. Go to Administrative Tools -> Services and start the Distributed Transaction Coordinator service
3. Click Retry to continue with the installation

del.ico.us digg this technorati BlinkList Furl reddit DotNetKicks google! live Facebook Stumble Upon Yahoo!



Comments

 

Vikas said:

Good solutions. It worked as you mentioned.

March 20, 2008 12:14 AM
 

Jeremy D said:

Thanks a lot for your help..it saved me from my boss

March 27, 2008 10:41 PM
 

huhfhhf said:

ghfhevfghvhf

May 23, 2008 11:03 AM
 

Patrick said:

Thanks a lot for this solution. It worked!

May 23, 2008 11:34 AM
 

Jeff Saxe said:

Thanks so much!! In my case, I was installing a SQL 2005 Cluster on top of MS Cluster Services on top of Windows 2003 Enterprise. There is actually an MSDN article to this effect, but basically you need to cluster MSDTC if you are going to install the workstation tools (Management Studio, for instance) on your servers in addition to just SQL Server itself. Fortunately all the hard work is done by the MS installers, if you start with Win2K3 Service Pack 2. Just follow the directions to use Add/Remove Programs to add the one checkbox item "Enable Network Access to MSDTC". Then it automagically adds the MSDTC resource into the Cluster Group you already had, checks all the checkboxes for inbound and outbound network transactions, and moves the MSDTC log to the quorum drive, all for you. Very nice.

Then go back and install Management Studio, and it works just fine.

Thanks again, David!

-- Jeff Saxe

Network Engineer, Blue Ridge InternetWorks

Charlottesville, VA

June 6, 2008 1:30 PM
 

ErisS said:

Thanks a million! Thought I was going to be at work late the day before a holiday!

July 3, 2008 3:31 PM
 

Chris said:

Very concise and accurate fix, thank you.

August 7, 2008 11:00 AM
 

Srinivas said:

That fixed my problem. Thank you very much for giving correct solution.

September 17, 2008 2:30 AM
 

Srinivas said:

That fixed the problem.

Thanks

September 17, 2008 2:31 AM
 

Prajith KC said:

Very good solution.Its Working

December 11, 2008 4:11 AM
 

Rahul K said:

Thanks a ton. this was my 2nd attempt and It worked

December 31, 2008 8:10 AM
 

Patrik said:

Thanks alot for the solution to this annoying problem!

January 7, 2009 7:38 AM
 

pavan said:

Cool.it resolved my issue.

Thanks

pavan

April 7, 2009 4:09 PM
 

pavan said:

Cool.it resolved my issue.

Thanks

pavan

April 7, 2009 4:09 PM
 

Swathi said:

Thanks. It resolved my issue

May 13, 2009 7:23 AM
 

Joo said:

Thanks for the post.  Worked like a charm.

May 19, 2009 6:30 PM
 

Penmoor said:

also applies to SP3 - good post!

Added this message to help the search engines find your tip

Microsoft SQL Server 2005 Service Pack 3 (KB955706)

Installation date: ‎22/‎05/‎2009 09:20

Installation status: Failed

Error details: Code 736D

Update type: Important

This service pack upgrades SQL Server 2005 to SQL Server 2005 Service Pack 3 (SP3). This service pack upgrades all SQL Server 2005 instances and all components installed by SQL Server 2005 Setup. This service pack upgrades all editions of SQL Server 2005 except Express Edition. You must use Microsoft SQL Server 2005 Express Edition (SQL Server Express) SP3 to upgrade instances of SQL Server Express to SP3. If you need additional installation options, you should download this service pack at the Microsoft Download Center. For more information, see Microsoft Knowledge Base article 955706.

More information:

http://support.microsoft.com/kb/955706">support.microsoft.com/.../955706

Help and Support:

http://support.microsoft.com

May 24, 2009 2:01 AM
 

Marco said:

Tank you!

good solution!

July 21, 2009 2:53 PM
 

Brad said:

I also had to do it twice, but it worked in the end.  I stopped the service before I ran the command and then started it again.

Thanks!

August 20, 2009 9:33 PM
 

Beast said:

Thanks for that, helped a load

September 9, 2009 6:10 AM
 

John Kirk said:

Just another note to say thanks - that solved my problem.

October 7, 2009 11:12 AM
 

jazsm said:

Great stuff !!! it worked for me too.  Thanks heaps.

October 28, 2009 2:23 AM
 

Ram said:

I am getting the same issue even i started the service u said.Please do the needful

November 26, 2009 10:21 PM
 

Ashutosh said:

Thanks ...... it worked for me as well

December 15, 2009 2:42 AM

Leave a Comment

(required)  
(optional)
(required)  
Add
Powered by Community Server (Non-Commercial Edition), by Telligent Systems