Event ID 1040 — Generic Service Resource Availability

  • Article

Applies To: Windows Server 2008 R2

The service used by a clustered Generic Service instance must start and run correctly before clients can use it. If any settings related to the service or the associated clustered resource are incorrect, the clustered Generic Service instance cannot function correctly.

Event Details

Product: Windows Operating System
ID: 1040
Source: Microsoft-Windows-FailoverClustering
Version: 6.1
Symbolic Name: RES_GENSVC_OPEN_FAILED
Message: Generic service '%1' could not be brought online (with error '%2') during an attempt to open the service. Possible causes include: the service is either not installed or the specified service name is invalid.

Resolve

Confirm that the service exists on nodes

Confirm that the correct service is specified in the configuration for the Generic Service resource, and confirm that the service is fully installed on all nodes that are possible owners of the resource. For more information, see "Viewing or changing the service name and the possible owners specified for a clustered Generic Service instance" and "Opening Services and viewing installed services."

If the service appears to be installed on the nodes that are possible owners, check Event Viewer for other errors related to the service to see what might be interfering with service startup.

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."

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.

Viewing or changing the service name and the possible owners specified for a clustered Generic Service instance

To view or change the service name and the possible owners specified for a clustered Generic Service instance:

  1. 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.
  2. 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.
  3. If the console tree is collapsed, expand the tree under the cluster you want to manage, and then expand Services and Applications.
  4. In the console tree, click the clustered Generic Service instance.
  5. In the center pane, right-click the Generic Service resource, and then click Properties.
  6. Click the Advanced Policies tab, and under Possible Owners, make sure that the selected nodes are as intended.
  7. Click the General tab, and make sure that the Service name and Startup parameters are entered as intended.

Opening Services and viewing installed services

To open Services and view installed services:

  1. 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.

  2. In the console tree, expand Configuration, and then click Services.

  3. 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.

To open Event Viewer and view events related to failover clustering:

  1. 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.
  2. In the console tree, expand Diagnostics, expand Event Viewer, expand Windows Logs, and then click System.
  3. 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.
  4. 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:

  1. View the event, and note the error code.
  2. Look up more information about the error code in one of two ways:

Verify

Confirm that you can bring the clustered Generic Service 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 Service instance online:

  1. 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.
  2. 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.
  3. If the console tree is collapsed, expand the tree under the cluster you want to manage, and then expand Services and Applications.
  4. In the center pane, if the clustered Generic Service instance is not online, right-click it and then click Bring this service or application online.

Generic Service Resource Availability

Failover Clustering