AppManager Windows Agent services are running, but MC Service is not listening on Port 9998.

  • 7014268
  • 10-Dec-2013
  • 10-Dec-2013

Environment

NetIQ AppManager Enterprise 8.x
NetIQ AppManager Enterprise 8.0.x
NetIQ AppManager Enterprise 7.0.x
NetIQ AppManager Windows Agent

Situation

The AppManager Windows Agent is running on a specific client server, but the NetIQ AppManager Client Resource Monitor Service (NetIQmc.exe) is not listening on Port 9998 as it is configured to.

Resolution

To correct this issue:
  1. Stop the NetIQ AppManager Client Resource Monitor (NetIQmc.exe) service on the affected server.
  2. "Clear and Save" all the Windows Event Logs on the agent server, one by one.
  3. Once all of the Windows Event Logs have been saved and cleared, re-start the NetIQmc.exe service on the server.
At this point, jobs should start automatically on the Agent, and the NetIQmc.exe service should be able to listen on Port 9998 as expected.

Cause

The most common cause for this type of behavior is if one or more of the Windows Event Logs have become corrupt on the affected server, which in turn causes a Windows Event Log monitoring job on the Agent (typically the General_EventLog KS) to work overtime, causing it to not release port 9998.