Event ID 1205 — Clustered Service or Application Availability

Event ID 1205 — Clustered Service or Application Availability

Updated: November 25, 2009

Applies To: Windows Server 2008 R2

In a failover cluster, a clustered service or application can come online (and be available for clients to use) only when the necessary clustered resources within it can come online.

Event Details

Product: Windows Operating System
ID: 1205
Source: Microsoft-Windows-FailoverClustering
Version: 6.1
Symbolic Name: RCM_EVENT_GROUP_FAILED_ONLINE_OFFLINE
Message: The Cluster service failed to bring clustered service or application ‘%1’ completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.

Resolve
Check state of all resources in the clustered service or application

Note that in some situations where a clustered service or application does not come online correctly, the Cluster service, as it follows restart policies, might be able to restart the clustered service or application and bring it fully online.

If you do not currently have Event Viewer open, see “Opening Event Viewer and viewing events related to failover clustering.” Review the event logs for information about all resources in this clustered service or application, and consider whether the following actions apply to your situation:

  • Confirm that resources are installed and configured correctly.
  • Confirm that dependencies are correctly configured for all resources in the clustered service or application. For more information, see “Viewing properties for a clustered resource.”
  • Confirm that any underlying services or other software are started and can run successfully.

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.

Viewing properties for a clustered resource

To view properties for a clustered resource:

  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 a clustered service or application.
  5. In the center pane, if you cannot see the clustered resource that you want to view, expand one or more visible resources until you see the clustered resource.
  6. Right-click the resource you want to view, and then click Properties.
  7. As needed, click tabs to view more resource properties. For example, for information about restart policies, click Policies, and for information about dependencies, click Dependencies.
  8. To see a diagram of the dependencies configured in the clustered service or application, click Cancel and then, in the Action pane, click Show Dependency Report. Scroll down in the report to see the diagram.

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.

Verify

Verify that the clustered service or application can come online, and observe whether additional events are logged regarding resources in the clustered service or application.

To perform the following 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.

To verify that a clustered service or application can come 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. Click the clustered service or application that you want to view. In the center pane, view the status of the clustered service or application and its associated resources. As needed, expand one or more visible resources until you see all the clustered resources you want to view.
  5. To bring a clustered service or application online, in the console pane, right-click it, and then click Bring this service or application online. You can observe the status of the associated clustered resources as the Cluster service attempts to bring them online.

Related Management Information

Clustered Service or Application Availability

Failover Clustering

Related:

Unable to open the network connection profile.

Details
Product: Windows Operating System
Event ID: 1205
Source: Kernel
Version: 5.0
Component: System Resources
Symbolic Name: ERROR_CANNOT_OPEN_PROFILE
Message: Unable to open the network connection profile.
   
Explanation

An application was trying to make, cancel, or view a network connection. Windows 2000 cannot carry out the request because the file it uses to remember network connections cannot be opened.

   
User Action

Contact your technical support group.

Related:

Failed to create the mailbox of {mailbox name} with error {error code}.

Details
Product: Exchange
Event ID: 1205
Source: MSExchangeIS Mailbox Store
Version: 6.0
Component: Information Store
Symbolic Name: msgidFailedCreateMailbox
Message: Failed to create the mailbox of {mailbox name} with error {error code}.
   
Explanation
An attempt to create a mailbox failed. Insufficient permissions, a Jet error, or a memory error may have caused the problem.
   
User Action
Try creating a mailbox again. Use the error returned to help determine a course of action. Review the event log for related entries.

Related:

While processing security descriptor propagation- the directory service found incorrect or missing object class information for %1 (error 0x%2). Propagation will not take place to children of this object.

Details
Product: Windows Operating System
Event ID: 1205
Source: Active Directory
Version: 5.0
Symbolic Name: DIRLOG_SDPROP_OBJ_CLASS_PROBLEM
Message: While processing security descriptor propagation- the directory service found incorrect or missing object class information for %1 (error 0x%2). Propagation will not take place to children of this object.
   
Explanation

This is an Active Directory internal event. Internal events appear in the Event Viewer only when the default logging level is changed. Most internal events are for informational purposes only. This event is logged when the security descriptor propagation task finds an incorrect or missing object class for the object specified in the message. Security descriptor propagation will not take place on this object’s child objects.

   
User Action

No user action is required.

Related:

Failed to create the mailbox of with error .

Details
Product: Exchange
Event ID: 1205
Source: MSExchangeIS
Version: 6.5.6940.0
Component: Microsoft Exchange Information Store
Message: Failed to create the mailbox of <mailbox name> with error <error code>.
   
Explanation

An attempt to create a mailbox failed. Insufficient permissions, a Jet error, or a memory error may have caused the problem.

   
User Action

Try creating a mailbox again. Use the error returned to help determine a course of action. Review the event log for related entries.

Related:

Failed to create the mailbox of %1 with error %2.

Details
Product: Exchange
Event ID: 1205
Source: MSExchangeIS Mailbox Store
Version: 8.0
Symbolic Name: msgidFailedCreateMailbox
Message: Failed to create the mailbox of %1 with error %2.
   
Explanation

This Error event indicates that a mailbox for the user account specified in the event description could not be created. This event may occur when moving the mailbox from one mailbox database to another mailbox database. One or more of the following conditions may occur.

  • The mailbox for this user already exists in the mailbox tombstone table.

  • The user account specified in the event description was deleted but the changes were not replicated to all the domain controllers in Active Directory.

  • There are logical corruptions in the database.

You may also see an Error event 1022 in the Application log.

   
User Action

To resolve this error, follow these steps:

  • If this error occurred during a move mailbox operation, make sure that the move was successful. If not, try to move the mailbox again. Make sure both the source and target mailbox database stores are in Mounted state.

  • If the mailbox was previously deleted, and it is still under retention period, reconnect the mailbox instead of recreating it. By default, the retention period for deleted mailboxes on Microsoft® Exchange Server 2007 is 30 days. You can see a list of disconnected mailboxes in Disconnected Mailbox container under Recipient Configuration in the Exchange Management Console.

  • Review other related Error and Warning events in the Application log. These related events may help you find the root cause of this error.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Transaction (Process ID %d) was deadlocked on %.*ls resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Details
Product: SQL Server
Event ID: 1205
Source: MSSQLServer
Version: 9.00.1281.60
Symbolic Name: LK_VICTIM
Message: Transaction (Process ID %d) was deadlocked on %.*ls resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
   
Explanation

Resources are accessed in conflicting order on separate transactions, causing a deadlock. For example:

  • Transaction1 updates Table1.Row1, while Transaction2 updates Table2.Row2.

  • Transaction1 attempts to update Table2.Row2 but is blocked because Transaction2 has not yet committed.

  • Transaction2 now attempts to update Table1.Row1 but is blocked because Transaction1 has not committed.

  • A deadlock occurs because Transaction1 is waiting for Transaction2 to complete, but Transaction2 is waiting for Transaction1 to complete.

The system will detect this deadlock and will choose one of the transactions involved as a ‘victim’ and will issue this message, rolling back the victim’s transaction. For more information about deadlocks, see Deadlocking in SQL Server 2005 Books Online.

   
User Action

Execute the transaction again. You can also revise the application to avoid deadlocks. The transaction that was chosen as a victim can be retried and will likely succeed, depending on what operations are being executed simultaneously.

To prevent or avoid deadlocks from occurring, consider having all transactions access rows in the same order (Table1, then Table2); this way, although blocking may occur, a deadlock will not occur. For more information about actions to take see “Detecting and Ending Deadlocks” in SQL Server 2005 Books Online.

Related: