I had an issue yesterday with SQL Server 2005 installation of the Notification services. The error that I was getting was:
- COM Plus Catalog Requirement (Warning)
Messages
COM Plus Catalog Requirement
If SQL Server Setup fails, Setup will roll back the installation but may not remove all .manifest files. The workaround is to rename the files and then rerun Setup. For more information, see How to: Work Around COM+ Check Failure in SQL Server Setup.
Well I did as the article said and this didn't help at all... in fact the install failed completely and I had to uninstall and start from scratch again. I gave MS tech support a call and we spent 3 and a half hours going through what it could be. It turned out the issue was with the MSDTC having been installed by SQL Server but not in it's entirity. In the end we put in the following command into command prompt:
msdtc - install
which installed the Distributed Transaction Coordinator service. This got us past that bit of the problem. The next error that I got was:
TITLE: Microsoft SQL Server 2005 Setup
------------------------------
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)
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=29549&EvtType=sqlca%5csqlassembly.cpp%40Do_sqlAssemblyRegSvcs%40Do_sqlAssemblyRegSvcs%40x80131501
Then we went into the services manager and started the service and hit the retry on the install (Silly us... we managed to install the Distributed Transaction Coordinator service but forgot to set it running!). This got us past that issue and SQL Server 2005 was installed.
Following that we had the common problem of Management Studio not being installed. This was a simpler problem to fix. We went into Control Panel, Add/ Remove programs and hit the change option on SQL Server 2005 and clicked on the url that says "To Install a new component, click here" Click it and select Workstation Components, books online and development tools and then click on advanced. Don't add in anything other than the client components (mandatory!) and the documentation, samples and sample database (optional). Click on next and install the components. You will now find that on completion you have Management Studio! (As if by magic!)
I hope this helps others who have the same issue. I didn't find any of the info above in any of the KB articles but I believe MS are supposed to be updating them with this solution I am sure they will provide a link to it once it has been updated. In the meantime best of luck with things. (I'm soooo glad we have support calls included in our MSDN subscription... otherwise I would have had to totally reinstall the OS and all the apps which would have taken far longer than 3 and a half hours!)
BTW all this started as a result of me installing SQL Everywhere (Beta) which removed the Visual Studio links in Server Explorer to SQL Mobile database implementations. After uninstall of SQL Everywhere (Beta) it doesn't restore the Server explorer links to SQL Mobile to integrate with Visual Studio! If you try uninstalling and reinstalling SQL Mobile this doesn't fix the problem nor does uninstalling just Visual Studio or just SQL Server. I had to totally uninstall SQL Server and Visual Studio to get it working with SQL Mobile. Be warned! (I suspect this uninstallation was what caused the issue with the Distributed Transaction Coordinator service as nothing else was installed or uninstalled at that time. It would be worth the SQL Everywhere team looking into this issue further as it may be that there is an underlying problem here. Please note I would be interested in looking at SQL Everywhere when the next version comes out either in Beta or RTM.)
Update: The KB article re the DTS is here but they don't relate it back to the SQL Server 2005 installation.
posted @ Thursday, August 03, 2006 9:12 PM