Generic application could not be brought online due to process creation error
Resolutions
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:
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.
To view or change the service name and other settings for a clustered Generic Application instance:
To open Event Viewer and view events related to failover clustering:
To find more information about the error codes that some event messages contain:
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.
In the console tree, click the clustered Generic Application instance.
In the center pane, right-click the Generic Application 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 Command line and Parameters are entered as intended. For Command line, check the path as well as the application name.
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.
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.
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 ( http://go.microsoft.com/fwlink/?LinkId=83027).
Click Start, point to All Programs, click Accessories, click Command Prompt, and then type:
NET HELPMSG errorcode
Home
ENU