ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » Windows 2000 Server and CSD07

Post new topic  Reply to topic Goto page 1, 2  Next
 Windows 2000 Server and CSD07 « View previous topic :: View next topic » 
Author Message
RogerLacroix
PostPosted: Tue Jun 22, 2004 11:54 am    Post subject: Windows 2000 Server and CSD07 Reply with quote

Jedi Knight

Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada

All,

My turn to ask for help.

Box:
Windows 2000 Server SP4 (dual CPU)

Today I installed WMQ v5.3 with CSD01 using Terminal Services (to D: drive of server) and the install went fine (I copied the CD to a local drive then did the install from it). As I said, everything went fine and I reboot the server.

After the reboot, I downloaded CSD07. First I stopped the MQ Services and clicked 'Hide the icon'. Check Task Manager for any AMQ*** or RUNMQ*** tasks and there were none.

Under Terminal Services launched the CSD07 (U200212A.exe) and goes fine until it gets to'Checking files; please wait' (the 2nd time). Then I get the following error:
IBM WebSphere MQ files are in use. Stop activity and retry. (AMQ4757)

I have rebooted the server 2 twice now, stopped services, checked the Task Manager and I don't see anything MQ related running. I have NOT even defined a queue manager yet on this server!!

Could it be a problem with Terminal Services?? Or is CSD07 like CSD06 where it wasn't fully baked by IBM?

Jeff, Jason, Charlie, etc. any thoughts? or anyone else?

Regards,
Roger lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter
Back to top
View user's profile Send private message Visit poster's website
jefflowrey
PostPosted: Tue Jun 22, 2004 12:00 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Typically, when I've seen this kind of problem, it's been because of the Alert Monitor.

But that should still show up as an AMQ* process. Unless your Terminal Services Task Manager isn't set up to "Show All Processes".

