IBM Support

WASServiceMsg.dll is locked when installing WebSphere Fix Packs and cumulative fixes on Windows

Troubleshooting


Problem

The WASServiceMsg.dll file is locked by the Microsoft Windows operating system and cannot be updated during the upgrade of WebSphere Application Server.

Symptom

If the WebSphere Application Server is defined as a service on Microsoft Windows, the following errors can occur during installation or removal of the WebSphere software.

Unable to open destination file: <path>\WASServiceMsg.dll 
Failed to delete: <path>\WASServiceMsg.dll

During an uninstall or fix pack installation, the WASServiceMsg.dll file can be in use by some non-WebSphere code such as the Windows event viewer. If the module is loaded in memory, the file cannot be removed or replaced. The uninstall or installation process fails.

Resolving The Problem

If you have WebSphere Application Server running as a service to start automatically, change the startup type to manual. Reboot the machine and retry the installation.

If you do not have the WebSphere Application Server service set to start automatically, reboot your machine to release locked resources. Retry the installation.

If the software is being uninstalled before a reinstallation, reboot the machine after the uninstall to ensure modules are unloaded properly.

Reboot the system and shut down the Windows Management Instrumentation software. Do not open the Windows Event Viewer. Retry the installation.

The WASServiceMsg.dll module is locked when the Windows Event Viewer (or third-party tools that provide a similar function) is browsing the Windows event log. If the installation continues to have issues with the WASServiceMsg.dll file, shut down the Windows Event Viewer and other services that monitor the Windows event log.

If the Installation Manager continues to fail due to this DLL file, and all WebSphere processes and third-party utilities that open the Windows event log are stopped, then try this alternative solution:
  1. Close or Exit the Installation Manager.
  2. Locate the WASServiceMsg.dll file, which is in the WAS_HOME\bin directory.
  3. Rename WASServiceMsg.dll to a different file name. It is good practice to rename the file to a name that contains the current WebSphere version. That way, you can easily distinguish this renamed file from other files, and you know that it belongs to a particular version of the product.

    For example, if you are using WebSphere Application Server v8.5.5.17, then rename the file to WASServiceMsg.dll.85517

    Although the file is locked, the operating system allows the file to be renamed.
  4. Reboot the system. The reboot is necessary to ensure the file is no longer locked.
  5. Using the Installation Manager, reinstall the WebSphere fix pack. Since the module was renamed, there is no longer any conflicts. The fix pack installation provides a new copy of the WASServiceMsg.dll file.
  6. Optional: You can delete the old, renamed copy of WASServiceMsg.dll. Do not delete the actual WASServiceMsg.dll file. Delete the copy of the file that was renamed in step 3).

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"ARM Category":[{"code":"a8m50000000CdXCAA0","label":"Install Update or Migration->Traditional WAS->Fixpack Issues"}],"ARM Case Number":"","Platform":[{"code":"PF033","label":"Windows"}],"Version":"8.5.5;9.0.0;9.0.5"},{"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Java SDK","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
22 February 2022

UID

swg21230924