Event ID 1039 — Generic Application Resource Availability

Updated: December 5, 2007

Applies To: Windows Server 2008

red

This aspect provides information to help you interpret system messages that indicate whether the Generic Application resource is operational.

Event Details

Product: Windows Operating System
ID: 1039
Source: Microsoft-Windows-FailoverClustering
Version: 6.0
Symbolic Name: RES_GENAPP_CREATE_FAILED
Message: Generic application '%1' could not be brought online (with error '%2') during an attempt to create the process. Possible causes include: the application may not be present on this node, the path name may have been specified incorrectly, the binary name may have been specified incorrectly.

Resolve

Confirm application settings

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 application used by the clustered Generic Application instance:

  • The application is fully installed on all nodes that are possible owners of the Generic Application resource. For more information about viewing possible owners of a resource, see "Viewing or changing the service name and other settings for a clustered Generic Application instance."
  • The configuration for the Generic Application resource specifies the correct application and path. For more information, see "Viewing or changing the service name and other settings for a clustered Generic Application instance."
  • The configuration for the Generic Application resource specifies appropriate parameters and settings for registry replication. (Registry replication settings ensure that all application configuration information being stored in the registry is replicated to all nodes.) For more information, see "Viewing or changing the service name and other settings for a clustered Generic Application instance."

If all of the preceding items appear to be configured correctly, check Event Viewer for other errors related to the application to see what might be interfering with application 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.

Viewing or changing the service name and other settings for a clustered Generic Application instance

To view or change the service name and other settings for a clustered Generic Application 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 Application instance.
  5. In the center pane, right-click the Generic Application resource, and then click Properties.
  6. Click the Advanced Policies tab, and under Possible Owners, make sure that the nodes that are selected are the ones you intended.
  7. Click the General tab, and make sure that the Command line and Parameters are entered as intended. For Command line, check the path as well as the application name.
  8. If the application requires configuration information to be stored in the registry on all computers on which the application runs, click Registry Replication and make sure that it specifies any registry keys below HKEY_LOCAL_MACHINE that should be replicated to all nodes in the cluster.

Opening Event Viewer and viewing events related to failover clustering

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 Application 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 Application 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 Application instance is not online, right-click it and then click Bring this service or application online.

Related Management Information

Generic Application Resource Availability

Failover Clustering

Community Additions

ADD
Show: