| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| reasoncode 2035 |
« View previous topic :: View next topic » |
| Author |
Message
|
| bath |
 Posted: Mon Jan 31, 2005 9:30 am Post subject: reasoncode 2035 |
 |
|
Apprentice
Joined: 23 Nov 2004
Posts: 29
|
Hello All,
I have the following problem : When trying to run my program on client machine I can not connect to Queue Manager and I received the error 2035.
On server computer I am connected as "administrator" and on the client machine the connected user is "administrateur". I have created the user administrateur on the server machine and set this as member of goup mqm and administrators. but i'm still unable to connect.
PS: my client and server computer are members of a domain but i'm connected as local user on each of them.
any help will be greatly appreciated
thanks |
|
| Back to top |
|
 |
| PGoodhart |
| Posted: Mon Jan 31, 2005 9:57 am Post subject: |
|
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
You may be having trouble due to your different machine language settings. I bet you have some set up as French of some kind and some as English. I would usually try MQM to see if that worked...
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
|
| csmith28 |
| Posted: Mon Jan 31, 2005 10:30 am Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
From the WMQ Message Guide:
| Quote: |
2035 X’07F3’ MQRC_NOT_AUTHORIZED
The user is not authorized to perform the operation attempted:
v On an MQCONN or MQCONNX call, the user is not authorized to connect to the queue
manager.
On z/OS, for CICS applications, MQRC_CONNECTION_NOT_AUTHORIZED is issued
instead.
v On an MQOPEN or MQPUT1 call, the user is not authorized to open the object for the
option(s) specified.
On z/OS, if the object being opened is a model queue, this reason also arises if the user is
not authorized to create a dynamic queue with the required name.
v On an MQCLOSE call, the user is not authorized to delete the object, which is a permanent
dynamic queue, and the Hobj parameter specified on the MQCLOSE call is not the handle
returned by the MQOPEN call that created the queue.
This reason code can also occur in the Feedback field in the message descriptor of a report
message; in this case it indicates that the error was encountered by a message channel agent
when it attempted to put the message on a remote queue.
Corrective action: Ensure that the correct queue manager or object was specified, and that
appropriate authority exists.
On z/OS, to determine for which object you are not authorized, you can use the violation
messages issued by the External Security Manager. |
For a better understanding of your problem please post detailed information about the Operating System, MQVersion and exactly how you are trying to connect.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jan 31, 2005 2:22 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You are connected locally on both machines.
On the server add the user ClientMachine\administrateur into the server's mqm group.
As a precaution go to the server run runmqsc and put the command
Try again.
Hope it helps  |
|
| 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
|
|
|
|
