Error message is displayed on upgrading APM IIS agent

Problem

When you upgrade Microsoft IIS agent along with Microsoft .NET agent, or when you upgrade only a single Microsoft IIS agent, the upgrade fails, and an error message is displayed.

Symptom

The following error message is displayed when you upgrade IIS agent, irrespective of single agent upgrade or multiple agent upgrades:

C:\IBM\APM\TMAITM6_x64\libcclog_64.dll The process cannot access the file because it is being used by another process. 0 file(s) copied.

Cause

In a single IIS agent upgrade, the DLL file, libcclog_64.dll, is used by IISCurrentExecutingReqs.exe for logging exceptions to the log file. Hence, the DLL file remains locked. Even when you stop all the IIS agent related services, the IISCurrentExecutingReqs.exe process remains in an active state for the next 5 minutes in the system.

In case of a multiple agent upgrade, where you upgrade IIS and .NET agents simultaneously, both IIS and .NET agents use the same DLL file, libcclog_64.dll, for logging exceptions to the log file. The libcclog_64.dll file is locked by .NET agent as it gets upgraded first.

Solution for single IIS agent upgrade

To resolve the issue, complete the following steps:
  1. Stop all the IIS agent services from IBM Performance Management.
  2. Wait for 3-5 minutes till IISCurrentExecutingReqs.exe process stops automatically or end the process manually from the task Manager window.
  3. Make sure that no other agent related services are in active state in the system, and then proceed for IIS agent upgrade.
    Note: The issue appears from APM V8.1.4.0.16 release onwards.

Solution for IIS and .NET agent upgrades

To resolve the issue, complete the following steps:
  1. Stop all the agent related services for IIS and .NET agents from IBM Performance Management.
  2. Make sure that no other agent related services are in active state in the system.
  3. Upgrade .NET agent first, and then stop .NET agent related services.
  4. Upgrade IIS agent.
  5. Start .NET agent related services.
    Note: The issue appears from APM V8.1.4.0.16 release onwards.