SQL Server Performance Forum – Threads Archive

Win2003 and SQL Server 2000 Clustering Errors

Hi all- We are running into some installation troubles when trying to set up SQL Server 2000 on Windows 2003. We have followed the KB articles posted on this board (including the one about Terminal Services). Some questions I have are: – Is MSDTC a requirement to install SQL Server 2000 clustered? I have read varying opinions on this. – When we go through a local install and try to upgrade to a virtual, or do a virtual from the beginning with one or two nodes, we encounter an error saying that the installer "couldn’t create cluster specific entries". Has anyone seen this before? Are we missing something else for Windows 2003 and SQL Server 2000? Thanks so much in advance!

All Microsoft documentation I red MSDTC is neccesary.
About second question: if there other error in event viewer?
Luis Martin
Moderator
SQL-Server-Performance.com The views expressed here are those of the author and no one else. There are no warranties as to the reliability or accuracy of anything presented here.

Do you mean the error "Cluster specific registry entries couldn’t be written"? 1.
Make sure the remote registry service is running both nodes during install. This was my problem when I got this error. 2.
Be sure to use an account that is administrator on both nodes when installing. 3.
Check that you don’t have a security group policy being pushed out from the domain controller limiting your access rights on the servers. 4.
Apply SP3a before clustering or you can not cluster SQL on Windows 2003 5.
Check:
PRB: Installation of a Named Instance of SQL Server 2000 Virtual Server on a Windows 2003-Based Cluster Fails
http://support.microsoft.com/default.aspx?scid=kb;EN-US;815431 6.
About MSDTC see:
http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=3919

Thanks so much for your responses. I appear to have it working now, but only after I did the following: Do you mean the error "Cluster specific registry entries couldn’t be written"? 1. Make sure the remote registry service is running both nodes during install. This was my problem when I got this error. Have verified that it’s running on both nodes. 2. Be sure to use an account that is administrator on both nodes when installing. We are using a domain admin account that is an administrator on both nodes. 3. Check that you don’t have a security group policy being pushed out from the domain controller limiting your access rights on the servers. I will double check on this, although I’m pretty sure we dont. 4. Apply SP3a before clustering or you can not cluster SQL on Windows 2003 We apply SP3a after doing our local install of SQL Server 2000. But when you run the upgrade to cluster, you run it from the original sql server 2000 cd. Is this a problem? 5. Check: PRB: Installation of a Named Instance of SQL Server 2000 Virtual Server on a Windows 2003-Based Cluster Fails http://support.microsoft.com/default.aspx?scid=kb;EN-US;815431</a> This is what I have done and it appears to be working (well kind of<img src=’/community/emoticons/emotion-5.gif’ alt=’

‘ />)…. Install SQL Server 2000, SP3a on one node. Upgrade both servers to virtual sql installation. The services were created under MSCS but the other server could not take ownership (received the couldn’t create registry error again). In eventvwr, it shows a couple warnings regarding performance monitor. Renamed the data location on the SAN logical drive, and went to the second server and did a default local install using the original data file path s

rogram filesmicrosoft sql server. After this, all services were able to be swung back and forth in MSCS with the exception of the Search Monitor. My question is: what is this used for and is it required? I had to delete it out.

I can’t really follow your aproach from your description. Why are you renaming data location paths? The Microsoft Search is used for the full text search engine in SQL Server. If you do not use full text search you do not need to install the service.

I finally got it. Even through the remote registry service was started, I had to change the Logon rights of the service and start it under the user who I was installing SQL with (domain user with local admin rights on both servers) Thanks for everyone’s help!

]]>