Author |
Message
|
kiran_raghunam |
Posted: Wed Jul 04, 2007 5:56 am Post subject: Problem in Starting and running a QMGR |
|
|
 Apprentice
Joined: 02 May 2006 Posts: 36
|
Hi,
I am using WMQ 6 on Windows 2003. The other details are as follows:
Name: WebSphere MQ
Version: 6.0.1.1
The problem is that I am not able to execute the runmqsc command for the queuemanager. The error I got is :
5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.
Starting MQSC for queue manager <Qmgr name>.
AMQ8135: Not authorized.
No MQSC commands read.
No commands have a syntax error.
All valid MQSC commands were processed.
When i start the QMGR from MQ Explorer window,the icon shows that it is runnning,but when i type
runmqsc <Qmgr name>
i get the error:
AMQ8135: Not authorized.
Also the queue manager objects are NOT visible in MQ Explorer window.
I am a member of the mqm groups also.
This problem has not occured previously,no clue as to why it is happenning now
Any help is appreciated
Thanks in Advance... _________________ Regards
Kiran
Last edited by kiran_raghunam on Wed Jul 04, 2007 6:38 am; edited 1 time in total |
|
Back to top |
|
 |
Vitor |
Posted: Wed Jul 04, 2007 6:06 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
If you type runqmqsc <Qmgr> and get an AMQ8135, then type endmqm, what happens? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
kiran_raghunam |
Posted: Wed Jul 04, 2007 6:13 am Post subject: |
|
|
 Apprentice
Joined: 02 May 2006 Posts: 36
|
When i type endmqm <Qmgrname> it is getting ended normally.
After that when i give strmqm <Qmgr name> then i get the following error:
WebSphere MQ queue manager <Qmgr Name> starting.
5 log records accessed on queue manager <Qmgr Name> during the log replay phase.
Log replay for queue manager <Qmgr Name> complete.
Transaction manager state recovered for queue manager <Qmgr Name>.
AMQ5615: Default objects cannot be created: CompCode = 2 Reason = 2063. _________________ Regards
Kiran |
|
Back to top |
|
 |
Vitor |
Posted: Wed Jul 04, 2007 6:18 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Certainly sounds like the security is all stuffed up. Try strmqm -c to recreate the system objects _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
kiran_raghunam |
Posted: Wed Jul 04, 2007 6:28 am Post subject: |
|
|
 Apprentice
Joined: 02 May 2006 Posts: 36
|
Thanks for the suggestion but when i did strmqm -c <QmgrName>
i got the following error:
WebSphere MQ queue manager <QmgrName> starting.
10 log records accessed on queue manager <QmgrName> during the log replay phase.
Log replay for queue manager <QmgrName> complete.
Transaction manager state recovered for queue manager <QmgrName>.
Setup completed.
AMQ5615: Default objects cannot be created: CompCode = 2 Reason = 2063.
 _________________ Regards
Kiran |
|
Back to top |
|
 |
Vitor |
Posted: Wed Jul 04, 2007 6:58 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Ok, is there anything in the Windows event log? Can you administer as another user id e.g. mqm?
If so, switch on security events and see who the queue manager thinks you are.
You're not using a domain id are you?? They're notoriously problematic!
(The search button will give you some background there!) _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
kiran_raghunam |
Posted: Wed Jul 04, 2007 11:30 pm Post subject: |
|
|
 Apprentice
Joined: 02 May 2006 Posts: 36
|
The Windows event log has the informations like :
1)
WebSphere MQ encountered the following network error: The RPC server is unavailable.
MQ failed to successfully complete a network operation due to the specified error.
Ensure that your network is functioning correctly
------------------------------------------------------------------------------------
2)
An essential WebSphere MQ process 2752 (amqzfuma.exe) cannot be found and is assumed to be terminated.
A user has inadvertently terminated the process. 2) The system is low on resources. Some operating systems terminate processes to free resources. If your system is low on resources, it is possible it has terminated the process so that a new process can be created.
WebSphere MQ will stop all MQ processes. Inform your systems administrator. When the problem is rectified WebSphere MQ can be restarted.
------------------------------------------------------------------------------------- _________________ Regards
Kiran |
|
Back to top |
|
 |
kiran_raghunam |
Posted: Wed Jul 04, 2007 11:36 pm Post subject: |
|
|
 Apprentice
Joined: 02 May 2006 Posts: 36
|
The FDC has the following error information
PIDS :- 5724H7200 |
| LVLS :- 6.0.1.0
| Product Long Name :- WebSphere MQ for Windows
| Vendor :- IBM |
| Probe Id :- ZX092002
| Application Name :- MQM |Component :- zmuStatisticsCollector
| SCCS Info :- cmd/zmain/amqzmus0.c, 1.18.1.1 |
| Line Number :- 248 |
| Build Date :- Oct 21 2005 |
| CMVC level :- p600-100-051021 |
| Build Type :- IKAP - (Production) |
| UserID :- kxr78144n |
| Process Name :- D:\IBM\WebSphere MQ\bin\amqzmur0.exe |
| Process :- 00002972 |
| Thread :- 00000003 |
| QueueManager :- GKOP_W2K_006 |
| ConnId(1) IPCC :- 6 |
| ConnId(2) QM :- 8 |
| Major Errorcode :- MQRC_SECURITY_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ080F |
| Probe Severity :- 4 |
| Probe Description :- AMQ6090: WebSphere MQ was unable to display an error |
| message 80F. |
| FDCSequenceNumber :- 0
and another FDC has :
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thu July 05 08:21:24 GMT Daylight Time 2007 |
| Host Name :- BRESAWNVM0074 (Windows 2000 Build 2195: Service Pack |
| 4) |
| PIDS :- 5724H7200 |
| LVLS :- 6.0.1.0 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- RM185002 |
| Application Name :- MQM |
| Component :- rrmInitRepos |
| SCCS Info :- cmd/remote/amqrrmfa.c, 1.414.1.7 |
| Line Number :- 3165 |
| Build Date :- Oct 21 2005 |
| CMVC level :- p600-100-051021 |
| Build Type :- IKAP - (Production) |
| UserID :- kxr78144n |
| Process Name :- D:\IBM\WebSphere MQ\bin\amqrrmfa.exe |
| Process :- 00001716 |
| Thread :- 00000001 |
| QueueManager :- GKOP_W2K_006 |
| ConnId(2) QM :- 11 |
| Major Errorcode :- rrcE_MQCONN_FAILED |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ9508 |
| Probe Severity :- 2 |
| Probe Description :- AMQ9508: Program cannot connect to the queue manager. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 2 2 |
| Arith2 :- 2063 80f |
| Comment1 :- GKOP_W2K_006 |
| |
| Comment2 :- MQRC_SECURITY_ERROR |
| |
| |
+-----------------------------------------------------------------------------+
Not sure from where these errors have crept in from ,as i was able to connect to the queue manager earlier and was able to create the Qmgr objects also....
Any suggestions are highly appreciated _________________ Regards
Kiran |
|
Back to top |
|
 |
