How to apply SP4 on a newly added node in SQL Server 2000 cluster   Leave a comment

Oh yes! SQL 2000 is aging out yet there are several organizations still using it. And so.. I also get to work on some SQL 2000 issues 🙂 I am writing this blog after seeing some similar questions on forums like this one

Assume, I have a SQL Server 2000 clustered instance installed on two nodes. Now, either

i. I added a third node and installed SQL on it such that it becomes part of the existing two node SQL cluster.


ii. My cluster remains a two node cluster however one of the nodes has some issues. Sysadmin rebuilt the OS, I then install SQL on it.

In either of the scenarios mentioned above, the common thing is – Other nodes already have SP4 applied on it. I need to apply SP4 on a new node which is currently on the RTM build. I am listing down the steps (and gotchas) to achieve this without needing a failover. SP4 will be applied on the passive node in binary-only mode.

1. Log into the newly added node (make sure it is not the active node) where SP4 has to be applied.

2. Save the following contents in a file with extension .reg (say filename is need_sp_key.reg)

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Need_Sp_Key]


Note: Replace Virtual_Server_Name and Instance_Name with the Virtual Server Name and Instance Name of SQL Server, respectively.

3. Right click on the file need_sp_key.reg  and choose Merge to add the entry into the registry.

4. Run SP4 setup on this newly added node (Passive node).

5. Once SP4 completes successfully, delete the registry hive added in step -2

Common errors and their resolution

Here are some of the common errors and their resolution one might encounter during installation:

1. While running the setup, you may encounter an error like below at the screen where we need to provide service account credentials :

Setup cannot verify/grant logon as service right to the SQL Server  service logon account: 5000 (0x1388)


To resolve this, download the hotfix which basically contains an upgraded version of sqlsui.dll (build 2151). Once you extract the ghotfix to obtain sqlsui.dll, replace it with the existing one usually located at C:\Program Files\Microsoft SQL Server\80\Tools\Binn\

2. If SP4 installation silently fails, check the log file %windir%\sqlsp.log to match the following error messages:

16:13:56 Setup is performing required operations on cluster nodes.  This may take a few minutes...
16:13:56  "C:\DOCUME~1\FFSMIS~1\LOCALS~1\Temp\SqlSetup\Bin\remsetup.exe" C:\WINNT\remsetup.ini
16:43:56 Process Exit Code: (1460) This operation returned because the timeout period expired.
16:43:56 Begin Action : GetRemsetupRetCode
16:43:56 Installation return status on FFSMISBETA : -1
16:43:56 End Action : GetRemsetupRetCode
#### SQL Server Remote Setup - Start Time 07/18/12 16:13:56 ####


If you find the same error message as listed above, follow these steps to resolve the issue:

  • Start, run, secpol.msc
  • Navigate to Local Policies\Security Options\Unsigned non-driver installation behaviour
  • Change this to Silently succeed
  • Choose Security Settings at the top of the tree.
  • Select Action – Reload
  • Test by attempting an install that previously did not succeed.


3. Upon successful completion of SP4, when you try to failover the group it may throw error as below :

Cluster Administrator
An error occurred attempting to move the '<YourClusterGroup>' group:
A cluster node is not available for this operation.
Error ID: 5005 (0000138d).


To resolve this error, go to Cluster Administrator and make sure all the resources including cluster group has both nodes listed as the possible owner.

4. When you try to Add the Cluster Nodes as possible owner to the Full text resource, you may NOT see the Secondary Node in the list. To resolve this issue register the below 2 dlls as per the KB811024

regsvr32 “%windir%\cluster\gathercl.dll” /u

regsvr32 “%windir%\cluster\gathercl.dll”

5. After the RTM setup succeeds on the new node and if you are failing over the SQL Group to the newly added/rebuilt passive node, you may encounter the following error:

“The cluster resource cannot be brought online. The owner node cannot run this resource”


To address the error, copy C:\Program Files\Microsoft SQL Server\ MSSQL\Binn\ssnetlib.dll from Active Node to Passive Node

Hope this helps. Stay tuned for some more cool tips..

Leave a Comment

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: