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
 High Availability (2005)
 Clustered instance fails to install

Author  Topic 

jordanam
Yak Posting Veteran

62 Posts

Posted - 2008-09-05 : 15:33:46
I imagine this is something silly and I am missing something simple. My problem is described here:
http://www.eggheadcafe.com/software/aspnet/29754769/cluster-install--cant-g.aspx

The person who posted had a vague solution.

On Windows 2008 x64 I have 2 clustered nodes. 1 node is hosting 2 SQL 2k5 instances, and the second node is passive. Failover is successful between nodes.

I am attempting to install a third instance. Using a domain administrator with explicitly defined admin rights on both boxes, I can run through the SQL setup successfully until I have to enter the user password. Authentication works (I tried using a bad password and that raised a different error), but I get an error message that says I must be an administrator on all nodes in order to install. For giggles I tried a second account and got the same results.

Thoughts?

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2008-09-05 : 15:48:02
Have you checked the SQL Server setup log files to see if there is more information in there or perhaps a better error?

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

jordanam
Yak Posting Veteran

62 Posts

Posted - 2008-09-05 : 16:01:29
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Server 4.0, Enterprise Edition Service Pack 1 (Build 6001)
Time : Fri Sep 05 14:32:52 2008

clusno1 : Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.
clusno1 : Failed to find the ASP.Net Version Registration with Microsoft Internet Information Services (IIS).
clusno1 : To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.

SQL Server Setup was interrupted. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.


Time : Fri Sep 05 14:35:17 2008



Looks kind of vague...
Go to Top of Page

jordanam
Yak Posting Veteran

62 Posts

Posted - 2008-09-05 : 16:20:48
I also get this. So, I changed my SA password on both instances... and still no dice.




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

SQL Server 2005 Setup requires administrator permissions on every cluster node. To continue, update permissions for the account currently running Setup, or log in with an account that has administrator permissions on every cluster node, and then run SQL Server Setup again.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=SQLSetup90&EvtType=28076

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

OK
------------------------------
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2008-09-05 : 16:43:38
I'd suggest opening a case with Microsoft on this. They've helped me numerous times on various cluster installation failures.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

jordanam
Yak Posting Veteran

62 Posts

Posted - 2008-09-10 : 14:10:00
Well, calling Microsoft certainly addressed the issue. It was a long day. I think I spoke to 7 different people, and at some point insisted that someone from the Windows Cluster 2008 core team be involved along with someone from the SQL core team. Between the two of them, we were able to fix the problems.

I can't for the life of me remember all of the steps we went through. Here is a list of the bigger steps:

- One of the servers was not synching time with the domain, this was fixed by referencing an article here: http://social.technet.microsoft.com/forums/en-US/winservergen/thread/96278628-03a1-4b3d-90d9-2208a65a1210/
- The WMI repository was rebuilt entirely. The MS techs used a batch script. I don't have a link for that. It wasn't the integrity check command.
- DTC was added as a resource to the cluster, and best practices for that can be found here: http://technet.microsoft.com/en-us/library/cc771540.aspx
Go to Top of Page
   

- Advertisement -