When trying to install SQL 2005 Standard on a two-node cluster, I get this
message when I start the install:

TITLE: Microsoft SQL Server 2005 Setup
------------------------------

There was an unexpected failure during the setup wizard. You may review the
setup logs and/or click the help button for more information.


For help, click:
http://go.microsoft.com/fwlink?LinkI...Property%400x2

------------------------------
BUTTONS:

OK
------------------------------
Any insight would be greatly appreciated as I did install a SQL 2005
two-node cluster into the same domain. The cluster, SQL cluster and MSDTC
cluster will have different names and IPs.

Thanks,
Tom.

Look for the SQL Setup logs and see where the first ERROR or FAILURE is.

That usually helps narrow down the problem.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"Germex" <Germex (AT) discussions (DOT) microsoft.com> wrote

Well,

Turns out that the culprit was MSDTC and COM+. Once I got those guys behave
properly in a cluster (successful fail over), I was at least able to install
SQL on the cluster. One minor issue now: SQL and SQL Agent Services are not
starting claiming that:

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 5173
Date: 3/24/2009
Time: 2:48:58 PM
User: N/A
Computer: SQLRPTTST
Description:
One or more files do not match the primary file of the database. If you are
attempting to attach a database, retry the operation with the correct files.
If this is an existing database, the file may be corrupted and should be
restored from a backup.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 35 14 00 00 10 00 00 00 5.......
0008: 0a 00 00 00 53 00 51 00 ....S.Q.
0010: 4c 00 52 00 50 00 54 00 L.R.P.T.
0018: 54 00 53 00 54 00 00 00 T.S.T...
0020: 00 00 00 00 ....

and
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (3)
Event ID: 19019
Date: 3/24/2009
Time: 2:48:58 PM
User: N/A
Computer: CELP-TST001
Description:
[sqsrvres] StartResourceService: Failed to start MSSQLSERVER service.
CurrentState: 1


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 4b 4a 00 40 01 00 00 00 KJ.@....
0008: 0a 00 00 00 53 00 51 00 ....S.Q.
0010: 4c 00 52 00 50 00 54 00 L.R.P.T.
0018: 54 00 53 00 54 00 00 00 T.S.T...
0020: 00 00 00 00 ....

Would you happen to have any ideas since this is an initial install with no
custom databases in it?

"Geoff N. Hiten" wrote:

I found this in the SQL error log.

2009-03-25 07:56:36.68 Server Database Mirroring Transport is disabled
in the endpoint configuration.
2009-03-25 07:56:36.68 spid5s Starting up database 'master'.
2009-03-25 07:56:36.71 spid5s Error: 5172, Severity: 16, State: 15.
2009-03-25 07:56:36.71 spid5s The header for file 'R:\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\master.mdf' is not a valid database file header.
The PageAudit property is incorrect.
2009-03-25 07:56:36.71 spid5s Error: 5173, Severity: 16, State: 1.
2009-03-25 07:56:36.71 spid5s One or more files do not match the
primary file of the database. If you are attempting to attach a database,
retry the operation with the correct files. If this is an existing database,
the file may be corrupted and should be restored from a backup.
2009-03-25 07:56:36.71 spid5s Error: 5173, Severity: 16, State: 1.
2009-03-25 07:56:36.71 spid5s One or more files do not match the
primary file of the database. If you are attempting to attach a database,
retry the operation with the correct files. If this is an existing database,
the file may be corrupted and should be restored from a backup.

How do I recover from this?

"Germex" wrote:

I would suggest ripping it out and reinstalling if you haven't got any real
data in the system.

If you have to fix what is there, you can rebuild the master database.

Log into the node with the SQL resource. Using cluster administrator, bring
everything online except SQL and the SQL Agent service. You can then follow
the BOL instructions on how to rebuild a master database. At this point it
works enough like a stand-alone SQL install for the instructions to work.

Again, ripping it out and reinstalling is easier.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP





"Germex" <Germex (AT) discussions (DOT) microsoft.com> wrote