Error 2035. Not Authorized For Access
Contents |
RSS Feed - WebSphere MQ mqconn ended with reason code 2035 Support RSS Feed - Message Broker Support
MQSeries.net Forum Index » Clustering » Error 2035 - Not authorizedDspmqaut
for access Error 2035 - Not authorized for access « View previous topic :: View next topic » Author Message MQFard Posted: Fri
Mqopen Ended With Reason Code 2035
Aug 04, 2006 10:13 am Post subject: Error 2035 - Not authorized for access NoviceJoined: 07 Oct 2004Posts: 17Location: VSP.COM We are running WebSphere MQ 5.3 fix pact 8 on Windows 2003 server. I have a http://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.tro.doc/q041060_.htm queue manager called TVSPQUE running on the server. I have installed a client on an NT desktop. When trying to connect to the queue manager via the client I’m receiving the following message: AMQ8077: Entity 'morero' has insufficient authority to access object 'TVSPQUE'. EXPLANATION: The specified entity is not authorized to access the required object. The following requested permissions are unauthorized: connect ACTION: Ensure that the correct level of authority has been set http://www.mqseries.net/phpBB/viewtopic.php?t=31120&sid=f1dcffc5665226cfe9942bed828ca228 for this entity against the required object, or ensure that the entity is a member of a privileged group. I have added morero to the MQM group and I’m still receiving this error. For the past two days I’ve been looking through manuals and searching the MQSeries.net database and everything says that if the User Id is in the MQM it should work. I have others defined in the MQM group and have no issues. We have tried changing the character case of the logon Id. We have created a new Id of the same name. I have deleted and installed the client and still receive the same results. Looking for help. _________________To Fard WebSphere MQ Administrator Back to top kevinf2349 Posted: Fri Aug 04, 2006 10:21 am Post subject: Grand MasterJoined: 28 Feb 2003Posts: 1311Location: USA I think this is in the wrong forum old chap....however..... Do you have an MCA Userid specified on the Server Conn channel? If so is this sufficiently authorised? *Warning* If you have this, this is not a very secure way of doing things. Back to top MQFard Posted: Fri Aug 04, 2006 10:25 am Post subject: NoviceJoined: 07 Oct 2004Posts: 17Location: VSP.COM Yes I realized I put in the wrong form after I submitted it. Sorry. The MCA user is blank.________________
RSS Feed - WebSphere MQ Support RSS Feed http://www.mqseries.net/phpBB2/viewtopic.php?t=13232&highlight=2035 - Message Broker Support
MQSeries.net Forum Index » General Discussion » 2035: Not authorized for access 2035: http://www.mqseries.net/phpBB/viewtopic.php?t=64459&view=previous&sid=9d35ba5097ba26a5c2c0fd49e3ccadac Not authorized for access « View previous topic :: View next topic » Author Message srinivas_sk Posted: Mon Feb 02, 2004 9:28 pm Post subject: 2035: Not authorized for access NewbieJoined: 02 Feb 2004Posts: 6 We are facing the following problem using MQ Series:- We have an application App1 installed on MachineA. Another application (server appl) App2 is installed on MachineB. App1 code 2 is compiled using the client MQ library (mqic). Now when App1 tries to do a MQCONN, it gets error 2035 (Not authorized for access). Is there any particular setting that needs to be done when using a client installation of MQ? Machine A is on HP UX 11i with MQSeries 5.2 Machines B has the same version of Mq but on HP UX 11.00 . Back to top mqonnet Posted: Tue Feb 03, 2004 5:41 am ended with reason Post subject: Grand MasterJoined: 18 Feb 2002Posts: 1114Location: Boston, Ma, Usa. You need to define a principal/userid on MachineB(remote system to which you are trying to connect to) as the same userid that you are logged on MachineA. As an aside you could as well perform a "search" on this site. There would no less than few thousand posts on this topic. Cheers Kumar Back to top srinivas_sk Posted: Tue Feb 03, 2004 8:31 pm Post subject: NewbieJoined: 02 Feb 2004Posts: 6 Thanks for the reply,Kumar. I did the same immediatly after my post and got the solution. ( the same what you have suggested). It works !! Back to top Display posts from previous: All Posts1 Day7 Days2 Weeks1 Month3 Months6 Months1 Year Oldest FirstNewest First Page 1 of 1 MQSeries.net Forum Index » General Discussion » 2035: Not authorized for access Jump to: Select a forumGeneral Discussion----------------Read First for All New to WebSphere - Only Moderators Post HereGeneral DiscussionWebSphere Technologies FAQNews/UpdatesLinksJob PostingsJob SeekersGeneral Forums InformationRequirements, Wishlists & Enhancement Requests----------------RFEs - Requirements, Wishlists & Enhancement Requests - Open ForumSponsored Forums----------------Cressida TechnologyIBM MQ Support----------------General IBM MQ SupportIBM MQ Installation/Configuration SupportClusteringIBM MQ Telemetry / Low Latency Messaging / EveryplaceMainframe, CICS, TXSeriesiSeries, OpenVMS, HP-NSSIBM MQ Performance MonitoringIBM MQ SecurityIBM MQ Development----------------IBM MQ Java / JMSIBM MQ API SupportMultiphase CommitUser ExitsWebSphere Message Broker----------------WebSphere Message Broker SupportWMB Patterns Repository - Available for DownloadWebSphere ApplicaRSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support
MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » CCSID problem CCSID problem « View previous topic :: View next topic » Author Message sarat Posted: Thu Jun 06, 2013 6:54 am Post subject: CenturionJoined: 29 Jun 2005Posts: 136Location: India Hello All, We are now facing with similar error. We have an issue at customer side for CCSID. We have special characters (Umlaut) in the incoming message with CCSID 850. But in our all Envs CCSID is 1208 and it was the same case at the customer before 2 weeks. But since last week all message logs in ESB (WMB) contains CCSID 850. Even inside WMB also there is no special setting. Broker is just carrying the same properties across the flow. We got a confirmation that default QMGR CCSID for partner system and ESB QM also 819. Where could be the possibility to over writing the CCSID !! As per above suggestions, now requested for code page for AIX machine and also Channel STATUS (If it is YES , CCSID will be taken over of OS CCSID). looking for any other suggestions !!_________________With Regards, Sarat. Back to top sarat Posted: Mon Jun 10, 2013 5:38 am Post subject: CenturionJoined: 29 Jun 2005Posts: 136Location: India I don't know the reason why my post was detached from the other thread. @ All : I was referring to this post http://www.mqseries.net/phpBB2/viewtopic.php?t=63405 @ Admin/Mod : Even, If some wants to help also they cannot as there is no reference what I'm taking about !!_________________With Regards, Sarat. Back to top rekarm01 Posted: Mon Jun 10, 2013 10:55 pm Post subject: Grand MasterJoined: 25 Jun 2008Posts: 1198 sarat wrote: We have special characters (Umlaut) in the incoming message with CCSID 850. But in our all Envs CCSID is 1208 and it was the same case at the customer before 2 weeks. So, the customer used to send messages with ccsid=1208, and