| Author |
Message
|
| sanu_mit |
 Posted: Sun Aug 20, 2006 9:58 pm Post subject: MB6 - Problem to connect to the ConfigMgr thru Toolkit |
 |
|
Apprentice
Joined: 03 Jul 2003
Posts: 25
Location: Kolkata
|
First my setup description:
Windows XP with SP2
WebSphere MQ 6 with CSD01
WBI MB 6.0.0.1 with CSD02
DB2 UDB 8.2
I successfully created a ConfigMgr WBRK6_CFGMGR and a Broker WBRK6_BROKER thru the Command Console but while trying to connect the ConfigMgr thru the Toolkit, it gives the error that "user <user name> is not authorized to connect to QMgr". I have only one QMgr for the ConfigMgr and Broker. Also that both the broker and configmgr services run successfully and that the user id i'm using has all the required rights and grps.
Also I'd like to inform that I have been able to successfully connect to the configmgr thru the ConfigMgrProxy as well as 've been able to put message into a test queue of the QMgr thru the put utility of the Toolkit.
Any help in this regard is highly appreciated.
Thanks in anticipation. |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Mon Aug 21, 2006 1:35 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| The problem is probably ACL related. Is the userid that you are using to connect using the CMP the same as the userid that you're using to connect using the toolkit? |
|
| Back to top |
|
|
| sanu_mit |
| Posted: Mon Aug 21, 2006 2:00 am Post subject: |
|
|
Apprentice
Joined: 03 Jul 2003
Posts: 25
Location: Kolkata
|
mqmatt,
I don't think there is a problem with the ACL because the ACL entry for the user id has full access and I used the same user id for all my work right from the installation. Also, just for your information that, the user id is a member of the Administrators group for the PC that I am using. |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Mon Aug 21, 2006 2:07 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi sanu_mit,
What is your user name and what is the system name ?
Regards. |
|
| Back to top |
|
|
| sanu_mit |
| Posted: Mon Aug 21, 2006 2:16 am Post subject: |
|
|
Apprentice
Joined: 03 Jul 2003
Posts: 25
Location: Kolkata
|
For elvis_gn
User Name: santanum
System Name: I'm not sure what you mean. However, It's is a Windows XP SP2 standalone system and I'am accessing it as localhost. |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Mon Aug 21, 2006 2:38 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi sanu_mit,
| sanu_mit wrote: |
System Name: I'm not sure what you mean. |
My Computer-->Properties-->Computer Name-->Full Computer Name
What does it say ?
Regards. |
|
| Back to top |
|
|
| mliu7777 |
| Posted: Thu Aug 31, 2006 12:09 pm Post subject: Same problem to me |
|
|
Newbie
Joined: 11 Aug 2006
Posts: 3
|
| I am having the same problem...We moved configmgr from windows to AIX. On Aix Configmgr and Broker running on the same Qmgr. All started successfully without errors. . The id on windows using toolkit to connect is the exactly same we defined on AIX. ACL rules also set full access . Id Has been used for a long time. It still gave me 'not authorized to connect to qmgr ' issue on toolkit. I am not sure if you have resolved this problem. If so, do you mind let me know what you have done? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Aug 31, 2006 12:16 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You need both ACLs and setmqaut permissions to connect to the ConfigMgr.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PieterV |
| Posted: Thu Aug 31, 2006 11:25 pm Post subject: |
|
|
Disciple
Joined: 04 Jan 2006
Posts: 164
Location: Belgium
|
yes,
it's probably the setmqaut that you've forgotten
you need +connect +inq rights on your queue manager
and access to at least:
SYSTEM.BROKER.CONFIG.QUEUE (+get ; +put)
SYSTEM.BROKER.CONFIG.REPLY(+get; +put)
command:
setmqaut -m QMGR -t qmgr -g GROUP (or use -p USERNAME) +connect +inq
setmqaut -m QMGR -t q -n SYSTEM.BROKER.CONFIG.QUEUE +get +put
good luck |
|
| Back to top |
|
|
| EddieA |
| Posted: Fri Sep 01, 2006 11:50 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
What's in the Event Logs.
I've just hit the same issue trying to start my Toolkit for the first time in ages. I get the following:
Unable to obtain account details for channel MCA user ID.
WebSphere MQ was unable to obtain the account details for MCA user ID 'EddieAth'. This user ID was the MCA user ID for channel 'SYSTEM.BKR.CONFIG' on queue manager 'EDDIEATH_V6' and may have been defined in the channel definition, or supplied either by a channel exit or by a client.
Playing around with a couple of Java applications, and RFHUTILC, I discovered the following. RFHUTILC can connect without problems. The Java applications all fail with the above error.
Now, even stranger, if I put my userID in the MCAUser field on the SVRCONN channel, nothing can connect.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| EddieA |
| Posted: Fri Sep 01, 2006 12:06 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Small update.
Initially, my userID was NOT in group mqm. Don't ask me why, as I'm sure it used to be. Anyway, after adding it, I did a REFRESH SECURITY. Following that, I got the results I mentioned above.
However, after bouncing the QM, I can now connect using a Java application,as long as I don't expicitly set the UserID. Hmmmm, why didn't the REFRESH SECURITY work.
So, it looks like the "Unable to obtain account details for channel MCA user ID." error is only thrown when the Java client EXPLICITLY passes the UserID. Which leads me to believe that the Toolkit is doing this. Is there any way to stop it.
Cheers.
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Sep 01, 2006 1:03 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The only way to stop the Toolkit passing an explicit user id is to install a dummy security exit.
It sounds like you've got a problem actually with the OAM connecting to the account repository - somehow.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| EddieA |
| Posted: Fri Sep 01, 2006 1:28 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
OK, playing around with the V5 Toolkit, the V6 Toolkit, amqsputc, rfhutilc, and a couple of Java clients, here's the list of what happens:
V5 Toolkit connects OK.
V6 Toolkit fails on connect with 2035, and the Event msg shown earlier.
amqsputc connects OK.
rfhutilc connects OK.
Java client, with NO UserID in MQEnvironment.userID connects OK.
Java client with MQEnvironment.userID set, fails on connect with 2035, and the Event msg shown earlier.
Setting the MCAUser to my UserID fails on ALL connections ith 2035, and the Event msg shown earlier.
Setting the MCAUser to MUSR_MQADMIN, everything connects OK.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Sat Sep 02, 2006 9:34 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi EddieA,
| EddieA wrote: |
| Setting the MCAUser to MUSR_MQADMIN, everything connects OK. |
So the problem is fixed I suppose...
I remeber getting an error for the v6 toolkit on trying to connect to the ConfigMgr...
The solution given by IBM was to put a new entry in the EnvironmentVariables as MQNOREMPOOL and set its value to 1.
Regards. |
|
| Back to top |
|
|
|
|
