| Author |
Message
|
| exerk |
 Posted: Wed Jun 01, 2011 12:24 am Post subject: |
 |
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| santnmq wrote: |
| Unique instance ID of the non-wokring queue manager can be found in the registry... |
You implied that it didn't. What does dspmq show? Does a simple endmqm command work?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
 |
| santnmq |
| Posted: Wed Jun 01, 2011 2:30 am Post subject: |
|
|
Centurion
Joined: 11 Jan 2011
Posts: 125
|
Ya DSPMQ command shows that the status of the queue managers as running.
I am able to start and stop the queue managers through command prompt using strmqm and endmqm command with no issues.
But it's failing, when you use the MQ exporer for this purpose OR use the command amqmdain. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jun 01, 2011 5:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| santnmq wrote: |
I am able to start and stop the queue managers through command prompt using strmqm and endmqm command with no issues.
But it's failing, when you use the MQ exporer for this purpose OR use the command amqmdain. |
The local install on one of my desktops does exactly this, and only started doing it when the domain id I usually logon as changed password. The other desktops (on which unsurprisingly I use the same combination of user id & password) are unaffected. In all cases WMQ is running as a local user on the desktop, and the domain id is in the local mqm group.
After much intimidation, threats, pleading and wailing, the desktop people blamed "an authentication problem somewhere in the domain and/or Active Directory for that desktop", which I took to be Windows-admin-speak for "we don't know and we don't care". I have resigned myself to the fact I will never again start the queue managers via the Explorer on that box & made a mental note to burn the lot and install v7 fresh when I get round to that one.
Unhelpful in terms of solving your problem, but you're not alone. And if you do find an answer...... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jun 01, 2011 1:44 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Vitor wrote: |
| fjb_saper wrote: |
| I have however had little success with my V7 installs on Windows V7. |
FWIW and potentially 
I've got WMQv7 running happily under Win7. Local install, local user & a service user to query the domain as per the documentation. Both amqmdain & strmqm work as expected. |
What happens if you use a domain user and add it to the mqm group?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| santnmq |
| Posted: Wed Jun 01, 2011 8:55 pm Post subject: |
|
|
Centurion
Joined: 11 Jan 2011
Posts: 125
|
thanks vitor for sharing your experience. It's really surprising for me as two of the other queue managers are working with the same user id.
The other surprising thng for me is that there are no entries in the registry under service folder for the non-working queue manager and I am not able to add it.
I think I am now only left with the option of recreating these queue managers again. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Jun 02, 2011 2:22 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| santnmq wrote: |
| ...I think I am now only left with the option of recreating these queue managers again. |
Finally! Make sure you snap-shot the objects and authorities before blowing them away.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 02, 2011 4:15 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fjb_saper wrote: |
| Vitor wrote: |
| fjb_saper wrote: |
| I have however had little success with my V7 installs on Windows V7. |
FWIW and potentially
I've got WMQv7 running happily under Win7. Local install, local user & a service user to query the domain as per the documentation. Both amqmdain & strmqm work as expected. |
What happens if you use a domain user and add it to the mqm group?
|
A domain user as the service user? I've never had a lot of luck with that under any version of WMQ.
If you mean a domain user in the mqm group of that install, works a treat. It's how the Win7 box runs; I'm logged on as my domain id (or one of them!) and I'm in mqm so I can administer it.
Maybe a new thread - "WMQ in Win7 - how?"
(If you want to take this offline email me)
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Jun 02, 2011 4:11 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| Vitor wrote: |
| A domain user as the service user? I've never had a lot of luck with that under any version of WMQ. |
It works. I've just installed MQ 7.0.1.4 on 6 Windows servers and the MQ service userid is a domain userid. Just before the MQ installer passes over the MQ setup wizard, I add the service userid and the domain mqm group to the local mqm group.
If there are problems with validating the userid & password or starting the service the MQ wizard diagnostics are very poor -- it just says "unexpected error". Some Windows DCOM or domain controller issues can cause failures here, the classic is CoCreateInstance failed 0x80080005 after 60 seconds. I never did get to the bottom of this one. Rebooting seemed to fix the issue.
Its wise to validate the domain userid & password before installing MQ, eg. contact admin /user:YourDomain\YourServiceUserid cmd.exe
It prompts for the password.
_________________
Glenn |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jun 02, 2011 7:53 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
No. Use the usual stand alone service usr.
Now use the domain user in the mqm group and admin group to start the qmgr via amqmdain.
Try an connect via a svrconn channel. I got 2035. The qmgr is running but does not seem to be accessible. (Possibly a problem with elevated priviledges in Win7)
Stop the qmgr. Use strmqm -si <qmgrname> from the same domain user and the qmgr is running and accessible.
Hope that helps some
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
