SQL Server 2005 Failover Cluster installation hang

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2005 Forums

SQL Server Administration (2005)

SQL Server 2005 Failover Cluster installation hang

Author

Topic

satishvsh
Starting Member

41 Posts

Posted - 2008-06-11 : 16:55:20

Hai -

Currently i am do sql server 2005 failover cluster installation on win 2003 server.

It is showing preparing to install please wait and there is no progress from last two hours.

Is there any way to check whether installation is going on or where can i check log files for this installation.

Please advise asap.

Cheers:)
vsh

satishvsh
Starting Member

41 Posts

Posted - 2008-06-11 : 17:00:13

Here is the log file i have :

Microsoft SQL Server 2005 Setup beginning at Wed Jun 11 14:23:56 2008
Process ID : 3680
\\NP486DB\D$\Installation Source\SQL 2005 Enterprise x86\Servers\setup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2008/5/11 14:23:56
Complete: LoadResourcesAction at: 2008/5/11 14:23:56, returned true
Running: ParseBootstrapOptionsAction at: 2008/5/11 14:23:56
Loaded DLL:\\NP486DB\D$\Installation Source\SQL 2005 Enterprise x86\Servers\xmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2008/5/11 14:23:56, 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::ProtectData
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", "", "3680"} 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/5/11 14:23:56
Complete: ValidateWinNTAction at: 2008/5/11 14:23:56, returned true
Running: ValidateMinOSAction at: 2008/5/11 14:23:56
Complete: ValidateMinOSAction at: 2008/5/11 14:23:56, returned true
Running: PerformSCCAction at: 2008/5/11 14:23:56
Complete: PerformSCCAction at: 2008/5/11 14:23:56, returned true
Running: ActivateLoggingAction at: 2008/5/11 14:23:56
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"
00C7CFC8Unable 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.

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-06-11 : 17:00:29

Did you meet all prerequisites? check event log if there is anything .

satishvsh
Starting Member

41 Posts

Posted - 2008-06-11 : 17:05:03

quote:
Originally posted by sodeep

Did you meet all prerequisites? check event log if there is anything .

Deep -

There is no eroors in event logs relevant to this installation

mdubey
Posting Yak Master

133 Posts

Posted - 2008-06-11 : 20:44:59

I am assuming you logged in both the server, that's what you are getting the same issue. Try to loggoff from one of the server.

Manoj
MCP, MCTS

billzini
Starting Member

1 Post

Posted - 2008-07-22 : 20:39:29

I am seeing the same exact issue, was this ever resolved? I made sure I was not logged on both nodes of the cluster during the install, I even rebooted both nodes and tried again, so far it fails every time. One item I saw, one of the logs told me to see the scheduled task log on my 2nd node and it says "An error has occurred that will negatively affect the operation of the service.
The specific error is:
0x80070020: The process cannot access the file because it is being used by another process." It does not specify what file, I looked on both systems and found no 'open' files so Im at a loss here.

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-07-22 : 23:05:42

Has anti-virus on those nodes? Disable scan if so.

nik
Starting Member

1 Post

Posted - 2009-07-28 : 07:46:40

I had absolutely the same issue - two node cluster and setup fails on the remote node. After few days fighting here is the solution in my case:

Use domain account for the SQL installation which is from the same domain as the servers. In my case i was using account from a child domain and this was the root cause.

Hope this will help you.

Regards,
Nik

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources