System Center operations Manager logo http://www.Oostdam.infoSystem Center Operations Manager 2007 R2 is a great product. It has some difficulties, but doesn't have any products have a problem here and there? Now this article has been made here, for several reasons. First of all, I collected all these errors, installs, hits, tips and warnings for my own personal reference. But, it is always better to share knowledge, so I decided to publish these articles, with a little extra explanation on this site, through these articles. So, I hope this article will help you with your problem as well. Now, this article is about an error that I ran into several times now. Today I found one again and decided to publish it. 

The problem is that an agent managed computer no longer responses to requests and you are unable to un-/re-/install the agents client from a management server. Until know, I have seen this on windows 2003 servers only. I know that OS is no longer officially supported, but there are still a lot of them in production environments, thats one of the direct reasons for this article. Due to the fact that most visitors of this page are from a lot of different countries, this article is in the english language.

Events on an SCOM 2007 R2 agent managed Windows 2003 server:
Below is a picture of the set of events that you have seen in the events, otherwise you would not read this page. The agent has been working correctly earlier, even for a couple of months, but suddenly, it went grey in all the views and reports. As far as I can track it down, no changes, or (de-)installations has been on these machines. But somewhere that must have happend, as you can read in the solution.  So, underneath the 3 events as they show up in the Operations Manager Eventlog.

We are starting with the bottom event, as thats the first one logged.

Event ID 21041 details/description:
Source:      OpsMgr Connector
Category:    None
Description: Operations Manager has received a bad configuration file for management group [scomgroupname] which could not be parsed. Configuration has been re-requested. A copy of the bad configuration file will be placed in C:\Program Files\System Center Operations Manager 2007\Health Service State\Connector Configuration Cache\[scomgroupname]\OpsMgrConnector.Config.Error.xml
OpsMgr Connector Event 21041

This is the actual error, indicating that the received configuration file, cannot be locally parsed.

Event ID 21027 details/description:
Source:      OpsMgr Connector
Category:    None
Description: OpsMgr has received configuration for management group [scomgroupname] from the Configuration Service, but failed to process the configuration. Configuration will be re-requested. The current state cookie is ""(State cookie may be empty if there is no active configuration)
OpsMgr Connector Event 21027

This event is actually saying that the cookie is "". Which means empty, or not loaded.

Event ID 21023 details/description:
Source:      OpsMgr Connector
Category:    None
Description: OpMgr has no configuration for management group [scomgroupname] and is requesting new configuration from the Configuration Service.
OpsMgr Connector Event 21023

This event triggers a new request, is keeping the primary management server rather busy, and using unnecessarily use of bandwidth on your network. 

This set of events occurs every 7 to 8 seconds and is filling up your eventlog rather quickly, but the solution it pretty simple,
took me some time and investigation, but once you know, its really simple.

Solution to this set of errors:
If this is a terminal- or citrix server, make sure that all users are logged of. Repair or re-install the msxml6 xml parser which is needed for a correct working of the SCOM 2007R2 agent. You can download it, but this msi is also present on the SCOM 2007 R2 installation media and also on the agent directories on you (RMS) management servers.
By default the location is C:\Program Files\System Center Operations Manager 2007\AgentManagement then browse to the correct agent directory.
Make sure you'll install the correct MSXML6.MSI as the amd64, ia64 and x86 version are all different.

Hope that this article will have helped you a bit further............ 
Have fun, using System Center Operation Manager R2!

Ben OostdamBen Oostdam has been working with Windows systems since 1993. Worked for several companies as a system administrator, and is currently a Senior Support Engineer for Qurius Customer Care in the Netherlands, specialized in System Center Solutions.

Disclaimer: The information contained in this website/article is for general information purposes only. The information is provided as is, by Ben Oostdam and others, and while we endeavour to keep the information up to date and correct, we make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability or availability with respect to the website or the information, products, services, or related graphics contained on the website for any purpose. Any reliance you place on such information is therefore strictly at your own risk. In no event will we be liable for any loss or damage including without limitation, indirect or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or profits arising out of, or in connection with, the use of this website. Through this website you are sometimes able to link to other websites which are not under my control. I have no control over the nature, content and availability of those sites. The inclusion of any links does not necessarily imply a recommendation or endorse the views expressed within them. Every effort is made to keep the website up and running smoothly. However, I take no responsibility for, and will not be liable for, the website being temporarily unavailable due to technical issues beyond our control. All entries in these articles, are my individual opinion, or from co-writers, and they don't necessary reflect the opinion of my employer.


Friday the 7th, May 2021. All rights reserved.. // Oostdam WebDesign