| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Windows MQ client + MS03 support pac setup problem |
« View previous topic :: View next topic » |
| Author |
Message
|
| LM |
 Posted: Tue Feb 20, 2007 7:31 am Post subject: Windows MQ client + MS03 support pac setup problem |
 |
|
Newbie
Joined: 20 Feb 2007
Posts: 3
|
Hi all,
I'm really a newbie to MQ, and I'm facing a problem that you may know how to solve. I've tried to search this forum for a similar problem, but haven't found anything 
Also, please forgive me for my english (I come from Spain)
I need to retrieve the details of a Queue Manager in a remote server (running under OpenVMS), and I work on a Windows PC, so I've downloaded and installed the Windows' Websphere MQ client v 5.3, and also downloaded the MS03 Support Pac (as I've read that this pac contains the saveqmgrc tool that should be able to get the QM details, and also that it can be used with MQ client version 5.3)
But I'm having problems when running the saveqmgrc tool, I've tried to configure the MQ client (setting an MQSERVER environment variable), and then run the following
| Code: |
saveqmgrc -a host -r remote_queue_manager -f
|
and always get the following error:
| Code: |
SAVEQMGR V6.0.3
Compiled for Websphere MQ V6.0 on Aug 22 2006
Using the server connection channel "SYSTEM.DEF.SVRCONN"
on connection name "host".
MQCONNX failed for , CC=2 RC=2035
|
I've read that the 2035 error code relates to user authentication problems, but I'm not sure about why I'm having the error, or how it can be solved (I've also read something about MCAUSER, but again I have no idea about how can I set it)
Can you please let me know what I'm doing wrong?
Thank you very much for your help.
Last edited by LM on Tue Feb 20, 2007 7:53 am; edited 1 time in total |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Feb 20, 2007 7:37 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It means that the user id you're running the saveqmgrc program as (the Windows logon id) does not have permissions on the queue manager you're trying to talk to.
If there is another MQ administrator available, you should ask them for help.
If *and only if* there isn't another MQ administrator available, you can put "mqm" in the MCAUser field of SYSTEM.DEF.SVRFCONN temporarily.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Feb 20, 2007 7:37 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
2035 is an authorisation failure - the user id you're using does not have connection authority for the queue manager you're using.
You need whoever administers that queue manager to authorise your use, either by granting authorities to your user id or providing you with a channel that has MCAUSER set to an authorised id.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| LM |
| Posted: Tue Feb 20, 2007 8:01 am Post subject: |
|
|
Newbie
Joined: 20 Feb 2007
Posts: 3
|
Hi,
first of all, thanks for your quick answers.
I don't have any access to the remote server other than the MQ channel I'm trying to connect to, so I'll need the MQ administrators then.
Thanks again for your help. |
|
| Back to top |
|
|
| LM |
| Posted: Wed Feb 21, 2007 1:12 am Post subject: |
|
|
Newbie
Joined: 20 Feb 2007
Posts: 3
|
Hi all,
I have 2 more questions regarding this issue. 
You've mentioned that a solution would be to change the MCAUSER value of the SYSTEM.DEF.SVRCONN channel to "mqm" temporarily ... but do I need some setup of my Windows XP account (something like creating an "mqm" group and adding my XP user to that group)?
And also, do you know how can the current MCAUSER value be obtained from the channel?
Thanks in advance for your help. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 21, 2007 1:32 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
No, the SVRCONN is the server side of the connection. One of the reasons you've been advised to do this temporarily is that no change is required on the client side and hence anybody who connects to that channel will be granted the rights of the MCAUSER. In this case the rights of the MQ administrator. You can imagine the security risk here, and why you don't leave the channel set like that.
There's a display command which will show the current setting. Ask the MQ administrator.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
