Discussion:
SCOM g/w installed but listed as 'not monitored'
(too old to reply)
unknown
2010-02-03 14:43:18 UTC
Permalink
Hi All,



I'm using SCOM to manage several networks in a WAN and all but one of these have installed and recognised the g/w.

The g/w shows up in SCOM as a Management Server but with a 'not monitored' ststus.

The g/w server is in a hosting facility where I don't have domain admin access and initially the MOMCertimport failed but I believe I resolved it with the s/n input via registry editor.

After restarting the health service on g/w I get the following errors.

20057 (repeats in eventvwr periodically after)

21001 (repeats in eventvwr periodically after)

21016

21006

(all listed in full below)



Would anyone have any ideas on where I'm going wrong with this?



Any help would be greatly appreciated,

Thanks in advance,

Ben.



20057

Failed to initialize security context for target MSOMHSvc/scom.dom.com The error returned is 0x80090303(The specified target is unknown or unreachable). This error can apply to either the Kerberos or the SChannel package.



21001

The OpsMgr Connector could not connect to MSOMHSvc/scom.dom.com because mutual authentication failed. Verify the SPN is properly registered on the server and that, if the server is in a separate domain, there is a full-trust relationship between the two domains.



21016

OpsMgr was unable to set up a communications channel to scom.dom.com and there are no failover hosts. Communication will resume when scom.dom.com is available and communication from this computer is allowed.



21006

The OpsMgr Connector could not connect to scom.dom.com:5723. The error code is 10061L(No connection could be made because the target machine actively refused it.). Please verify there is network connectivity, the server is running and has registered


Submitted via EggHeadCafe - Software Developer Portal of Choice
SqlWebAdmin Redux: Rebuilt for ASP.NET 2.0
http://www.eggheadcafe.com/tutorials/aspnet/61c487c6-5817-44aa-8184-4b34a12cab89/sqlwebadmin-redux-rebuil.aspx
Murad Akram
2010-03-19 18:56:08 UTC
Permalink
Ben,
I assume you ran the "Microsoft.EnterpriseManagement.GatewayApprovalTool.exe
" utility on your Management server to approve your gateway server already?
What it successfully aproved? Also can you verify is the following message
showed up in the event logs of the Gateway server?

Log Name: Operations Manager
Source: OpsMgr Connector
Date: 1/27/2010 3:23:03 PM
Event ID: 20053
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: GWservername.cust.yourdomainname.com
Description:
The OpsMgr Connector has loaded the specified authentication certificate
successfully.
--
Murad Akram
Post by unknown
Hi All,
I'm using SCOM to manage several networks in a WAN and all but one of these have installed and recognised the g/w.
The g/w shows up in SCOM as a Management Server but with a 'not monitored' ststus.
The g/w server is in a hosting facility where I don't have domain admin access and initially the MOMCertimport failed but I believe I resolved it with the s/n input via registry editor.
After restarting the health service on g/w I get the following errors.
20057 (repeats in eventvwr periodically after)
21001 (repeats in eventvwr periodically after)
21016
21006
(all listed in full below)
Would anyone have any ideas on where I'm going wrong with this?
Any help would be greatly appreciated,
Thanks in advance,
Ben.
20057
Failed to initialize security context for target MSOMHSvc/scom.dom.com The error returned is 0x80090303(The specified target is unknown or unreachable). This error can apply to either the Kerberos or the SChannel package.
21001
The OpsMgr Connector could not connect to MSOMHSvc/scom.dom.com because mutual authentication failed. Verify the SPN is properly registered on the server and that, if the server is in a separate domain, there is a full-trust relationship between the two domains.
21016
OpsMgr was unable to set up a communications channel to scom.dom.com and there are no failover hosts. Communication will resume when scom.dom.com is available and communication from this computer is allowed.
21006
The OpsMgr Connector could not connect to scom.dom.com:5723. The error code is 10061L(No connection could be made because the target machine actively refused it.). Please verify there is network connectivity, the server is running and has registered
Submitted via EggHeadCafe - Software Developer Portal of Choice
SqlWebAdmin Redux: Rebuilt for ASP.NET 2.0
http://www.eggheadcafe.com/tutorials/aspnet/61c487c6-5817-44aa-8184-4b34a12cab89/sqlwebadmin-redux-rebuil.aspx
.
Loading...