Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
|Source: Microsoft Operations Manager|
The agent could not connect to the MOM Server <server name>. The error reported is '<error>'. Verify the management group name is correct, the MOM Server is running, that it is listening on port 1270, and that any firewalls between this agent and the MOM server are configured to pass TCP and UDP traffic on port 1270.
|English: Request a translation of the event description in plain English.|
According to Microsoft if a Microsoft Operations Manager (MOM) 2005 agent cannot communicate with a MOM 2005 Management Server, the MOM 2005 agent may experience a deadlock situation. This symptom occurs if the MOM 2005 Management Server shuts down or the network communication between the MOM 2005 agent and the MOM 2005 management server is unavailable. The deadlock situation occurs while the MOM 2005 agent is trying to clear the MOM 2005 agent queue after the communication is restored. See ME902447 for a hotfix applicable to Microsoft Operations Manager (MOM) 2005.
This event also occurs after a MOM 2005 agent tries to fail over to the secondary MOM 2005 server. See ME934441 for a hotfix applicable to Microsoft Operations Manager (MOM) 2005.
- Error: "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond" - See ME885726 for a workaround on this problem.
|Private comment: Subscribers only. See example of private comment|
|Links: ME885726, ME902447, ME934441|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated