I could not upgrade WAS61 because there was a dll (WASServiceMsg.dll) is locked. This ended up stopping the install of the fix pack. This also made the autorecovery stop working. So I had to delete the entire installation of all 3 base products and start again - happy! No!!!
So I reinstalled everything and restarted the machine and tried to delete the WASServiceMsg.dll from the appserver\bin dir to ensure that the update would apply (this is what it could not do last time). I could not delete the file.
I downloaded a tool from http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx which is totally awesome. It shows lots of nerdy information about all of the processes that are loaded up, and allows you to search for DLLs in that information.
I found that the wmiprvse process was locking this DLL. This is a low level process which allows you get get all of the WMI information out of them. Obviously IBM is allowing the service to get information from WebSphere - but it's being locked.
known issue from IBM
Resolving the problem
If you have WebSphere Application Server running as a service to start automatically, change this to start manually. Then reboot your machine and retry the installation.
If you do not have WebSphere Application Server set to start automatically and it is already set to start manually, then reboot your machine to free the locked resource. Then retry the installation.
If you are uninstalling and then reinstalling. Reboot your machine after a successful uninstall before reinstalling.
In addition to the steps above, sometimes it is necessary to shut down the Windows Management Instrumentation service after your system has rebooted. Then retry the installation.
Subscribe to:
Post Comments (Atom)
-
There are a heap of instructions of what you need to change if you change the IP address of your weblogic server, but I find they are not co...
-
I need to support long usernames for a 8.98.1.1 site via MAD LDAP. I’m thinking that I can get the collaborative portal to do the full leng...
-
If you want to change this, there is a lot of BS on the internet, something like – change the startup parameters and add this… XX:MaxPermSi...
1 comment:
I have also came across the same situation while installing Fix Pack 6.1.0.23 on WAS 6.1 BASE. To overcome this issue, I renamed the WASServicemsg.dll and then tried to recover the upgradation failure and it worked. Please visit the following link:
http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg21230924
This resource really helped me out to resolve the issue.
Post a Comment