SQL Server 2005 SP3 add node to cluster error: Adding nodes to the Virtual Server definition using a newer version of Setup is not allowed.

Question

SQL Server 2005 SP3 add node to cluster error: Adding nodes to the Virtual Server definition using a newer version of Setup is not allowed.

sqlcl

SSC Enthusiast

Points: 161
More actions
June 9, 2015 at 7:30 am

#298806

Hi experts.
One of my actual production environments is a Failover two-node cluster, SQL Server 2005 SP3 on Windows Server 2003 R2. Recently, the node 2 was failed, so I formatted a new machine to add the new node, but it failed with the following error: “Adding nodes to the Virtual Server definition using a newer version of Setup is not allowed.”
I have searching across the web for a solution but I can’t find it.
The Summary file “Summary.txt” are:
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 2 (Build 3790)
Time : Thu Jun 04 13:04:38 2015
Machine : NODE01
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0025_NODE01_WI.log
Error Number : 1603
--------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time : Thu Jun 04 13:07:37 2015
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0025_NODE01_Core(Local).log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0025_NODE01_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0025_NODE01_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0025_NODE01_SCC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0025_NODE01_WI.log
C:\DOCUME~1\Admin\LOCALS~1\Temp\2\SCA11.dmp
One point of my attention, it’s that the Product Version that appears on this summary file corresponding a 9.00.1399.06 that is to say, a RTM version, not SP3 (9.00.4035).
Based on this, I went to the path where the files of installation are (ARPWrapper.exe), "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap" and I 've found that these files contain a different version of what I have currently installed. For example, in properties of ARPWrapper.exe the version of this is 2005.90.1399.0 The same goes for the rest of the files in that folder:
Microsoft.SqlServer.AnalysisServices.UpgradeAdvisor.dll
Microsoft.SqlServer.BestPracticesAnalyzer.UpgradeAdvisor.dll
Microsoft.SqlServer.DTS.UpgradeAdvisor.dll
setup.exe
…
…
…
And so on.
So, the question is:
Is it possible that the solution is to replace these files with the corresponding version, in this case the version 2005.90.4035.0(SP3) and continue with the installation? Has anyone done this before?
Please , any help is welcome.

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

spaghettidba SSC Guru Points: 105732 More actions · Answer 1

At a glance, looks like the previous installation of service pack 3 failed to update the binaries, which is quite weird.

Adding more nodes to a SQL 2005 cluster has always been a bloodbath, especially when the setup files don't match the installed version. It's one of the main points adressed in the setup process since SQL Server 2008.

That said, you could also patch the existing node to SP4, slipstream SP4 in the setup media and re-run the add node process with it.

Sounds reasonable?

-- Gianluca Sartori

sqlcl SSC Enthusiast Points: 161 More actions · Answer 2

Dear Gianluca.

What you say makes sense, for some reason, when applying SP3 this not updated binaries. Unfortunately for now I can not apply SP4 because applications that connect to the database engine have not been tested with this update, so the engine has to stay in SP3.

sqlcl SSC Enthusiast Points: 161 More actions · Answer 3

Update:

In laboratory environment, I have replaced the file versions standardizing both, the SQL engine and the installation files and it worked, so I will try in production.

spaghettidba SSC Guru Points: 105732 More actions · Answer 4

spaghettidba

SSC Guru

Points: 105732

June 10, 2015 at 9:50 am

#1804399

Good luck!

-- Gianluca Sartori

Perry Whittle SSC Guru Points: 234064 More actions · Answer 5

to install and patch a new node to a sql 2005 cluster requires the following steps

join new node to the Windows cluster
from active node run sql server setup via add\remove programs, select the option to "Maintain virtual server"
run through setup and at the part where nodes are selected add the new node and click next
when setup finishes the instance will fail to start as the binaries will be a lower version. obtain the SP3 installer and from cluster administrator pause the active node (sql server instance outage is required)
run the SP3 installer on the new node and when finished reboot the node
resume the paused node
when the second node comes back up perform a failover to check operation

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

sqlcl SSC Enthusiast Points: 161 More actions · Answer 6

Hi everyone.

Finally , in the active (and only) node, I've replaced the installation binary files the following path C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\ and added the node without problems, so now I have two-node cluster environment.

I had previously tested this in development and now made ??the change in production environment, resulting in the successful action.

Thank you all for your help and advice.