Hi all,
My WHS2011 Server (so not any of the clients) is throwing Computer Monitoring Errors very often. I posted about this at http://social.microsoft.com/Forums/en-US/c348ec16-3aed-4cf6-bdde-f8cbc6d0653b/computer-monitoring-error-on-server?forum=whs2011 but got no love there so far.
I have looked at past threads and not found a solution therein (it is, for instance, not related to the MacConnector (.MacClientUpdateCondition.Run(IActionContext context), http://support.microsoft.com/kb/2686857/en-gb)
It appears to be related to "ConnectivityFeature!", whatever that may be.
The Alert Viewer States:
"Some health evaluations did not complete. The imcomplete items are:
ConnectivityFeature!InternetConnectivity: ConnectivityFeature!CertificateMissing:
ConnectivityFeature!CertificateExpiredManualFlow;
ConnectivityFeature!CertificateExpiredAutomaticFlow;
ConnectivityFeature!CertificateNearExpirationManualFlow..."
From the logs, the only thing I could find that might be related is:
[10544] 140108.110533.4213: AlertFramework: Subcomponent: HealthEvaluator > Evaluation of Health Definition conditions is either hung or is taking a long time to execute
[10544] 140108.110533.4213: AlertFramework: Subcomponent: HealthEvaluator > EvaluateAlerts: Timed out Definitions are: ConnectivityFeature!InternetConnectivity ConnectivityFeature!CertificateMissing ConnectivityFeature!CertificateExpiredManualFlow ConnectivityFeature!CertificateExpiredAutomaticFlow ConnectivityFeature!CertificateNearExpirationManualFlow ConnectivityFeature!CertificateNearExpirationAutomaticFlow ConnectivityFeature!IisConfiguration ConnectivityFeature!TsGatewayConfiguration ConnectivityFeature!FirewallConfiguration DomainManagementFeature!DomainNameConfig DomainManagementFeature!DomainNameReady DomainManagementFeature!DomainNameExpire DomainManagementFeature!DomainNameNearlyExpire DomainManagementFeature!DomainNameProviderCredentials DomainManagementFeature!DDNSUpdate DomainManagementFeature!LiveSignInAssistantExists MicrosoftMedia!WmpAxHostTask MicrosoftSecurity!WindowsUpdateDisabled MicrosoftSecurity!WindowsUpdateMissing MicrosoftSecurity!WindowsUpdateRestart ServerBackupFeature!LowSpaceOnTargetDisk ServerBackupFeature!TaskPausingOverdue MicrosoftServicing!MUOptIn MicrosoftServicing!MacClientUpdate
[10544] 140108.110533.4233: Notifications: Information: [0] : LNx01: Source SNx03 fired a one-shot:
Notification Category: NetworkHealthAlerts
Id: Raise
Source: notifier:SharedServiceHost.exe:p3580:mt4:1
[10544] 140108.110533.4253: DevicesProvider: DevicesBackend.CallProxyOneWay: Error happened: System.ServiceModel.ProtocolException: This channel can no longer be used to send messages as the output session was auto-closed due to a server-initiated shutdown. Either disable auto-close by setting the DispatchRuntime.AutomaticInputSessionShutdown to false, or consider modifying the shutdown protocol with the remote server.
Server stack trace:
at System.ServiceModel.Channels.ServiceChannel.PrepareCall(ProxyOperationRuntime operation, Boolean oneway, ProxyRpc& rpc)
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.WindowsServerSolutions.Common.Devices.IDevicesProvider.ReportDevicePropertiesOneWay(String deviceId, IEnumerable`1 properties)
at Microsoft.WindowsServerSolutions.Common.Devices.DevicesBackend.CallProxyOneWay(Action`1 action, Action`2 callback)
[10544] 140108.110533.4253: AlertFramework: Subcomponent: DevicesManagerFacade > ReportDevicePropertiesAsync failed: DeviceId=S-1-5-21-4142299911-2264946761-488892081-1010 Error=Microsoft.WindowsServerSolutions.Common.Devices.DevicesProviderException: This channel can no longer be used to send messages as the output session was auto-closed due to a server-initiated shutdown. Either disable auto-close by setting the DispatchRuntime.AutomaticInputSessionShutdown to false, or consider modifying the shutdown protocol with the remote server. ---> System.ServiceModel.ProtocolException: This channel can no longer be used to send messages as the output session was auto-closed due to a server-initiated shutdown. Either disable auto-close by setting the DispatchRuntime.AutomaticInputSessionShutdown to false, or consider modifying the shutdown protocol with the remote server.
Server stack trace:
at System.ServiceModel.Channels.ServiceChannel.PrepareCall(ProxyOperationRuntime operation, Boolean oneway, ProxyRpc& rpc)
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.WindowsServerSolutions.Common.Devices.IDevicesProvider.ReportDevicePropertiesOneWay(String deviceId, IEnumerable`1 properties)
at Microsoft.WindowsServerSolutions.Common.Devices.DevicesBackend.CallProxyOneWay(Action`1 action, Action`2 callback)
--- End of inner exception stack trace ---
I would really like to get rid of this so that I can reasonably enable e-mail alerts. Anyone else getting this message? Any help would be appreciated.
Kind rgds,
Umf
(Apologies for the long post).