Jobs and reports run successfully, but do not show up as Stopped in the Operator Console. (NETIQKB41155)

Jobs and reports run successfully, but do not show up as Stopped in the Operator Console.

Jobs appear to continue running in the Operator Console, even when RPLib.log shows that the jobs have completed successfully.

Reports appear to continue running in the Operator Console, even when the RPLib.log shows that the reports have completed successfully.

Creating a second Report Agent system, and running reports through that agent results in the same issue.

Some reports being run against a specific Agent system will not contain any data, even though you can confirm that data is being collected and the report is being run successfully.

In order to resolve this problem, please perform the following steps:

1. Stop the NetIQmc and NetIQccm services on the Agent system that the jobs/reports are running against.  
2. In Windows Explorer, drill down to the \AppManager\dat\Mapque directory and delete all files within this directory (there will only be a few). 
3. Restart the NetIQmc and NetIQccm services on this system, using the -o switch in the Start parameters option box. 

The NetIQmc service will create a single new cache file.

Jobs and Reports may need to be manually stopped and restarted, but should now stop correctly in the Operator Console when they are done running.  Newly run reports should now all contain data.

This situation occurs if the Mapque cache file is corrupt or there are duplicate Mapquecache files in the ...\AppManager\dat\Mapque directory on the Agent system that the jobs or reports are being run against.

When the Mapque cache file is corrupt or when there are more than one cache file in the Mapque directory, the NetIQmc and NetIQccm services can not properly communicate with each other on an Agent system.  This can result in jobs and reports not being properly shown as "Stopped" in the Operator Console, even after they have been properly completed on the Agent that they are running against.

Formerly known as NETIQKB41155

More information on Cold Starting an AppManger Agent please review the following.:

NETIQKB86

For more information on what happens when Cold Starting an AppManager Agent and the different options please review the following.

NETIQKB20149