Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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.

↑ Back to the top


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.

↑ Back to the top


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.

↑ Back to the top


Keywords: vkball, kb

↑ Back to the top

Article Info
Article ID : 2262476
Revision : 1
Created on : 1/8/2017
Published on : 7/1/2010
Exists online : False
Views : 116