| Author |
Message
|
| abnormallynormal |
 Posted: Wed Feb 23, 2005 8:17 am Post subject: 2035 Error on MQSession.AccessQueueManager |
 |
|
Newbie
Joined: 23 Feb 2005
Posts: 1
|
I'm trying to issue a MQSession.AccessQueueManager("") or MQSession.AccessQueueManager("QM_MARGIN") using the mqaxdlst VB example from a client machine, Server1. I get the 2035 Reason code, MQRC_NOT_AUTHORIZED.
I have the following environment on two W2K Servers.
Server1 - MQ Client Install with MQSERVER=CHANNEL1/TCP/X.X.X.X(1414)
Server2 - MQ Server Install with one default Queue Manager=QM_MARGIN, Queue, Channel (Server connection), Listener (running for port 1414)
1) I thought OAM was disabled by default? If not how do I disable it?
2) Both servers are not in a Domain but a workgroup. Therefore I cannot add a Server1 User to the mqm group on Server2 and add authorization with setmqaut.
This is a development environ so security/authorization is not a concern.
Thanks!! |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Feb 23, 2005 8:25 am Post subject: Re: 2035 Error on MQSession.AccessQueueManager |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| abnormallynormal wrote: |
| 1) I thought OAM was disabled by default? If not how do I disable it? |
Not that I know, and Don't.
| abnormallynormal wrote: |
| 2) Both servers are not in a Domain but a workgroup. Therefore I cannot add a Server1 User to the mqm group on Server2 and add authorization with setmqaut. |
Set an MCAUser on the client channel. Or create a user with the same name and password on both servers.
| abnormallynormal wrote: |
| This is a development environ so security/authorization is not a concern. |
Except you need to understand how to deal with security and troubleshoot security problems. So it's better to have it setup in dev than not.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Feb 23, 2005 2:14 pm Post subject: Re: 2035 Error on MQSession.AccessQueueManager |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| abnormallynormal wrote: |
This is a development environ so security/authorization is not a concern.
|
And when the 2035s show up in QA and PROD, then what? You will have no experience on solving them.
If you really want to disable OAM, but you shouldn't, set the below b4 you create the QM:
You cannot turn it back on for the QM, nor can you turn it off after you created the QM.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| RAJESHRAMAKRISHNAN |
| Posted: Fri Feb 25, 2005 12:44 am Post subject: |
|
|
Voyager
Joined: 01 May 2004
Posts: 96
|
I think you can disable and enable the OAM validation in Win 2000. I delete the Authorization Services on the MQServices console to disable OAM validations and add back if required.
BTW Is the same possible on other platforms, AIX for instance? |
|
| Back to top |
|
|
| Nigelg |
| Posted: Fri Feb 25, 2005 2:46 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
| You can disable the auth service on UNIXy commenting out the Service and ServiceComponent stanzas andx entries for the auth service, and enable it again by reinstating the lines. A qmgr restart is required each time to implement the change. |
|
| Back to top |
|
|
| xgnitesh |
| Posted: Thu Apr 27, 2006 9:14 am Post subject: |
|
|
Novice
Joined: 06 Sep 2005
Posts: 19
|
Hi All,
Did anyone solve the 2035 error? I am facing the same error and I should not disable authorization.
I have a MQ Server with the following objects:
Queue Manager = QM
Local Queue = LQ
Server Connection Channel = CHANNEL
(default port)
On the clinet which is on the local domain less network, I have set environment variable MQSERVER = CHANNEL/TCP/192.168.1.3 where the IP address specified is my MQ server's IP address.
as specified in this thread: "Set an MCAUser on the client channel. Or create a user with the same name and password on both servers.
"
I tried to have a user account with same username and password on the server and the client machine but that did not help.
The other suggestion of having MCAUser on the client channel was not clear to me. Can anyone pls elaborate this method for me.
Thanks very much in advance for any help.
Best regards
Nitesh Gupta |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Apr 27, 2006 9:23 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Easiest and quickest is to set MCAUSER on SVRCONN channel as mqm
Or issue setmqaut commands for the userid you created and set it as MCAUSER |
|
| Back to top |
|
|
| xgnitesh |
| Posted: Thu Apr 27, 2006 9:40 am Post subject: |
|
|
Novice
Joined: 06 Sep 2005
Posts: 19
|
Thanks Vennela,
Your quick help solved my problem. I made a user account called mqseries on both server and client machines with the same password on both. Then I set the MACUser for the server connection channel on the server to mqseries. Then I gave connect get and put permission to mqseries principal.
I have one more question:
In my current setup, I had server and client both on a win2k prof machines respectively. But, in my production setup, I am going to have server on win2k prof/server and the client will run on unix/solaris os.
QUESTION:
Having a normal unix/solaris user account on client will work in the similar manner? OR will I have to make any change? Do you or anyone else have experience of such a setup?
Thanks again.
Regards,
Nitesh Gupta |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Apr 27, 2006 11:30 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| I don't think there will be a problem with UNIX QMGRS either |
|
| Back to top |
|
|
| SAFraser |
| Posted: Thu Apr 27, 2006 12:20 pm Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
I do not think the passwords on the two machines must match. I believe that only the userID is passed by MQ.
Shirley |
|
| Back to top |
|
|
|
|
