ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » Reason code 2035

Post new topic  Reply to topic
 Reason code 2035 « View previous topic :: View next topic » 
Author Message
pstarke
PostPosted: Wed Jun 19, 2002 7:37 am    Post subject: Reason code 2035 Reply with quote

Newbie

Joined: 11 Jun 2002
Posts: 2
Location: seattle, WA

Hello,
I am attempting to run the command line utility amqsputc. When I do so, I get:

"Sample AMQSPUT0 start
MQCONN ended with reason code 2035"

Which indicates I do not have rights to perform this operation.

We have not enabled security on the MQServer. If I log in as another user, it works fine. If I log into another machine which also has the client installed, using my user ID, I get the 2035 error. So, problem seem to be with my user account.

Any help would be greatly appreciated!

Thanks!
P.S.
Back to top
View user's profile Send private message Visit poster's website
bduncan
PostPosted: Wed Jun 19, 2002 9:24 am    Post subject: Reply with quote

Padawan

Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley

What platform are you using? Also, try using the dspmqaut and setmqaut programs to look at, and if necessary, change your user's permissions...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator
Back to top
View user's profile Send private message Visit poster's website AIM Address
bower5932
PostPosted: Wed Jun 19, 2002 10:30 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA

I would guess that the userid of your client isn't part of the mqm group on the machine where your qmgr resides. When you tried to connect in, you would have used a channel that has an mcauser property that is probably blank (which means use the logged on userid). You could change this to the mqm user, but then anybody would be able to connect in on the channel.
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
cvshiva
PostPosted: Wed Jun 19, 2002 8:50 pm    Post subject: Reply with quote

Apprentice

Joined: 04 Mar 2002
Posts: 35
Location: Chennai

Hi ,

Check whether the MQServer contains an user account in the name with which you logon to the client if so You can try to add your Client user account in the MqServer's mqm group if you need to have all admin rights on the Queue Manager. Or you can create a new group called "mqusers"
and add your user account to this group.

You should then use "setmquat" on the Queue Manager to grant necessary rights to the "mquser" group.

Details of "setmqaut" and "dspmqaut" can be found in "System Administration manual , Protecting MQ Objects Section"

After this try connecting from the client. It should be fine.

You can try setting the MCAUSER property of the channel , but it is dangerous as anybody ( even a hacker ) can connect and screw up things on your MQServer... this is a big security risk


Regards
_________________
Ramnath Shiva
IBM Certified SOA Specialist
IBM Certified MQSeries Specialist
Standard Scope International Pvt Ltd , Chennai
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger MSN Messenger
glen
PostPosted: Wed Jun 19, 2002 11:55 pm    Post subject: Reply with quote

Novice

Joined: 05 Jun 2002
Posts: 13
Location: Dublin, Ireland.

At least you aren't getting 2059's.

I had this problem when I had an NT4/MQServer in a DMZ - this did not have the rights to verify the SID of the client, in a foreign domain. Trusting the domain was not an option.

Security in OAM was set to Default.

I worked around this by creating an identical (local) account to that used on the client pc on the MQS .. different passwords did not seem to make any difference. I did add the new local account to MQM.

you could also try to use setmqaut +alladm +all on the queue
Back to top
View user's profile Send private message
cvshiva
PostPosted: Thu Jun 20, 2002 4:45 am    Post subject: Reply with quote

Apprentice

Joined: 04 Mar 2002
Posts: 35
Location: Chennai

Hi Glen,

That's what I did too... for the client to connect to my MQS..
but I didn't add the newly created user account to "MQM" group but to a new group created for all MQCLIENTS called "MQUSERS" .. with only specific rights granted to them ( This was useful for me to protect MQ Objects and enforce security .. and control over MQServer)..

That should certainly work


Regards
_________________
Ramnath Shiva
IBM Certified SOA Specialist
IBM Certified MQSeries Specialist
Standard Scope International Pvt Ltd , Chennai
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger MSN Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » Reason code 2035
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.