Re: SQL Server pulls incorrect instance data from the registry?
- From: "Anthony Thomas" <ALThomas@xxxxxxxxx>
- Date: Tue, 19 Jun 2007 16:26:21 -0500
At least one of them had to be a named instance or both. Sounds like the
system wasn't configured correctly to begin with.
However, if you are having disk problems, then there could have been
corruption in the QUORUM which may have corrupted the registry replication
process.
For default instances, the parameters are stored in
HKLM\SOFTWARE\Microsoft\MSSQLSERVER\MSSQL\Parameters.
For named instances, the parameters are stored in
HKLM\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL$NamedInstance\MSSQL\Parameters.
I would check all instances on all cluster nodes to make sure they are in
the current proper configuration. Then, run the Cluster Recovery tool to
checkpoint the configuration to make sure the QUORUM contains the proper
registry key information.
Sincerely,
Anthony Thomas
--
<brettestes@xxxxxxxxx> wrote in message
news:1180478382.927737.213590@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi guys,
I had a very odd error occur over the weekend in a development
environment, and I want to see if you've ever heard of this or had
this happen.
Environment:
Active-Active SQL Cluster on Windows 2000 Server, SP4
One instance is called DEV, the other UAT
SQL Server 2000 Enterprise Ed., version 8.0.2040
Both hit an older SAN that has had some I/O issues as of late
Basically, UAT failed over due to some disk issues on the SAN and gave
an error that stated that the ERRORLOG could not be opened because it
was in use by another process. I checked the UAT Startup Parameters
in the registry, and somehow, the -d, -l-, and -e parameters were set
to DEV? Once we took the UAT instance offline and changed the
registry settings, we were able to bring the instance back online.
However, I can't explain how UAT instance grabbed and updated the
registry with the DEV Startup Params.
Has anyone ever had an issue similar to this? How did you explain
it?
Thank you for any information you may provide.
--Brett
.
- Prev by Date: Re: Error 42d during Fail Over SQL 2000 Enterprise in a Server 2003 Ent. Cluster
- Next by Date: Re: Service Pack 2 : SP2 for SQL 2005 Fails on a clustered server node
- Previous by thread: Re: Error 42d during Fail Over SQL 2000 Enterprise in a Server 2003 Ent. Cluster
- Next by thread: Re: Max SAN time out
- Index(es):
Relevant Pages
|