August 13, 2003 at 9:50 am
I am trying to set up an active/active SQL cluster on Win2k3. I have been able to fail the servers over to each other before I installed SQl. But once SQL is installed and I try failing on node over to the other the resources move over but SQL server, SQL Server Agent, and SQL Server Fulltext fail to start.
Does anybody have any ideas ?
August 13, 2003 at 11:44 am
Any error messages in application/system logs? Do you removed BUILTIN\Administrators login from SQL Server? Is the account which is used for setuping windows 2000 cluster be granted to access SQL Server?
August 14, 2003 at 9:04 am
Last week, when we installed SQL Server 2000 on Windows 2003, we got the same problem. Please look at the Microsoft web link below first.
http://support.microsoft.com/default.aspx?scid=kb;en-us;319349
But we didn't follow the doc. We just remove SQL Server, then make sure uncheck the Force Protocol Encryption option before you reinstall SQL. Hopefully can give you an idea to figure out your problem.
Ray
August 14, 2003 at 1:05 pm
I read that when SQL is installed on a cluster, even an active/active cluster you need to install each instance on both nodes I had not done that. So I uninstalled SQL off both nodes and tried to reinstall it properly. The following error is what I recieved...
cluster specific registry entries couldn't be written.
Does anybody have any suggestions to fix this ?
August 14, 2003 at 7:11 pm
it sounds like it might be a permissions issue. Are you using an administrator account on your domain to do the install?
Wes
August 15, 2003 at 4:52 am
See Knowledge Base Article 329329 - PRB: Windows Server 2003 Support for SQL Server 2000
Apparently SQL2K SP2 and before are not supported on WS2003, and on trying to install SQL2K you get a warning.
The workaround is to click OK to the warning message and immediately upgrade to SQL2K SP3 or later.
Tony Bater
Tony
August 15, 2003 at 7:19 am
There is a work around for SP2 and below which I have followed it allows me to install SQL if I am installing one one node only but not both. I have check permissions and they are fine (domain and local). The install never completes, giving me the above error.
August 15, 2003 at 12:53 pm
What's being reported in your sqlstp.log files on both nodes? They should be in %systemroot% (usually C:\WINNT or C:\WINDOWS).
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
K. Brian Kelley
@kbriankelley
August 18, 2003 at 1:41 pm
Here is the relevent data that I found in the file sqlstp.log...
13:43:28 End Action : Run setup on cluster nodes
13:43:28 SetClusterSecuritySQL (CONNECTBUILDER\clusterservice) and (CONNECTBUILDER\clusterservice) returned: 0
13:43:28 Begin Action : CreateVirtualServerResources
13:43:56 End Action : CreateVirtualServerResources
13:51:31 An error occurred while creating virtual server resources for clustering.Cluster specific registry entries couldn't be written.K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
September 1, 2004 at 7:18 am
Hi,
I also got the same error as,
22:10:58 Begin Action : CreateVirtualServerResources
22:11:22 End Action : CreateVirtualServerResources
22:43:28 An error occurred while creating virtual server resources for clustering.Cluster specific registry entries couldn't be written.
September 2, 2004 at 3:15 am
Finally, I got the solution.
http://support.microsoft.com/default.aspx?scid=kb;en-us;872931
You may receive the "Cluster specific registry entries couldn't be written" error message when you try to install a virtual instance of SQL Server 2000 on the cluster nodes that are running Windows Server 2003
Resolution:
To resolve this problem, you must make sure that the Winreg subkey is configured with the correct permissions on all the nodes that are participating in the failover cluster. To do this, follow these steps on each node that is participating in the failover cluster:
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
HKEY_LOCAL_MACHINE\SYSTEM\CurentControlSet\Control\SecurePipeServers\Winreg
It may also be possibly occurring due to the permissions to the following registry keys, ensure that the following keys have full control permissions for the account that you are using to run SQL Server setup under. It requires full control as the setup will add entries to this key during setup:
HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply