Installation issue..Help !! | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Installation issue..Help !!

Hi, I’m getting the following message while installing 64-bit SQL Server 2005 cluster: "Setup failed to start on the remote machine. Check the Task scheduler event log on the remote machine." SQL Server 2005 install files are copied to the local share. Also the Task Scheduler service is running. Users are not logged into this node. Followed KB article 910851, no luck! Appreciate help on this.. Thanks
be sure you don’t have sessions like Remote Desktop connection open to the other node !
Appreciate your response. I’m logged into the Node via RDP session, no other sessions are open to this node or the other node.

SQL Server 2005 Books Online
Before Installing Failover Clustering Verify Your Operating System Settings
Make sure that your operating system is installed properly and designed to support failover clustering. For more information on supported operating systems, see Hardware and Software Requirements for Installing SQL Server 2005.
Enable Windows Cryptographic Service Provider (CSP) on Windows Server 2003. If the CSP service is stopped or disabled on any cluster node, SQL Server Setup fails with a Windows Logo Requirement dialog.
Enable the Task Scheduler service on all operating systems for remote and cluster installation. If the Task Scheduler is disabled, SQL Server Setup fails with Error 1058. For more information, see How to: Enable Windows Task Scheduler Service. SQL Server 2005 supports mount points; the clustered installations of SQL Server are limited to the number of available drive letters. Assuming that you use only one drive letter for the operating system, and all other drive letters are available as normal cluster drives or cluster drives hosting mount points, you are limited to a maximum of 25 instances of SQL Server per failover cluster. A mounted volume, or mount point, allows you to use a single drive letter to refer to many disks or volumes. If you have a drive letter D: that refers to a regular disk or volume, you can connect or "mount" additional disks or volumes as directories under drive letter D: without the additional disks or volumes requiring drive letters of their own. Special mount point considerations for SQL Server 2005 failover clustering:
SQL Server Setup requires that the base drive of a mounted drive has an associated drive letter. For failover cluster installations, this base drive must be a clustered drive.
The base drive, the one with the drive letter, cannot be shared among failover cluster instances. This is a normal restriction for failover clusters, but is not a restriction on stand-alone, multi-instance servers.
Take extra care when setting up your failover cluster to ensure that both the base drive and the mounted disks or volumes are all listed as resources in the resource group. SQL Server Setup does not take care of this automatically, nor does SQL Server check for this during CREATE/ALTER DATABASE.
Ensure that the mounted disks or volumes are mounted under the correct lettered base drive, and make sure that the mounted drive is set to be dependent on the parent drive. MohammedU.
Moderator All postings are provided “AS IS” with no warranties for accuracy.

MohammedU, Windows 2003 Clustering works fine. I’m able to move groups/resources between nodes. All the drives are NTFS formatted.. Also I get as far as selecting the necessary services to install SQL Server 2005 on this cluster but right when it starts to install, it fails with that message. Should I be running the install of Disc ??
When you install the on cluster server….it uses Task Scheduler to install on the other node so make sure that the Schedule service is running on both nodes…
And do not intall using network/mapped drives…either you use local media or local folder…
Moderator All postings are provided “AS IS” with no warranties for accuracy.

MohammedU, I got this resolved. Apparently I can have only 1 node logged in at a time for install. I had installed SQL Server 2005 32-bit version clustered in a VM environment and didn’t have this restriction. Appreciate your help guys!!! Thanks!
that’s exactly what I was refering to when i mentioned … … be sure you don’t have sessions like Remote Desktop connection open to the other node !….
Hi Alzdba, My bad , I was under stress due to time limitation on getting the cluster up & running and couldn’t read the obvious as per your earlier response. Appreciate your help!!! Thanks
been there … done that [<img src=’/community/emoticons/emotion-5.gif’ alt=’;)‘ />]