Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 4689

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.

$
0
0

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 itfailed 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_CLSANRECAUDB01_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_CLSANRECAUDB01_Core(Local).log

               C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0025_CLSANRECAUDB01_Datastore.xml

               C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0025_CLSANRECAUDB01_.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_CLSANRECAUDB01_SCC.log

               C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0025_CLSANRECAUDB01_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 all articles
Browse latest Browse all 4689

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>