| Author |
Message
|
| santnmq |
 Posted: Sun May 29, 2011 9:39 pm Post subject: AMQ8118: WebSphere MQ queue manager does not exist |
 |
|
Centurion
Joined: 11 Jan 2011
Posts: 125
|
I have a queue manager on my local system on windows XP. I can see at the MQ explorer that the queue manager QM1 is running and connected to the MQ explorer.
When trying to stop this queue manager QM1 from MQ explorer, it is throwing the error
****************************************
* Command: amqmdain qmgr end QM1 -i
****************************************
AMQ8118: WebSphere MQ queue manager does not exist.
exitvalue = 16
Any help on this please...
thanks in advance... |
|
| Back to top |
|
 |
| santnmq |
| Posted: Sun May 29, 2011 10:15 pm Post subject: |
|
|
Centurion
Joined: 11 Jan 2011
Posts: 125
|
I have identified the issue and this is because of the amqmdain command used internally by the MQ explorer.
I am able to start the queue manager using strmqm command, but it fails to start if I use amqmdain command with the error code 16, which means that "Failed to configure service principal name"
Any idea, what can be the cause for this? |
|
| Back to top |
|
|
| exerk |
| Posted: Mon May 30, 2011 2:26 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Is it a 'local' install, i.e. MUSR_MQADMIN exists, or a domain install? What did you change on your system, or what domain policy changed?
_________________
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: Mon May 30, 2011 2:41 am Post subject: |
|
|
Centurion
Joined: 11 Jan 2011
Posts: 125
|
it is a local install and the user MUSR_MQADMIN exists for MQ processes.
As the issue seems to because of the service principal name, I have changed the DCOM config for the MQ Series from the MUSR_MQADMIN to launching user. Now it's working fine.
But I think now, MQ will not survive logged in user logoff.. please correct me if I am wrong. |
|
| Back to top |
|
|
| exerk |
| Posted: Mon May 30, 2011 3:22 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Try switching it back to MUSR_MQADMIN and see if the issue persists.
_________________
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 |
|
|
| fjb_saper |
| Posted: Mon May 30, 2011 4:07 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
He did not say which version of MQ he is using.
I have however had little success with my V7 installs on Windows V7.
We do not use a domain install.
amqmdain does not work as expected and connections to the running qmgr are refused as not authorized.
strmqm -si however seems to work fine. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| santnmq |
| Posted: Mon May 30, 2011 8:43 pm Post subject: |
|
|
Centurion
Joined: 11 Jan 2011
Posts: 125
|
I have reverted back to the user MUSR_MQADMIN and it's not working. it throwing the same error.
AMQ8118: WebSphere MQ queue manager does not exist.
exitvalue = 16
I am using MQ V6.0.2.5.
There are 4 qmgr on this system, out of which two qmgrs are working fine through MQ explorer but two qmgrs are having issue.
I am confused, as if this issue is because of the User, then all the queue managers should have this issue. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue May 31, 2011 1:52 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Something got screwed. Try deleting and recreating the two 'broken' queue managers.
_________________
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: Tue May 31, 2011 2:08 am Post subject: |
|
|
Centurion
Joined: 11 Jan 2011
Posts: 125
|
Ya recreating the qmgrs again will surely solve the problem but I am not in a condition to do so.
There is one more thing that I found out by observing the windows registry.. hope somebody can conclude how to solve this problem.
In windows registry...under location
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\ CurrentVersion\Configuration\Services
I can see that entry for those qmgrs which are not working is absent.
I had tried manually to add those entries there but could'nt do so. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue May 31, 2011 2:11 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| santnmq wrote: |
| Ya recreating the qmgrs again will surely solve the problem but I am not in a condition to do so. |
Why not?
| santnmq wrote: |
There is one more thing that I found out by observing the windows registry.. hope somebody can conclude how to solve this problem.
In windows registry...under location
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\ CurrentVersion\Configuration\Services
I can see that entry for those qmgrs which are not working is absent.
I had tried manually to add those entries there but could'nt do so. |
What entries are missing in comparison to the working queue managers?
_________________
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: Tue May 31, 2011 2:40 am Post subject: |
|
|
Centurion
Joined: 11 Jan 2011
Posts: 125
|
There are below two entries in the registry for working qmgrs. These are not present for the non-working qmgrs.
-------
[HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion\Configuration\Services\SAN_QMGR]
"InstanceID"="1295243153"
[HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion\Configuration\Services\SAN_QMGR\Queue Manager]
"ServiceType"=dword:00000004
"RecAction"=dword:00000001
"RecDelay"=dword:00000001
"RecAttempts"=dword:00000003
-------
[HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion\Configuration\Services\KUM_QMGR]
"InstanceID"="1294222551"
[HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion\Configuration\Services\KUM_QMGR\Queue Manager]
"ServiceType"=dword:00000004
"RecAction"=dword:00000001
"RecDelay"=dword:00000001
"RecAttempts"=dword:00000003
----- |
|
| Back to top |
|
|
| santnmq |
| Posted: Tue May 31, 2011 2:42 am Post subject: |
|
|
Centurion
Joined: 11 Jan 2011
Posts: 125
|
I had successfully added the entries in the registry using the registry file and editing it.. but these entries got removed automatically from registry after sometime.
It seems some MQ process is removing these entries for non-working qmgrs. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue May 31, 2011 5:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| 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.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue May 31, 2011 5:32 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| santnmq wrote: |
I had successfully added the entries in the registry using the registry file and editing it.. but these entries got removed automatically from registry after sometime.
It seems some MQ process is removing these entries for non-working qmgrs. |
Then either a Windows or WMQ internal process is removing them. I doubt you'd be able to restore the unique instance ID of each anyway as it's probably generated when the queue manager is created. Delete and recreate, and please answer my earlier question of why you are not in a position to do so.
_________________
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: Tue May 31, 2011 8:39 pm Post subject: |
|
|
Centurion
Joined: 11 Jan 2011
Posts: 125
|
The reason why I am unwilling to delete and recreate the queue manager is that these queue managers are linked to so many other MQ setups and which I have to setup again in case of recreation of the qmgrs.
If this issue could'nt resolve by any other way, as a last option I have to recreate the qmgrs.
Unique instance ID of the non-wokring queue manager can be found in the registry... |
|
| Back to top |
|
|
|
|
