NetIQ AppManager 7.0.x
Jobs Stuck in Pending State
To correct this issue, please install an AppManager Agent and the AppManager for Microsoft Windows Module on the target system. If, once the Agent and WinOS Module have been installed on the target system, you see tha thte jobs are still stuck in a Pending-Start state, you can correct this issue by performing a Cold-Start of the NetIQ AppManager Client Resource Monitor service on the target Server. To do so, complete the following steps:
- Log onto the target system using an account that has Local Administrator rights.
- Launch the Services application in Administrative Tools (Start -> Run -> Services.msc).
- Double-click the NetIQ AppManager Client Resource Monitor Service.
- In the Properties window, click Stop.
- In the Start Parameters field below the Service Status, type: -o ("o" as in Oscar).
- Click Start.
- Click OK.
Discovery jobs should now start, run, and complete as expected.
The Server was added to the NetIQ AppManager Operator Console using the Add Computer... tool with the "Discover Windows objects automatically" option enabled, before the AppManager Managed Client (Agent) was installed on that system. This option will force a job to be created, even if the target system has no Agent installed. As a result, the Discovery jobs are trying to run against a server that has no Agent installed on them and are thus stuck in a Pending-Start mode.
The Cold-Start option clears any Job information stored in the Local Repository (Local-Repository.mdb) on the target Server. If there are any Jobs running against this target Server (displayed in the AppManager Operator Console in a Running status), the cold-start may cause these Jobs to stop and may generate an Event message with a "MC Can't Locate Job" error. If this should occur, simply restart the Jobs in question to populate the Job information back to the Local Repository of the affected Agent(s).