Author |
Message
|
mattfarney |
Posted: Tue Apr 25, 2006 10:38 am Post subject: |
|
|
 Disciple
Joined: 17 Jan 2006 Posts: 167 Location: Ohio
|
|
Back to top |
|
 |
okiedokie |
Posted: Tue Apr 25, 2006 10:52 am Post subject: |
|
|
 Newbie
Joined: 12 Oct 2005 Posts: 8
|
Yup, we work 'together' in the sense that we are working on the same problem. Two different companies, two different locations. Same machine, same problem.
That's the long answer |
|
Back to top |
|
 |
BBM |
Posted: Tue Apr 25, 2006 12:33 pm Post subject: |
|
|
Master
Joined: 10 Nov 2005 Posts: 217 Location: London, UK
|
Hi,
This completely sounds like the account MQ is running under is incorrect.
Go to the component services snap-in under control panel/administrative tools. Or do start, run, dcomcnfg.
Look under Dcom Config section for IBM MQ Services, right click properties. Click on identity tab. Check account has correct privileges - test with local admin account to be certain.
Alternatively run the prepare Websphere MQ wizard from the start menu which allows you to specfiy the account there also.
Also make sure you are not using the command line STRMQM command - under windows it will be started as the current user. Use the Websphere MQ Explorer to start the queue managers - this way ensures the QM's are being started as the account specified above.
Good luck
BBM |
|
Back to top |
|
 |
mattfarney |
Posted: Tue Apr 25, 2006 12:46 pm Post subject: |
|
|
 Disciple
Joined: 17 Jan 2006 Posts: 167 Location: Ohio
|
This may not be clear from the posts above, but the queue manager will start up and run for periods of time (sometimes days), before shutting down.
I would have expected an account or permissions problem to manifest immediately at start up.
-mf |
|
Back to top |
|
 |
BBM |
Posted: Tue Apr 25, 2006 12:52 pm Post subject: |
|
|
Master
Joined: 10 Nov 2005 Posts: 217 Location: London, UK
|
Yes, I read that.
Unfortunately in Windows you can start the queue managers up using STRMQM or with an incorrect account and it will work fine, then you logout and the QM is asked to perform some work maybe hours or days later and will then fail. I have a list as long as my arm of other Windows specific MQ funnies that i don't get on other platforms.
cheers
BBM |
|
Back to top |
|
 |
mattfarney |
Posted: Tue Apr 25, 2006 1:20 pm Post subject: |
|
|
 Disciple
Joined: 17 Jan 2006 Posts: 167 Location: Ohio
|
Thanks for the info. I will definetly look at that.
-mf |
|
Back to top |
|
 |
okiedokie |
Posted: Wed Apr 26, 2006 6:42 am Post subject: |
|
|
 Newbie
Joined: 12 Oct 2005 Posts: 8
|
Right now that looks to be the issue. The identity is set to The Interactive User. I'm working on getting a userid built and used.
Thanks for the help. |
|
Back to top |
|
 |
BBM |
Posted: Wed Apr 26, 2006 8:28 am Post subject: |
|
|
Master
Joined: 10 Nov 2005 Posts: 217 Location: London, UK
|
Interactive User will mean any process started in MQ will fail at some point after that user has logged out.
Cheers
BBM |
|
Back to top |
|
 |
okiedokie |
Posted: Wed Apr 26, 2006 10:33 am Post subject: |
|
|
 Newbie
Joined: 12 Oct 2005 Posts: 8
|
Do we need to shutdown & restart MQ for this to take effect? |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Apr 26, 2006 11:12 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
If you change the user using DCOMCFG or by rerunning the Prepare MQ Security wizard, then you need to restart the IBM MQ Service - not just the queue manager.
And it's probably better to restart the whole machine. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
|