Communication between a System Center Operations Manager 2007 Gate...

http://support.microsoft.com/kb/2004886

Article ID: 2004886 - Last Review: November 16, 2009 - Revision: 2.0

Communication between a System Center Operations Manager 2007 Gateway Server and Management Server fails when the Agent is installed on the Gateway Server

A System Center Operations Manager 2007 Gateway Server may have problems communicating with its Management Server. You may also see the following events on the Gateway Server: Log Name: Operations Manager Source: OpsMgr Connector Date: <date><time> Event ID: 21016 Task Category: None Level: Error Keywords: Classic User: N/A Computer: <gateway-server> Description: OpsMgr was unable to set up a communications channel to <gateway-server> and there are no failover hosts. Communication will resume when <gateway-server> is available and communication from this computer is allowed. Log Name: Application Source: MsiInstaller Date: <date><time> Event ID: 11707 Task Category: None Level: Information Keywords: Classic User: <user> Computer: <gateway-server> Description: Product: System Center Operations Manager 2007 R2 Agent -- Installation operation completed successfully.

This can occur if the System Center Operations Manager 2007 Agent is installed on the Gateway Server computer.

To resolve this issue, follow the steps outlined below: 1. When you try uninstalling the Agent using Add/Remove Programs it will likely fail. If so then we will need to remove the following registry keys manually: HKLM\Software\Microsoft\Microsoft Operations Manager HKLM\System\CurrentControlSet\Services\HealthService 2. Go to HKCR\Installer\Products and delete both GUID reg keys that have a Product Name of SCOM Agent and SCOM Gateway. 3. Go to HKCR\Installer\UpgradeCodes and delete the GUID reg keys under HKCR\Installer\UpgradeCodes within which we

1 of 2

3/2/2010 09:45

Communication between a System Center Operations Manager 2007 Gate...

http://support.microsoft.com/kb/2004886

see the GUIDs we deleted in step #3 above. Note: The exact GUID referenced in steps 3 and 4 above will vary. 4. Rename the SCOM folder in both Program Files and Program Files (x86) folders. 5. Reboot the Gateway Server to make sure everything for SCOM is cleaned from the system. 6. Run the Operations Manager 2007 Gateway setup. It should complete successfully. 7. Run the MOMCertImport tool on the Gateway Server to import the certificate that is already present for this gateway on the server. At this point the gateway will start communicating with its Management server and also show state as Green and Healthy. After a few moments all of the agents behind the gateway will became Green and Healthy as well. The event below will confirm that the gateway is now working properly: Log Name: Operations Manager Source: OpsMgr Connector Date: <date><time> Event ID: 21026 Task Category: None Level: Information Keywords: Classic User: N/A Computer: <gateway-server> Description: OpsMgr has received confirmation for management group <mgmt-group-name> from the Configuration Service that our existing configuration is up-to-date. The current state cookie is "99 B1 5E FD C0 64 61 A1 14 C9 68 D8 AD 11 2F 04 5C F1 1C 6A " Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.

APPLIES TO
Microsoft System Center Operations Manager 2007 R2 Microsoft System Center Operations Manager 2007 Service Pack 1 Microsoft System Center Operations Manager 2007

Keywords: kbrapidpub kbnomt KB2004886

Get Help Now

Contact a support professional by E-mail, Online, or Phone

Microsoft Support

2010 Microsoft

2 of 2

3/2/2010 09:45