SQL 2005 x64 install failover cluster fails - unexpected error while completing Commit - fatal error

Florescu
Florescu used Ask the Experts™
on
I have 2 Windows Server 2003 Enterprise x64 and I have configured them for clustering using the following article:

http://www.sql-server-performance.com/articles/clustering/cluster_server_2003_p1.aspx

I tested the failover between the two nodes and everything was successful.  

I then started installing SQL 2005 Enterprise x64 (Failover cluster) using the following article

http://www.sql-server-performance.com/articles/clustering/cluster_sql_server_2005_p1.aspx

Everything was going fine and then about half way thru, I started getting error messages:

1.  The SQL Server Service failed to start.  

-->I verified that the account I was using was a member of the local administrators on both nodes, tried Local System account by going to Services and Properties of that service but that didn't work either.  I just said "Cancel" on that first error.

2.  The setup has encountered an unexpected error while Completing Commit.  The error is Fatal error during installation.

I then looked at the setup log.  here's what I found:

MSI (s) (FC:14) [23:17:58:434]: Note: 1: 1708
MSI (s) (FC:14) [23:17:58:434]: Product: Microsoft SQL Server 2005 (64-bit) -- Installation failed.

Then I searched for "value 3" and here's the 10 lines above that:

MSI (s) (FC:14) [23:17:57:856]: MsiProvideAssembly is returning: 1607
MSI (s) (FC:14) [23:17:57:856]: Entering MsiProvideAssembly. AssemblyName: Microsoft.SqlServer.SString,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0", AppContext: , InstallMode: -4
MSI (s) (FC:14) [23:17:57:856]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (FC:14) [23:17:57:856]: MsiProvideAssembly is returning: 1607
MSI (s) (FC:14) [23:17:57:856]: Entering MsiProvideAssembly. AssemblyName: Microsoft.SqlServer.Smo,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0", AppContext: , InstallMode: -4
MSI (s) (FC:14) [23:17:57:856]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (FC:14) [23:17:57:856]: MsiProvideAssembly is returning: 1607
MSI (s) (FC:14) [23:17:57:872]: No System Restore sequence number for this installation.
MSI (s) (FC:14) [23:17:57:872]: Unlocking Server
MSI (s) (FC:14) [23:17:57:872]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
Action ended 23:17:57: INSTALL. Return value 3.



What to do?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Systeemontwikkelaar, Database Administrator
Commented:
With the error, make sure that you're NOT logged in on the other node because than the authentication will fail or the service.

Second problem: I've had a lot of trouble installing a SQL Server 2005 cluster when the amount of processors was not in the power of 2 or just had too much processors.

In that case try this article: http://www.sqlservercentral.com/articles/SQL+Server+2005/67297/

Author

Commented:
Thanks a lot for that.  That fixed the install for me.  It was that I had too many CPUs.  

I kept following that article because I need to install SP3 so I can get my CPUs back.  
http://www.sqlservercentral.com/articles/Installation/66128/ 

I ran into some problems with following that.  I got to steps 3 and 4 and then I got confused.  My data files are on drive S.  I'm assuming that we need to copy the "mssqsystemlresource.ldf" and "mssqsystemlresource.mdf" to another location, rename them, then copy them back.  So I ended up with this in the data folder:

mssqsystemlresource.ldf
mssqsystemlresource.mdf
mssqsystemlresource_old.ldf
mssqsystemlresource_old.mdf

Then I attempted to start SQL from command line but that didn't work:
NET START MSSQLSERVER /f /T3608
The SQL Server (MSSQLSERVER) service is starting.
The SQL Server (MSSQLSERVER) service could not be started.

The service did not report an error.
More help is available by typing NET HELPMSG 3534.

Then I started the SQL services in the cluster and I was able to connect from the command line:
SQLCMD -S CPS9 -U sa -P password

(CPS9 is the virtual SQL name and I only have a default instance).  This is where I started to get more error messages:

1> ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME = data, FILENAME = 'mssq
lsystemresource_old.mdf')
2> GO
Msg 5105, Level 16, State 2, Server CPS9, Line 1
A file activation error occurred. The physical file name 'mssqlsystemresource_old.mdf' may be incorrect. Diagnose and correct additional errors, and retry the operation.
Msg 911, Level 16, State 1, Server CPS9, Line 1
Could not locate entry in sysdatabases for database 'mssqlsystemresource'. No entry found with that name. Make sure that the name is entered correctly.

I'm not very familiar with SQL commands so I'm assuming the GO command runs on a separate line.  I also tried it on the same line but it gave me the same error message.

-----------------------------------------------------------
I also tried to just rename the MDF and LDF files so I only had this in the data folder:
mssqsystemlresource_old.ldf
mssqsystemlresource_old.mdf

Then the SQL services wouldn't start at all, not even from the cluster administrator.
Sander StadSysteemontwikkelaar, Database Administrator

Commented:
The "GO" statement tells the SQL engine to start the command(s) given before the "GO".

Could you try to assign the full path to the MDF en LDF file in the command like this:
ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME = data, FILENAME = 'S:\mssqlsystemresource_old.mdf')

It could be that there is some different setting where SQL Server searches for the files.

Author

Commented:
1> ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME = data, FILENAME = 'S:\M
icrosoft SQL Server\MSSQL.1\MSSQL\Data\mssqlsystemresource_old.mdf')
2> ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME = log, FILENAME = 'S:\Mi
crosoft SQL Server\MSSQL.1\MSSQL\Data\mssqlsystemresource_old.ldf')
3> GO
Msg 911, Level 16, State 1, Server CPS9, Line 1
Could not locate entry in sysdatabases for database 'mssqlsystemresource'. No en
try found with that name. Make sure that the name is entered correctly.

Author

Commented:
I was able to install SP3 without doing any of that.  I guess it's case specific.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial