|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Applying CSD04 - .dll locked |
« View previous topic :: View next topic » |
Author |
Message
|
sjackson |
Posted: Wed May 22, 2002 5:42 am Post subject: Applying CSD04 - .dll locked |
|
|
 Apprentice
Joined: 28 Jun 2001 Posts: 26 Location: Milwaukee
|
Hello -
I am attempting to install CSD04 on an NT 4 server (MQ version 5.2).
During the install I am getting an error saying that amqxcs2.dll is locked, and to ensure that MQSeries, or any monitoring applications are stopped.
I stopped all of queue managers, monitoring agents (Candle) and stopped the MQSeries Service via the task bar. I did not get this problem when I did the same thing on a Windows 2000 server.
Is there another process or service I need to kill before I can apply the CSD? I'm probably missing something obvious.
Thanks in advance.
Scott |
|
Back to top |
|
 |
oz1ccg |
Posted: Wed May 22, 2002 6:01 am Post subject: |
|
|
 Yatiri
Joined: 10 Feb 2002 Posts: 628 Location: Denmark
|
I've seen the same problem also on NT, the way I got arround was locating the locked DLL, and the move it to a safe place (maybe reboot) and the apply the fix (ignoring that the CSD warning..)
It worked for me.  _________________ Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
Back to top |
|
 |
sjackson |
Posted: Wed May 22, 2002 6:50 am Post subject: |
|
|
 Apprentice
Joined: 28 Jun 2001 Posts: 26 Location: Milwaukee
|
It worked for us, too. Thanks, Jorgen.
We also have another reason to upgrade the server to Windows 2000 .....  |
|
Back to top |
|
 |
a1r |
Posted: Sat Mar 15, 2003 2:46 am Post subject: |
|
|
 Newbie
Joined: 31 Oct 2002 Posts: 3 Location: Edinburgh, UK
|
I've encountered this countless times with CSD06 on Windows 2000. The usual cause is that you still have an application running that accesses MQ; though I find sometimes the MQ process amqsrvn.exe doesn't go away when you stop the MQ service, and hogs the DLL.
The locked DLL in our case is always amqxcs2.dll.
In any case, rather than moving the DLL, a better solution is to find the process that's locking the DLL and stop it.
Try the free utility ProcView from http://www.teamcti.com/pview/ - it reports which modules are in use for a given process. It has a command line version pv.exe so you don't have to install anything (crucial for production upgrades!).
Simply run
Code: |
pv -m *.exe > modules.txt |
and search the text file for the locked DLL name. Then stop the necessary process(es). |
|
Back to top |
|
 |
oz1ccg |
Posted: Sat Mar 15, 2003 5:51 am Post subject: |
|
|
 Yatiri
Joined: 10 Feb 2002 Posts: 628 Location: Denmark
|
That sounds great, I'll add it on my patch-toolbox, and return my expierences with the tool.
Quote: |
The locked DLL in our case is always amqxcs2.dll. |
I can only agree on the dll.
Just my $0.02  _________________ Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
Back to top |
|
 |
leongor |
Posted: Mon Mar 17, 2003 12:30 am Post subject: |
|
|
 Master
Joined: 13 May 2002 Posts: 264 Location: Israel
|
I use it too. It's great utility.You can find locked dll's also from GUI.
I think this site has more updated version of PrcView :
http://www.xmlsp.com/pview/prcview.htm _________________ Regards.
Leonid.
IBM Certified MQSeries Specialist. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|