Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Agent doesn't communicate with server - problem

869 views
Skip to first unread message

Rem-8

unread,
Feb 1, 2008, 6:43:21 AM2/1/08
to
I'm installing multiple agents on many computers and on one of them
there's a problem that state stays empty. There are lots of errors in
Event Viewer on the agent side like this:

Event Type: Information
Event Source: OpsMgr Connector
Event Category: None
Event ID: 21023
Date: 2008-02-01
Time: 12:38:17
User: N/A
Computer: OVIS
Description:
OpsMgr has no configuration for management group BROWN and is
requesting new configuration from the Configuration Service.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: OpsMgr Connector
Event Category: None
Event ID: 21041
Date: 2008-02-01
Time: 12:38:17
User: N/A
Computer: OVIS
Description:
Operations Manager has received a bad configuration file for
management group BROWN 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\BROWN
\OpsMgrConnector.Config.Error.xml

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: OpsMgr Connector
Event Category: None
Event ID: 21027
Date: 2008-02-01
Time: 12:38:17
User: N/A
Computer: OVIS
Description:
OpsMgr has received configuration for management group BROWN 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)

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Can it be the OVIS application problem? How can I start receiving good
configuration?

Rem-8

unread,
Feb 1, 2008, 6:56:45 AM2/1/08
to
Well, this is no OVIS problem as we stopped it and it is still the
same

Config and SDK Services run as LocalSystem
Agent run as LocalSystem or Local Admin account (we tried both)
Computers are in the same domain, installation went successfull from UI

Rem-8

unread,
Feb 6, 2008, 10:56:04 AM2/6/08
to


Hello. Has anyone confirmed this bug? I've tried everything and it is
still receiving a bad configuraion. Repair, Manual Installation -
nothing helped. Ports are both open.

Vince_Poi

unread,
Apr 9, 2008, 2:14:01 PM4/9/08
to
Hi
I’ve got the same problem with one of my computer.

I’ve solved the problem by reinstalling MSXML6 on the agent side. (MSXML6 is
included with SCOM installation files)

NB: MSXML6 is (normally) automatically installed when agent is deployed. But
it was not the case with that computer.

I hope that will be helpful for you

Vince_Poi

T103988

unread,
Apr 10, 2008, 9:33:00 AM4/10/08
to
Thank you! This solved my problem. I actually had to uninstall, reinstall,
and then run a repair before it started working. However, the repair may not
have been necessary. I did a repair and then restarted the OpsMgr Health
Service. If I had restarted the service after reinstalling XML, it may have
started working. Thanks, Vince.

stevet

unread,
Aug 4, 2009, 11:21:01 AM8/4/09
to
I had the same problem with SCOM 2007 R2. Installing MSXML6.msi solved the
problem.
--
SteveT

Korbee

unread,
Dec 17, 2009, 7:37:01 AM12/17/09
to
Thanx,

Repair of MSXML 6.0 SP2 worked for me too.
Solved the unresponsive SCOM 2007 R2 agent.

Marcel

Kobile

unread,
Dec 19, 2009, 5:32:01 AM12/19/09
to
Hi,

i had the same problem but MSXML didnt solve my problem.

my problem was with RMS,
http://kobile.spaces.live.com/blog/cns!EC0CAF63D41E5082!198.entry

BrianW

unread,
Apr 14, 2010, 1:25:01 PM4/14/10
to
MSXML6 was the problem for me on SCOM R2.

B-

Mihir Patel

unread,
Nov 9, 2022, 12:31:42 PM11/9/22
to
How did you reinstalled MSXML6 on the agent side?
Thanks!
0 new messages