I have a single SCOM R2 server running on Windows 2008 SP2 64bit. And the SQL server runs on a different Windows 2008 SP2 64bit server. The SQL server is SQL 2008 SP1 64bit. The domain is running at Windows 2008 mode and the DCs are all running Windows 2008 R2. After instilling CU3 on the SCOM 2007 R2 server. I get the following alert The root management server (HealthService) is running but has reported limited functionality soon after 10/11/2010 2:30:14 PM. The specific reason code is 43 and description is " System workflows essential to running of the product have failed to load. ". The SCOM 2007 R2 server is also running with very high CPU utilization. I disable all non-essential services but no change i would appreciate any help.

Hi, Please check if the suggestions on the following links will work: increased the size od the OpsMgr database: http://social.technet.microsoft.com/forums/en-US/systemcenter/thread/5006fef6-32d0-4962-ab6a-f8f5f9720f56 added the SCOM worker accounts to the local admin group: http://movement3.wordpress.com/2009/08/10/scom-alert-root-management-server-unavailable/Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Carl, Check if: 1. All OpsMgr services is running on RMS 2. any other errors in eventlog on RMS?http://OpsMgr.ru/

Carl, Have you run the SQL update scripts from the CU3 install? Kevin Holman has a good article on installing CU3: http://blogs.technet.com/b/kevinholman/archive/2010/10/04/opsmgr-2007-r2-cu3-rollup-hotfix-ships-and-my-experience-installing-it.aspx MattMatt White ( http://systemcenterblog.hardac.co.uk/ )

I'd be interested in what other critical and warning events are showing up on your RMS OpsMgr event log.