In a previous entry, I explained how Setup for a SQL Server failover cluster runs the installation on the second (and subsequent) node(s) to provide the ‘failover’ SQL Server instances; to install these instances, Setup creates a Scheduled Task on the second node (that points back the Setup program on the first node) and then starts the scheduled task, installing SQL Server on both nodes at the same time.
However, imagine a scenario where you don’t have Task Scheduler running on the remote server/s (e.g. for security reasons); if this is the case, you may encounter the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
along with an error similar to the following in the Event Log:
Connection to remote computer's scheduler service.
Error: SetTargetComputer on \\machinename failed with
Unable to start service (1058)
If this is the case, simply start the Task Scheduler on the remote node/s and restart the SQL Server installation.
0 Responses to “Clustered SQL Server Installation – More Task Scheduler Challenges”