Quantcast
Channel: Operations Manager - General forum
Viewing all articles
Browse latest Browse all 11941

Service Control Manager -- Event ID 7046 Network Location Awareness - Stopped Watcher Node Functioning

$
0
0

Hi All,

I am trying to debug an Issue with a Watcher Node Machine which was unable to communicate to Other Machine post the Event 7046 was logged on this Server... SCOM Monitoring for this Server did not alert us... Infact SCOM was able to ping to the Server & Agent Status was also Healthy on SCOM Console...But the Agent is supposed to Run some Check for other Monitor which was not Working well  ….All the Check stopped due to this Event.<o:p></o:p>

The Machine which had this problem function as a Monitoring Watcher Node with SCOM 2012
Agent with 2012 OS. All the Monitor were Showing Green during this Period outage,
while actually there was no Check done due to this Issue. We Faced an Outage
which went unmonitored for 2 days because of this problem. <o:p></o:p>

Can somebody suggest how do we avoid this kind of Issue or if there is any Know Bug for this Issue.<o:p></o:p>

Following is the Event Logged on this Server Post this Event Every Monitor Stopped
Running from this Watcher Node Expect the Heartbeat:<o:p></o:p>


Prior to the Above Event we had as Series of Stopped Event --with timeout Error for event ID 7011

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CryptSvc service. -- 4/18/2014 9:42:19 AM
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Dnscache service. -- 4/18/2014 9:42:49 AM
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the LanmanWorkstation service. -- 4/18/2014 9:43:19 AM
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the NlaSvc service. -- 4/18/2014 9:43:49 AM
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Wecsvc service. -- 4/18/2014 9:44:19 AM
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WinRM service. -- 4/18/2014 9:44:49 AM
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CryptSvc service. -- 4/18/2014 9:46:19 AM
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Dnscache service. -- 4/18/2014 9:46:49 AM
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the LanmanWorkstation service. -- 4/18/2014 9:47:19 AM

There was Critical Event Prior to this 10 min ago as Below.  SCOM Monitoring was not Functional since this Event was Logged with Time-Stamp of 9:34 AM Onward No Monitor was Reported from this server to SCOM, however the Server HB was Sent to SCOM to show it availability in the SCOM Console.

Regards,

Jason Aranha


Jason Aranha


Viewing all articles
Browse latest Browse all 11941

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>