Optional: You can delete the old, renamed copy of WASServiceMsg.dll.

The fix pack installation provides a new copy of the WASServiceMsg.dll file. Since the module was renamed, there is no longer any conflicts.

Using the Installation Manager, reinstall the WebSphere fix pack.

The reboot is necessary to ensure the file is no longer locked. 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.įor example, if you are using WebSphere Application Server v8.5.5.17, then rename the file to WASServiceMsg.dll.85517Īlthough the file is locked, the operating system allows the file to be renamed. It is good practice to rename the file to a name that contains the current WebSphere version.

Rename WASServiceMsg.dll to a different file name.

Locate the WASServiceMsg.dll file, which is in the WAS_HOMEin directory.Close or Exit the Installation Manager.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: 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. 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. Reboot the system and shut down the Windows Management Instrumentation software. If the software is being uninstalled before a reinstallation, reboot the machine after the uninstall to ensure modules are unloaded properly. If you do not have the WebSphere Application Server service set to start automatically, reboot your machine to release locked resources. Reboot the machine and retry the installation. If you have WebSphere Application Server running as a service to start automatically, change the startup type to manual.

Unlock a dll file