There is a log file from the installer (somewhere... I don't remember where). It should tell you which files are "in use", so you can manually intervene if necessary - by renaming the files in question.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
EddieA
PostPosted: Tue Jun 22, 2004 12:48 pm    Post subject: Reply with quote

Jedi

Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles

I've seen a problem where something to do with Windows Instrumentation was the culprit.

There's also a command line override to say "Ignore files in use". But I can't remember it off hand.

Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
Back to top
View user's profile Send private message
Albator
PostPosted: Tue Jun 22, 2004 1:05 pm    Post subject: Reply with quote

Voyager

Joined: 04 Mar 2004
Posts: 75
Location: Toronto, Canada

I had this problem 2 days ago on my cluster server (Win2k) and I had to stop the following services:

- Norton Antivirus
- Windows Management Intrumentation

Also, some Compaq Services are known to have a handle on MQ files.

Anyways, this worked for me!
Back to top
View user's profile Send private message
RogerLacroix
PostPosted: Tue Jun 22, 2004 1:30 pm    Post subject: Reply with quote

Jedi Knight

Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada

All,

Thanks for your comments.

No matter how many things I stopped and how many times I rebooted the server, I had the problem with locked files.

Besides what mentioned above, here is what I did to resolve the problem:
    - Removed the MQ Taskbar icon from the Startup folder
    - Set the "IBM MQ Series" service to 'Manual' then REBOOTED.
    - Tried the CSD07 install again and of course it failed
    - Checked the CSD install log by doing the following command: notepad %TEMP%\amqicsdn.txt
    - Search for the string 'Target file is in use'
    - For each entry found (I had 5), renamed it to 'roger_amq*****'
    - REBOOTED again.
    - After the the reboot, deleted the 'roger_amq*****' files
    - Tried the CSD07 install again and this time it worked.
    - REBOOT again.
    - Put back the Task Bar icon in the startup folder
    - Set the "IBM MQ Series" service to 'Automatic' and started the service.
    - REBOOTED one last time to make sure everything worked and it did.

Now mqver gives 530.7 CSD07. Yeah!!!

Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter
Back to top
View user's profile Send private message Visit poster's website
PeterPotkay
PostPosted: Tue Jun 22, 2004 6:29 pm    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

Quote:

- Checked the CSD install log by doing the following command: notepad %TEMP%\amqicsdn.txt
- Search for the string 'Target file is in use'
- For each entry found (I had 5), renamed it to 'roger_amq*****'
- REBOOTED again.
- After the the reboot, deleted the 'roger_amq*****' files


So at this point your system was completly missing those 5 amq* files? I assume you assumed that the CSD07 would rebuild them if they were missing at CSD07 install time?
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
RogerLacroix
PostPosted: Tue Jun 22, 2004 7:31 pm    Post subject: Reply with quote

Jedi Knight

Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada

Actually, that is true, I DID make a BIG assumption but it did work. I didn't think about it until now (a little too trusting).

Regards,
Roger
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter
Back to top
View user's profile Send private message Visit poster's website
jefflowrey
PostPosted: Wed Jun 23, 2004 3:08 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

While I agree with Peter that you were maybe a little hasty in deleting those files...

I'm fairly confident that the installer wouldn't have complained about them if it was not going to be replacing them.

But, I still would have left the renamed versions around until after the CSD was successfully installed, and then made sure.

The other thing that's known to have a lock on MQ files is any sort of MQ monitoring agent or aparatus. I'm sure you would have turned that off, though, if you had one running.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
JasonE
PostPosted: Wed Jun 23, 2004 6:57 am    Post subject: Reply with quote

Grand Master

Joined: 03 Nov 2003
Posts: 1220
Location: Hursley

What were the files?

MQPINUSEOK=1 should allow the install even if files are in use.

The other issue I have seen are JVM's loading com.ibm.mq.jar even if they are not running MQ java programs due to classpath searches caching them!
Back to top
View user's profile Send private message
RogerLacroix
PostPosted: Wed Jun 23, 2004 9:25 am    Post subject: Reply with quote

Jedi Knight

Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada

Here is the snap of the amqicsdn.txt file:
Code:
16:13:15 File name 'amqxcsn.dll'
16:13:15 Features: 'Server,Client', platforms: 'nt'
16:13:15 Target file is 'D:\Program Files\IBM\WebSphere MQ\bin\amqxcsn.dll'
16:13:15 ***Target file is in use
16:13:15   version '5.300.100.2283', time 'Oct 11 2002 at 00:00' (126787680000000000)
16:13:15 Source file is 'C:\Program Files\IBM\Source\WebSphere MQ CSD07 EnUs\CSD00020\amqxcsn.dll'
16:13:15   version '5.300.700.4148', time 'May 27 2004 at 05:00' (127301076000000000)
16:13:15   to be processed
...
16:13:16 File name 'amqxcs2.dll'
16:13:16 Features: 'Server,Client', platforms: ''
16:13:16 Target file is 'D:\Program Files\IBM\WebSphere MQ\bin\amqxcs2.dll'
16:13:16 ***Target file is in use
16:13:16   version '5.300.100.2283', time 'Oct 11 2002 at 00:00' (126787680000000000)
16:13:16 Source file is 'C:\Program Files\IBM\Source\WebSphere MQ CSD07 EnUs\CSD00001\amqxcs2.dll'
16:13:16   version '5.300.700.4148', time 'May 27 2004 at 05:00' (127301076000000000)
16:13:16   to be processed
...
16:13:18 File name 'amqmperf.dll'
16:13:18 Features: 'GuiAdmin', platforms: ''
16:13:18 Target file is 'D:\Program Files\IBM\WebSphere MQ\bin\amqmperf.dll'
16:13:18 ***Target file is in use
16:13:18   version '5.300.100.2283', time 'Oct 11 2002 at 00:00' (126787680000000000)
16:13:18 Source file is 'C:\Program Files\IBM\Source\WebSphere MQ CSD07 EnUs\CSD00001\amqmperf.dll'
16:13:18   version '5.300.700.4148', time 'May 27 2004 at 05:00' (127301076000000000)
16:13:18   to be processed
...
16:13:22 File name 'amqmgs.dll'
16:13:22 Features: 'Server', platforms: ''
16:13:22 Target file is 'D:\Program Files\IBM\WebSphere MQ\bin\amqmgs.dll'
16:13:22 ***Target file is in use
16:13:22   version '5.300.100.2283', time 'Oct 11 2002 at 00:00' (126787680000000000)
16:13:22 Source file is 'C:\Program Files\IBM\Source\WebSphere MQ CSD07 EnUs\CSD00001\amqmgs.dll'
16:13:22   version '5.300.700.4148', time 'May 27 2004 at 05:00' (127301076000000000)
16:13:22   to be processed
...
16:13:22 File name 'amqmgs.dll'
16:13:22 Features: 'Server', platforms: ''
16:13:22 Target file is 'D:\Program Files\IBM\WebSphere MQ\bin\amqmgs.dll'
16:13:22 ***Target file is in use
16:13:22   version '5.300.100.2283', time 'Oct 11 2002 at 00:00' (126787680000000000)
16:13:22 Source file is 'C:\Program Files\IBM\Source\WebSphere MQ CSD07 EnUs\CSD00001\amqmgs.dll'
16:13:22   version '5.300.700.4148', time 'May 27 2004 at 05:00' (127301076000000000)
16:13:22   to be processed

Also, I have read many posting where the MQPINUSEOK flag doesn't work. Hence, I didn't use it.

Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter
Back to top
View user's profile Send private message Visit poster's website
bower5932
PostPosted: Wed Jun 23, 2004 11:25 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA

I've seen problems with the above files in use because of the Windows Management Instrumentation service.
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
JasonE
PostPosted: Wed Jun 23, 2004 12:29 pm    Post subject: Reply with quote

Grand Master

Joined: 03 Nov 2003
Posts: 1220
Location: Hursley

I havent seen any problems where the flag (when supplied currectly ) doesnt work (and I would believe it would be a defect if it doesnt work)

The file amqmperf.dll is the performance counters. As I understand it, once the performance counters have been loaded by a process, they cant be unloaded (not just MQ ones) without the process ending, but I have never checked this. (Maybe it was just a particular pgm which had this, my memory is lapsing...).

You can use process explorer with lower pane view set to DLLS to work out which process has it loaded. Windows is telling us the file is in use during the check, and hence we dont even try to do anything with it (as it wouldnt allow us if it really is in use). MQPINUSEOK means we do a deferred install on the next reboot.
Back to top
View user's profile Send private message
sebastianhirt
PostPosted: Thu Sep 30, 2004 4:41 am    Post subject: Reply with quote

Yatiri

Joined: 07 Jun 2004
Posts: 620
Location: Germany

Sorry, I know it is not really a help, and this post is not adding any value to this Thread....

But I had the same problem today... What I did was...

1. Tried to install... Didn't work
2. Killed each and every MQ process that was remaining
3. Still didn't work
4. Went to lunch for about 2 hours.
5. Had a long phone call
6. Did some other things
6. Tried it again

And suddenly it worked. Without changing anything.

Don't get me wrong. I love Windows. But sometimes it is a really wired OS.

cheers and good luck
Back to top
View user's profile Send private message
Heinz57
PostPosted: Thu Sep 30, 2004 6:59 am    Post subject: Reply with quote

Apprentice

Joined: 21 Jan 2004
Posts: 26
Location: Syracuse, NY

We have used utility to list all the dlls in a process. we pump the output to a file then do a find on amq - kill all the process that are running with an amq dll and away we go..... here's a link to the tool

http://www.sysinternals.com/ntw2k/freeware/listdlls.shtml

good luck
Back to top
View user's profile Send private message
JasonE
PostPosted: Fri Oct 01, 2004 3:18 am    Post subject: Reply with quote

Grand Master

Joined: 03 Nov 2003
Posts: 1220
Location: Hursley

That wont work for jvms which have loaded com.ibm.mq.jar...
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » Windows 2000 Server and CSD07
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.