Clustering SQL and service packs

I have a SQL 2000 cluster and have applied SP3 to it.
However, when running on one side of the cluster SQL reports a different
version to when it is running on the other side. Is this normal / expected
or has it not applied SP3 to the other node correctly?
e.g
Running on node 1
select @.@.version
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: )
SELECT SERVERPROPERTY('ProductLevel')
SP3
Running on node 2
select @.@.version
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: )
SELECT SERVERPROPERTY('ProductLevel')
RTM
If this is not normal / exptected, can I just apply SP3 to node 2 on its
own?
Thanks.
Hi
SQL 2000 sp3 automatically installs itself on all nodes of a cluster. You
have a problem.
Try running it on the 2nd node and see if it will install. Was B down when
sp3 was installed?
Regards
Mike
"Stephen Aldous" wrote:

> I have a SQL 2000 cluster and have applied SP3 to it.
> However, when running on one side of the cluster SQL reports a different
> version to when it is running on the other side. Is this normal / expected
> or has it not applied SP3 to the other node correctly?
> e.g
> Running on node 1
> select @.@.version
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: )
> --
> SELECT SERVERPROPERTY('ProductLevel')
> SP3
> --
> Running on node 2
> select @.@.version
> Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: )
> SELECT SERVERPROPERTY('ProductLevel')
> RTM
>
> If this is not normal / exptected, can I just apply SP3 to node 2 on its
> own?
>
> Thanks.
>
>
|||I've tried to install SP3 on the virtual cluster name again and it crashes
to desktop with an error with _INS576._mp error.
Can I just fail it over to the second node and install SP3 on the local
machine?
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:76ECCB2C-267F-406E-B6EE-0CA05F435A2B@.microsoft.com...[vbcol=seagreen]
> Hi
> SQL 2000 sp3 automatically installs itself on all nodes of a cluster. You
> have a problem.
> Try running it on the 2nd node and see if it will install. Was B down when
> sp3 was installed?
> Regards
> Mike
> "Stephen Aldous" wrote:
expected[vbcol=seagreen]
|||Hi
Raise a case with Microsoft PSS as you need their help. Safest.
Regards
Mike
"Stephen Aldous" wrote:

> I've tried to install SP3 on the virtual cluster name again and it crashes
> to desktop with an error with _INS576._mp error.
> Can I just fail it over to the second node and install SP3 on the local
> machine?
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:76ECCB2C-267F-406E-B6EE-0CA05F435A2B@.microsoft.com...
> expected
>
>
|||Hi Steve,
This is not normal. It appears that SP3 got installed only on node 1 and not node 2. Currently your cluster nodes has mis-matched binaries. Infact, SQL Server MAY not even start on node 2 or you may get
unexpected results if you run SQL on node 2.
While SQL is running on node 1, try running SP3 setup on node 2 and see if it succeeds. If it fails then post the exact steps that you took to run the setup, exact error message and the sqlsp.log file.
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