Author |
Message
|
Vitor |
Posted: Thu Jul 05, 2007 3:43 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Did you ever say if you were using a domain id? If domain access has been broken or changed, that would cause a simulatious failure on 3 machines as you describe. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
kiran_raghunam |
Posted: Tue Jul 10, 2007 12:03 am Post subject: |
|
|
 Apprentice
Joined: 02 May 2006 Posts: 36
|
The problem still is unresolved after cross checking my access to the domain.
Still i am getting the error :
AMQ8135: Not authorized.
when i issue the runmqsc <Qmgr Name> command.
The application log has the following warning:
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.
The FDC has the following :
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Tue July 10 08:51:27 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 :- ZF095010 |
| Application Name :- MQM |
| Component :- zfuCacheAuthQueue |
| SCCS Info :- cmd/oam/amqzfuma.c, 1.86.1.1 |
| Line Number :- 944 |
| Build Date :- Oct 21 2005 |
| CMVC level :- p600-100-051021 |
| Build Type :- IKAP - (Production) |
| UserID :- kxr78144n |
| Process Name :- D:\IBM\WebSphere MQ\bin\amqzfuma.exe |
| Process :- 00003176 |
| Thread :- 00000001 |
| QueueManager :- Test |
| ConnId(2) QM :- 14 |
| 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 |
| |
+-----------------------------------------------------------------------------+
Any help is greatly appreciated.
Thanks in advance _________________ Regards
Kiran |
|
Back to top |
|
 |
Vitor |
Posted: Tue Jul 10, 2007 12:38 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
kiran_raghunam wrote: |
The problem still is unresolved after cross checking my access to the domain.
Still i am getting the error :
AMQ8135: Not authorized.
when i issue the runmqsc <Qmgr Name> command.
The application log has the following warning:
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.
|
Okay, there's your problem right there. You may think you've got access via the domain, but the domain is not confirming this to MQ. Either the domain permissions are set wrong or the domain controller is inaccessable.
Speak to your network / domain admins. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
srinivas Raju |
Posted: Tue Jul 10, 2007 3:30 am Post subject: |
|
|
Novice
Joined: 20 Feb 2007 Posts: 22 Location: India
|
kiran_raghunam wrote: |
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. |
use endmqm -i <Qmgr NAme>
this will forcely disconnect all application which connected to QMGR
it may work try this  |
|
Back to top |
|
 |
Vitor |
Posted: Tue Jul 10, 2007 3:52 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
srinivas Raju wrote: |
use endmqm -i <Qmgr NAme>
this will forcely disconnect all application which connected to QMGR
it may work try this  |
So you fix an authorisation problem on startup by forceably closing the queue manager? When it's already closed successfully? What's your thinking here?  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Biju |
Posted: Wed Jul 11, 2007 3:15 am Post subject: |
|
|
 Acolyte
Joined: 03 Oct 2005 Posts: 71
|
Is this problem solved?
If not would you try running the MQ Wizard and and see what it says?
Regards,
Biju |
|
Back to top |
|
 |
Everest |
Posted: Wed Jul 11, 2007 12:47 pm Post subject: |
|
|
Novice
Joined: 02 Feb 2007 Posts: 16
|
Try recycling MQ. Free shared memory.
May be that will narrow down the problem.. |
|
Back to top |
|
 |
mqperson |
Posted: Wed Jul 11, 2007 2:49 pm Post subject: |
|
|
Apprentice
Joined: 10 Jan 2006 Posts: 32
|
this looks like a domain security related issue to me. did u install MQ as a domain user ? try starting mq after logging into the system as a local user on the system. you may want to check the userid that mq services run under using dcomcnfg.
hope this helps.. |
|
Back to top |
|
 |
kiran_raghunam |
Posted: Wed Jul 11, 2007 11:18 pm Post subject: |
|
|
 Apprentice
Joined: 02 May 2006 Posts: 36
|
No this problem is still not resolved.
Quote: |
If not would you try running the MQ Wizard and and see what it says? |
I tried running the MQ Wizard and got the following error:
An unexpected error has occured while validating the security credentials of the user '<DomainName>\<user>'
Ensure that the network is operational,and that all required domain controllers are available.
Quote: |
Try recycling MQ. Free shared memory.
May be that will narrow down the problem.. |
can you tell me what do you exactly mean by 'recycling MQ'? _________________ Regards
Kiran |
|
Back to top |
|
 |
kiran_raghunam |
Posted: Wed Jul 11, 2007 11:25 pm Post subject: |
|
|
 Apprentice
Joined: 02 May 2006 Posts: 36
|
Quote: |
this looks like a domain security related issue to me. |
Yes it is a security related issue.
Quote: |
did u install MQ as a domain user ? try starting mq after logging into the system as a local user on the system. |
I have installed MQ as a domain user.I dont have access to login as the local user on that system.
Quote: |
you may want to check the userid that mq services run under using dcomcnfg |
The userid that mqservices run under is MUSR_MQADMIN
Presently i m waiting for the network / domain admin to respond to this issue.Will update it once i found the resolution. _________________ Regards
Kiran |
|
Back to top |
|
 |
kiran_raghunam |
Posted: Fri Jul 20, 2007 1:52 am Post subject: |
|
|
 Apprentice
Joined: 02 May 2006 Posts: 36
|
Any idea if applying the latest Fixpack 6.0.2.1 could resolve this problem ???
Thanks _________________ Regards
Kiran |
|
Back to top |
|
 |
Vitor |
Posted: Fri Jul 20, 2007 2:05 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
kiran_raghunam wrote: |
Any idea if applying the latest Fixpack 6.0.2.1 could resolve this problem ???
|
Wouldn't have thought so, but it's always worth applying maintenance. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
kiran_raghunam |
Posted: Sun Jul 29, 2007 10:38 pm Post subject: |
|
|
 Apprentice
Joined: 02 May 2006 Posts: 36
|
Hi All
The problem is solved at last when i log in to the system as a local user instead of logging in as a Domain User.
Thanks all for your suggestions  _________________ Regards
Kiran |
|
Back to top |
|
 |
Vitor |
Posted: Sun Jul 29, 2007 11:36 pm Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
kiran_raghunam wrote: |
The problem is solved at last when i log in to the system as a local user instead of logging in as a Domain User.
|
Now I said that weeks ago!
Well done you for resolving your problem.  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
fjb_saper |
Posted: Mon Jul 30, 2007 2:54 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Well to run runmqsc you would need to have the local box administrator add the domain\user account to the local mqm group.
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
|