Microsoft Knowledge Base Email Alertz

Attempts to opening the System Center Operations Manager 2007 console fails with The client has been disconnected from the server exception

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 2262476 - Last Review: July 1, 2010 - Revision: 1.0

Attempts to opening the System Center Operations Manager 2007 console fails with "The client has been disconnected from the server" exception

Symptoms

When you attempt to open the System Center Operations Manager 2007 console it may fail with the following exception:

===========================================================================================
Date:    -
Application: System Center Operations Manager 2007 R2
Application Version: 6.1.7221.0
Severity: Warning
Message:

Microsoft.EnterpriseManagement.Common.ServerDisconnectedException: The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection. ---> System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

Server stack trace:
   at System.ServiceModel.Channels.CommunicationObject.ThrowIfFaulted()
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.EnterpriseManagement.Common.ITypeSpaceDataAccess.GetNotificationActions(String languageCodes)
   at Microsoft.EnterpriseManagement.DataAbstractionLayer.TypeSpaceOperations.GetNotificationActions(String languageCodes)
   --- End of inner exception stack trace ---
   at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.HandleIndigoExceptions(Exception ex)
   at Microsoft.EnterpriseManagement.DataAbstractionLayer.TypeSpaceOperations.GetNotificationActions(String languageCodes)
   at Microsoft.EnterpriseManagement.ManagementGroup.GetNotificationActions()
   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.Administration.MomRequiredConfigService.<>c__DisplayClass3.<UpdateNotificationChannelStatus>b__0(Object , ConsoleJobEventArgs )
   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)
System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
===========================================================================================

In some instances the console will open but the exeption will be thrown when trying to select any node.  Operations Manager consoles hosted on remote workstations will also exhibit similar behavior.  Attempts to open the Operations Manager command shell will time out and no cmdlet using the Operations Manager provider will return data.

Cause

This can occur if the communication channel to the OperationsManager database from the System Center Data Access Service (SDK service) is failing due to a protocol error.

Resolution

This issue has been resolved by applying the hotfix described in Knowledge Base article KB931319 to the Root Management Server.  A reboot of the RMS is required after applying the hotfix.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.

APPLIES TO
  • Microsoft System Center Operations Manager 2007 R2
  • Microsoft System Center Operations Manager 2007 Service Pack 1
  • Microsoft System Center Operations Manager 2007
Keywords: 
KB2262476
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate