| Event Information | According to Microsoft :
Cause :
This event is logged when Generic application could not be brought online during an attempt to start the service.
Resolution :
Confirm service settings and parameters
If you do not currently have Event Viewer open, see ""Opening Event Viewer and viewing events related to failover clustering."" If the event contains an error code that you have not yet looked up, see ""Finding more information about error codes that some event messages contain."" After reviewing events, confirm that the following are true for the service used by the clustered Generic Service instance: - The service is enabled. For more information, see ""Opening Services and viewing installed services.""
- If the service interacts with other files, permissions on those files are not interfering with the running of the service.
- The parameters specified for service startup are appropriate. For more information, see ""Viewing or changing the service name and other settings for a clustered Generic Service instance"" and ""Opening Services and viewing installed services.""
- The correct service is specified in the configuration for the Generic Service resource. For more information, see ""Viewing or changing the service name and other settings for a clustered Generic Service instance.""
- The service is fully installed on all nodes that are possible owners of the resource. For more information about viewing the possible owners of a resource, see ""Viewing or changing the service name and other settings for a clustered Generic Service instance,"" later in this description.
If all of the preceding items appear to be configured correctly, check Event Viewer for other errors related to the service to see what might be interfering with service startup.
To perform these procedures, you must be a member of the local Administrators group on the server, or you must have been delegated the equivalent authority.
Opening Services and viewing installed services
To open Services and view installed services: - 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 Configuration , and then click Services .
- In the center pane, scroll to the service you want to view.
You can view the properties of the service by right-clicking it and then clicking Properties .
Viewing or changing the service name and other settings for a clustered Generic Service instance
To view or change the service name and other settings for a clustered Generic Service instance: - To open the failover cluster snap-in, click Star t, 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 .
- In the console tree, click the clustered Generic Service instance.
- In the center pane, right-click the Generic Service resource, and then click Properties .
- Click the Advanced Policies tab, and under Possible Owners , make sure that the nodes that are selected are the ones you intended.
- Click the General tab, and make sure that the Service name and Startup parameters are entered as intended.
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.
Finding more information about the error codes that some event messages contain
To find more information about the error codes that some event messages contain: - View the event, and note the error code.
- Look up more information about the error code in one of two ways:
- Search System Error Codes.
- Click Start , point to All Programs , click Accessories , click Command Prompt , and then type:
NET HELPMSG errorcode
Verify :
Confirm that you can bring the clustered Generic Script instance online and that it remains online without causing additional events to be logged.
To perform this procedure, 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.
To bring a clustered Generic Script instance online: - To open the failover cluster snap-in, click Start , click Administrative Tools , and then click Failover Cluster Management . If the User Account Contro l 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 .
- In the center pane, if the clustered Generic Script instance is not online, right-click it and then click Bring this service or application online .
|