Microsoft have released a hotfix to resolve the bogus “Computer Monitoring Error” issue that some users have encountered after their servers updated to the UR2 release. The hotfix is not available for direct download, you’ll need to click the “View and Request Hotfix Downloads” link to email support for the hotfix. If you’ve experienced the issue, let us know how the fix works for you.
Below are the links to the specific KB Articles for each platform and an overview of the issue for Windows Home Server 2011.
After you updated a server that is running Windows Home Server 2011 with the Update Rollup 2 for Home Server 2011, you receive the warning “Computer Monitoring Error” in the Home Server 2011 Launchpad or Dashboard. You receive this warning every 30 minutes.
This happens after the system installs Update Rollup 2. You find the following exceptions in the SharedServiceHost-AlertServiceConfig.log file.
120222.003152.9814: NetworkHealthEngine: Exception happened in Microsoft.WindowsServerSolutions.NetworkHealth.Engine.BinaryActionDefinition: System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.WindowsServerSolutions.Servicing.Alerts.MacClientUpdateCondition.Run(IActionContext context)
Additionally, this can occur when you have removed a previously connected network computer from the server.
The log file is located in the following folder:
You do not receive a warning reminding you to update your Mac client connector. There is no effect on other alerts or product features.
This occurs when one of the Alert evaluation components in Home Server 2011 tries to iterate through the records of all client computers in the network. It throws an unhandled exception when the component accesses the record of a client computer that was removed.