In this article, I
will discuss some of the common issues and questions I receive about clustering
a SQL Server 2000 database and Windows 2000. This article will be update
periodically so you may not have to go through some of the grief that I had to.
Most of the se errors and warnings will appear in your Event Log as soon as you
add SQL Server to your Windows 2000 cluster. Some are SQL Server issues and
others are Windows.
Server ErrorNoRemapPipes
This first severe
error will present itself to you as soon as you cluster SQL Server in a Windows
2000 environment. It will appear in your Event Log as a server error and the
description will look like this:
The value named
NoRemapPipes in the server's Registry key LanmanServer\Parameters was
invalid. The value was ignored, and
processing continued.
This error can be
ignored event though it appears in your Event Log continuously.
Warning1355
This warning will
appear in your Application Log continuously:
SuperSocket info:
(SpnRegister) : Error 1355.
Whenever SQL Server
is installed on Windows 2000, it tries to register itself to the Active
Directory always. This error should be considered informational, not a warning.
If you receive this message, you should ignore it.
System Process - LostDelayed Write Data
One common error
that is an actual error is the delayed write error that will appear in your
System Log. If you receive one of these, your SQL Server may failover without
warning because the SQL Server node does not have access to a particular drive.
The error will look like this:.
System Process -
Lost Delayed-Write Data
The system was
attempting to transfer file data from buffers to \Device\Harddisk#\Partition#\.
The write operation failed, and only some of the data may have been written to
the file.
The error may
continue to complain about corrupt and unusable drives. This is common on
servers that do not have Service Pack 2 for Windows 2000 installed. Even if you
have installed Service Pack 2 for Windows 2000 before you have clustered, you
will need to reinstall after you have clustered. This is because the files and
DLL files for clustering will be pre-Service Pack 2 after clustering is
complete. For complete details about how to install Service Pack 2 in a
clustered environment see the following Microsoft article:
http://support.microsoft.com/support/kb/articles/Q174/7/99.ASP
How do I Remove SQL Serverfrom a Cluster?
One
thing you’ll notice after you install SQL Server in a clustered environment that
you cannot remove SQL Server by using the traditional method of Control Panel
under Add/Remove Programs. To remove SQL Server in a clustered environment, you
must first move the SQL Server node back to where it was setup, then place the
SQL Server CD in the server and perform a uninstall through the CD’s
setup.
