OpsMgr 2007: Files and Folders starting with "Program" causing unmonitored Agent

Article ID: 969596 - View products that this article applies to.
Expand all | Collapse all

On This Page

Source: Microsoft Support

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Symptom



The Operations Manager Service Pack 1 (SP1) Agent or Management Server may be shown as greyed out in the Operations Manager console and the following events may be logged in the event log:

Event ID: 10000
Source: DCOM
Description: Unable to start a Dcom Server: {<GUID>}. The error: <error
description>
Happened while starting this command: <command> -Embedding
regarding monitoring host

-and-

Event Type: Error
Event Source: HealthService
Event Category: Health Service
Event ID: 1102
Description: Rule/Monitor
"Microsoft.SystemCenter.DiscoveryHealthServiceCommunication" running for instance
"<computer fqdn name>" with id:"{38696FAA-2A83-6068-B008-DB43D49FB879}" cannot be
initialized and will not be loaded. Management group "<management group name>"

Cause

Computers having files or folder that start with "Program" on the root drive may not be monitored. All workflows fail when file "c:\Program" is present on the machine. This happens because HealthService.exe is unable to start MonitoringHost.exe.

Resolution

Update Information

To resolve this problem, obtain the latest version of Microsoft System Center Operations Manager 2007. For more information, refer to this Microsoft Web site: http://www.microsoft.com/systemcenter/operationsmanager/en/us/how-to-buy.aspx

Workaround Information

To resolve this issue, delete or rename the file or folder named Program on the affected computer.

MORE INFORMATION

For a list of issues that are fixed in Microsoft System Center Operations Manager 2007 R2, refer to the following article in the Microsoft Knowledge base:
971410 List of issues that are fixed in System Center Operations Manager 2007 R2

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Properties

Article ID: 969596 - Last Review: March 27, 2009 - Revision: 1.1
APPLIES TO
  • Microsoft System Center Operations Manager 2007 Service Pack 1
Keywords: 
kbrapidpub kbnomt KB969596

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com