Setup failed to start

Yesterday I ran into this error message while installing a new SQL Server 2005 instance on a Windows 2003 cluster:

Setup failed to start on the remote machine. Check the Task scheduler event log on the remote machine.

SQL Server 2005 setup, in a clustered environment, relies on a remote setup process started on the passive nodes through a scheduled task:

For some weird reason, the remote scheduled task refuses to start if there is an active RDP session on the passive nodes. This KB article describes symptoms and resolution in detail:

If you look into the Scheduled Tasks log you will find something similar to this:

sql server Task did not appear to start on machine <machine_name> 267015

Needless to say that one of my co-workers was logged on the desktop of one of the passive nodes.  So, if you need another good reason to lock everyone out of your servers’ desktop, here it is.

After resetting the offending session, remember to log on to all the passive nodes and kill the zombie setup processes you may have left. Also, delete the scheduled tasks from each node.

Posted on May 27, 2011, in SQL Server and tagged , , . Bookmark the permalink. 1 Comment.

  1. And What will happen if there is no logged session over the nodes should I move the instances to other servers (counting the foreign connections to the server )

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: