Issue installing sql 2005 x64 on a cluster

[kodaksmile]

I am trying to install sql 2005 on a 64 bit cluster (which I have done several times with no issues) but, have hit a glitch where the install hangs saying it is configuring components but, never proceeds. When I check the install logs I find the following message:

Microsoft SQL Server 2005 Setup beginning at Mon Oct 20 13:09:58 2008
Process ID : 4904
\\SACDEVMCSSQL04A\D$\SQL 2005 Ent 64-bit\CD1\setup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2008/9/20 13:9:58
Complete: LoadResourcesAction at: 2008/9/20 13:9:58, returned true
Running: ParseBootstrapOptionsAction at: 2008/9/20 13:9:58
Loaded DLL:\\SACDEVMCSSQL04A\D$\SQL 2005 Ent 64-bit\CD1\xmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2008/9/20 13:9:58, returned false
Error: Action "ParseBootstrapOptionsAction" failed during execution. Error information reported during run:
Could not parse command line due to datastore exception.
Source File Name: utillib\persisthelpers.cpp
Compiler Timestamp: Fri Jul 29 01:13:55 2005
Function Name: writeEncryptedString
Source Line Number: 124
----------------------------------------------------------
writeEncryptedString() failed
Source File Name: utillib\persisthelpers.cpp
Compiler Timestamp: Fri Jul 29 01:13:55 2005
Function Name: writeEncryptedString
Source Line Number: 123
----------------------------------------------------------
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.

Source File Name: cryptohelper\cryptsameusersamemachine.cpp
Compiler Timestamp: Mon Jun 13 14:30:00 2005
Function Name: sqls::CryptSameUserSameMachine:rotectData
Source Line Number: 50

2
Could not skip Component update due to datastore exception.
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "InstallMediaPath" {"SetupBootstrapOptionsScope", "", "4904"} in cache
Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupBootstrapOptionsScope"
Running: ValidateWinNTAction at: 2008/9/20 13:9:58
Complete: ValidateWinNTAction at: 2008/9/20 13:9:58, returned true
Running: ValidateMinOSAction at: 2008/9/20 13:9:58
Complete: ValidateMinOSAction at: 2008/9/20 13:9:58, returned true
Running: PerformSCCAction at: 2008/9/20 13:9:58
Complete: PerformSCCAction at: 2008/9/20 13:9:58, returned true
Running: ActivateLoggingAction at: 2008/9/20 13:9:58
Error: Action "ActivateLoggingAction" threw an exception during execution. Error information reported during run:
Datastore exception while trying to write logging properties.
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache
Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name: SetupStateScope.primaryLogFiles
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupStateScope"
0000000000FBAF90Unable to proceed with setup, there was a command line parsing error. : 2
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.

Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44

Class not registered.

I have used the same media in the past and have not had any issues. Any suggestions?

 

[yelworcm]

Step one would probably be to check the OS patch levels on all the cluster nodes. Just to make sure they are all in sync. If that does not pan out, I have copied the installation files to a physical disk of one of the nodes, and installed from there. Our setupsespecially do not like to install from USB devices, but the local disk approach has worked for me.