Adding new node to SQL SP4 cluster

Hi all,
I'm trying to add a new node to our SQL Server 2000 SP4 cluster. Cluster
node is Windows 2003 SP1. I can add the node to the SQL cluster, but when I
try to add SP4 to the new node, I get an error message when I enter in the
service password for the instance.
Error message : Setup cannot verify/grant logon as service right to the SQL
Server service logon account: 5000 (0x1388)
However, this error didn't come up when I was adding the node to the SQL
cluster and it prompted me for the same password. We're running an
active/active configuration and I can't do anything with the other instance
(the default one) as it says that this instance is still waiting for the
service pack!
Any ideas anyone? Thanks in advance
Dave
Dave Wall
Dave,
It looks like a permission issue. Does the Windows domain a/c that you are using the setup have local admin privileges on both the cluster nodes? Try running the setup using the virtual SQL Server service a/c or the
cluster service a/c ?
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Dave,
Are you using the NEED_SP_KEY in the registry. If yes, then remove this key and re-run SP4 from the original node (i.e the node that is already on SP4 and owns the SQL resources) and see if this helps?
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Thanks Uttam,
removed the reg key and it all went through without any problems
Dave
Dave Wall
"Uttam Parui[MS]" wrote:

> Dave,
> Are you using the NEED_SP_KEY in the registry. If yes, then remove this key and re-run SP4 from the original node (i.e the node that is already on SP4 and owns the SQL resources) and see if this helps?
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
>
|||Dave,
Glad to hear that the issue is resolved. I appreciate your update.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Hello, I'm having the same problem, but I don't know what you mean by this
NEED_SP_KEY I can't find any information on it. If you could shed some light
on this I would greatly appreciate it!
--Gene
"Uttam Parui[MS]" <uttamkp@.online.microsoft.com> wrote in message
news:KA3IUo6kFHA.944@.TK2MSFTNGXA01.phx.gbl...
> Dave,
> Are you using the NEED_SP_KEY in the registry. If yes, then remove this
key and re-run SP4 from the original node (i.e the node that is already on
SP4 and owns the SQL resources) and see if this helps?
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
|||Depending on certain parameters, the Need_SP_Key is added to the new node by the setup process when the node is
added to the SQL failover cluster.
Check (on all nodes) if you have the following key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Need_SP_Key
If yes, then delete it. Then try to install the service pack 4 from the active node where SQL Server is currently running.
If no, then you might be having a different issue. Give more details for us to help you.
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way
to do this is to visit the following websites: http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Uttam Parui[MS] wrote:
> Dave,
> Are you using the NEED_SP_KEY in the registry. If yes, then remove this key and re-run SP4 from the original node (i.e the node that is already on SP4 and owns the SQL resources) and see if this helps?
For me this does not realy help. The node needs to be a possible owner of
the sql resources or else, the node is not updated. When you have just added
the node by the advanced sql setup option, this is not the case yet.
The second problem is, that this way sp4 updates all the nodes and takes the
SQL resources OFFLINE.
I tried installing SP3 first, which is not a goed idea. The sqlsetup runs
fine, the node becomes a possible owner but can't be used (sql wil not come
online), the NEED_SP_KEY dissapears, with means SP4 wants to reapply totaly.
Restoring the NEED_SP_KEY solves this but then the "Setup cannot
verify/grant logon as service right..." is back.
So adding a SP4 node without takeing SQL temporarily offline is not possible.
Hans
p.s.
SP4 was installed with a enterprise admin account.
|||There is a hotfix available from Microsoft support which fixed this for me.
See http://support.microsoft.com/?kbid=905286
BB.
"Hans de Bruin" wrote:

> Uttam Parui[MS] wrote:
> For me this does not realy help. The node needs to be a possible owner of
> the sql resources or else, the node is not updated. When you have just added
> the node by the advanced sql setup option, this is not the case yet.
> The second problem is, that this way sp4 updates all the nodes and takes the
> SQL resources OFFLINE.
> I tried installing SP3 first, which is not a goed idea. The sqlsetup runs
> fine, the node becomes a possible owner but can't be used (sql wil not come
> online), the NEED_SP_KEY dissapears, with means SP4 wants to reapply totaly.
> Restoring the NEED_SP_KEY solves this but then the "Setup cannot
> verify/grant logon as service right..." is back.
> So adding a SP4 node without takeing SQL temporarily offline is not possible.
> --
> Hans
> p.s.
> SP4 was installed with a enterprise admin account.
>