The NetIQ AppManager Client Resource Monitor service will start and then stop.
- Make sure both the agent services (Client Resource Manager, Client Communication Manager) are stopped and disabled on the machine.
- Open Task Manager
- Find the NQPerfprovider4.exe process
- Choose End Task
- If multiple copies of this process are still running, repeat Steps 3 & 4 for each running NQPerfprovider4.exe process.
- If the task does not stop after a few minutes restart the machine, but make sure both the NetIQ Agent services are disabled before doing so (to prevent them from auto-starting after the reboot completes).
- After the restart please re-apply the latest WinOS module.
Once those steps are completed, you can re-enable both of the NetIQ AppManager Agent services, and start them up. Both services should now run normally.
In the WinOS_Install.log you will see the following:
1299250116 Copying NQPerfProvider4_x86.exe to c:\Program Files\NetIQ\AppManager\bin\NQPerfProvider4.exe
1299250116 Executing: "c:\Program Files\NetIQ\AppManager\bin\NQPerfProvider4.exe" /RegServer
1299250116 Process created - [last error was 0]
1299250116 Utility::RunProcess - Returning exit code from process = 0
During a failure it will not be able to copy the file and will indicate an error while performing the copy.
You can further verify this condition by checking the NQPerProvider4.exe version and comparing against the qdotneta4.dll. If the NQPerfProvier4.exe version is older than the qdotneta4.dll version, the Windows OS Module upgrade was unsuccessful.