Vitor |
Posted: Thu Jul 05, 2007 12:03 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
|
Back to top |
|
 |
kiran_raghunam |
Posted: Thu Jul 05, 2007 1:14 am Post subject: |
|
|
 Apprentice
Joined: 02 May 2006 Posts: 36
|
Hi
The system does'nt seem to be running out of memory.
Also this problem is occuring on the other windows server also which we use for testing....previously they both were working fine.
From the FDCs
did not get any info on the Probe Id :- ZX092002 from google or ibm...
For the | Probe Id :- ZX005025,
| Probe Description :- AMQ5008: An essential WebSphere MQ process 1404 |
| (amqrrmfa.exe) cannot be found and is assumed to be terminated.
but when i check the taskmanager the process amqrrmfa.exe is running
Please let me knw if there is any other alternative approach to resolve the error.
Thanks _________________ Regards
Kiran |
|
Back to top |
|
 |
Vitor |
Posted: Thu Jul 05, 2007 1:52 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Well if MQ is throwing "out of resource" errors and you're confident that the machines are not if fact short of resources (even transitorily) then the obvious conclusion is that not all of the available resources are being assigned to MQ or communication between the queue manager and it's child processes are being interupted.
I'd check that Windows is patched to the latest level, see if there's anything in the MSoft KB about this sort of resource or comms problem, that sort of thing.
But if both machines were working fine, and are now failing without apparent software changes I'd still suspect something environmental like resource. Especially if I was getting resource messages. But that's just me.  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Jul 05, 2007 2:31 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Confirm that you have sufficient LOG space - the number of primary & secondary log files.
Confirm that you have sufficient DISK SPACE in general. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
kiran_raghunam |
Posted: Thu Jul 05, 2007 2:54 am Post subject: |
|
|
 Apprentice
Joined: 02 May 2006 Posts: 36
|
There is no problem with Disk Space as we are having about 17GB free.
Can you please suggest what can be done to increase the log space.
also when the dspmqaut is given we get:
C:\Documents and Settings\kxr78144n>dspmqaut -m Test -t qmgr -p kxr78144n
WebSphere MQ was unable to display an error message 7047.
AMQ7047
C:\Documents and Settings\kxr78144n>mqrc amq7047
28743 0x00007047 lpiRC_CSPRC_UNEXPECTED_ERROR
xcsGetMessage() returned xecE_W_DEFAULT_TEXT_SUBSTITUTED
MESSAGE:
WebSphere MQ was unable to display an error message 7047.
EXPLANATION:
MQ has attempted to display the message associated with return code hexadecimal
'7047'. The return code indicates that there is no message text associated
with the message. Associated with the request are inserts 1111 : 2222 : <insert
one> : <insert two> : <insert three>.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
Does this suggest that there is problem else where??
Thanks _________________ Regards
Kiran
Last edited by kiran_raghunam on Thu Jul 05, 2007 3:02 am; edited 2 times in total |
|
Back to top |
|
 |
Vitor |
Posted: Thu Jul 05, 2007 2:59 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
No, it sounds like your MQ is in serious trouble.
I'll assume you've bounced the box to clear out any transient problems.
Failing that it sounds like one or more of the services are failing to start. I'd go back to the event log and see what that says. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
kiran_raghunam |
Posted: Thu Jul 05, 2007 3:20 am Post subject: |
|
|
 Apprentice
Joined: 02 May 2006 Posts: 36
|
well the event log has the details like :
WebSphere MQ encountered the following network error: The RPC server is unavailable.
MQ failed to successfully complete a network operation due to the specified error.
Ensure that your network is functioning correctly.
and
An internal WebSphere MQ error has occurred on queue manager <Qmgrname>.
An error has been detected, and the WebSphere MQ error recording routine has been called. The failing process is process 756.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
Also when i tried to replace the mq objects using strmqm -c ,
C:\Documents and Settings\kxrn>strmqm -c <Qmgr name>
WebSphere MQ queue manager <Qmgr name> starting.
10 log records accessed on queue manager <Qmgr name> during the log replay phase.
Log replay for queue manager <Qmgr name> complete.
Transaction manager state recovered for queue manager <Qmgr name>
Setup completed.
AMQ5615: Default objects cannot be created: CompCode = 2 Reason = 2063.
C:\Documents and Settings\kxrn>mqrc 2063
2063 0x0000080f MQRC_SECURITY_ERROR
Still not able to figure it out why  _________________ Regards
Kiran |
|
Back to top |
|
 |
|