Stop the clustered Generic Script instance and check that the script code does not contain an infinite loop or infinite hang at the entry point indicated in the event message. If the script code is not causing a problem, consider increasing the pending timeout for this resource so that the associated application has enough time to start. For more information, see the procedures that follow.
To perform these procedures, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.
Stopping a clustered Generic Script instance, checking the coding, and restarting
To stop a clustered Generic Script instance, check the coding, and restart the clustered instance:
To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
In the Failover Cluster Management snap-in, if the cluster you want to manage is not displayed, in the console tree, right-click Failover Cluster Management, click Manage a Cluster, and then select or specify the cluster that you want.
If the console tree is collapsed, expand the tree under the cluster you want to manage, and then expand Services and Applications.
Right-click the clustered Generic Script instance and then click Take this service or application offline.
Review the associated script and ensure that any problematic code in it has been corrected.
Right-click the clustered Generic Script instance and then click Bring this service or application online.
Viewing the Pending Timeout setting for a clustered Generic Script resource
To view the Pending timeout setting for a clustered Generic Script resource:
To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
In the Failover Cluster Management snap-in, if the cluster you want to manage is not displayed, in the console tree, right-click Failover Cluster Management, click Manage a Cluster, and then select or specify the cluster that you want.
If the console tree is collapsed, expand the tree under the cluster you want to manage, and then expand Services and Applications.
Click the clustered Generic Script instance.
Right-click the generic script resource, and then click Properties.
Click the Policies tab and view the value for Pending timeout, which is measured in minutes and seconds. This timeout must allow enough time for the associated application to start.
If you do not currently have Event Viewer open, see "Opening Event Viewer and viewing events related to failover clustering."
Opening Event Viewer and viewing events related to failover clustering
To open Event Viewer and view events related to failover clustering:
If Server Manager is not already open, click Start, click Administrative Tools, and then click Server Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
In the console tree, expand Diagnostics, expand Event Viewer, expand Windows Logs, and then click System.
To filter the events so that only events with a Source of FailoverClustering are shown, in the Actions pane, click Filter Current Log. On the Filter tab, in the Event sources box, select FailoverClustering. Select other options as appropriate, and then click OK.
To sort the displayed events by date and time, in the center pane, click the Date and Time column heading.
Home
PLK