February 17, 2006 at 2:19 am
Hi,
I have been having a very strange problem with a new SQL Server install. I shall Start from the beggining
Installed SQL Server 2000 on top of a windows 2003 clustered system with 2 shared disks.
Started to split the system databases so i changed the -l startup parameter to change the location of the master database transaction log. Brought down the resource and brought it back up in cluster administrator and it failed. After a little trouble shooting i found that it had lost SQLArg in the registry. So i did the following
Started SQL Server from the command line specifying the the master data file and log manually it came up fine!! Then execute shutdown command
Entered the -l SQLArg into the registry and started the "Service" (not the resource in cluster admin) it came up fine!! Then execute shutdown command
Start the SQL Server resource in cluster admin it fails. You look in the registry and it has reverted all the SQL Entries.
I know this isnt "EXACTLY" a SQL Server issue and more of a clustering issue but has any body seen anything like this before?
Any information would be appreciated....
February 17, 2006 at 4:36 am
I have now fixed this.
The way round this is to bring down the cluster services on both nodes add the SQLArg registry entries back into both systems and bring the SQL Server resource back online.
This worked for me hope it helps anyone who has this problem in the future.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply