July 24, 2007 at 4:41 pm
Hi, I've just moved the master database to a new disk. After that I changed the startup parameters to point to those new files. It worked perfectly, but at the time of changing those parameters in the failover server (it's clustered) using the command line I couldn't make it. So after several failovers something really weird happened: SQL Server says it can't find the master.mdf file... But what it is really strange: SQLServr.exe was completely corrupted in one of the servers (the one I changed first), being 0Kb long!!! Now I have both servers well configured (I made it with regedit) and I have tried to point back to the previous disk, but it says the same. I've looked also at the effective permissions for the service user, at the locks over the files, read only, etc... No result... I have a backup, but I don't know how to rebuild it since I can't start SQL Server even with -T3607
Hope someone can help me. Thanks in advance.
July 26, 2007 at 6:41 pm
Could you failover your nodes? If not, your cluster is broken. You may have to rebuild your cluster.
July 27, 2007 at 12:36 am
I can failover the nodes, but SQL Server won't work.
July 27, 2007 at 1:37 am
You need to do a fresh installation and rebuild the cluster.
Minaz
"More Green More Oxygen !! Plant a tree today"
July 27, 2007 at 2:51 am
Ok, thanks. I think it's a registry entries issue.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply