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 » WebSphere Message Broker (ACE) Support » Can't connect to Local Queue manager

Post new topic  Reply to topic Goto page 1, 2  Next
 Can't connect to Local Queue manager « View previous topic :: View next topic » 
Author Message
Veera B
PostPosted: Thu Feb 21, 2013 6:35 pm    Post subject: Can't connect to Local Queue manager Reply with quote

Voyager

Joined: 16 Jan 2013
Posts: 76

Hi All,

I am not able to connect to local queue manager from MQ explorer. But i am able to connect to Remote queue managers.

I did not mind this earlier but for using MB user trace i am having problem running mqsireadlog and mqsiformattrace commands. its giving me cant connect to queue manager error ..

some suggestions pls ...
Back to top
View user's profile Send private message
visasimbu
PostPosted: Thu Feb 21, 2013 9:30 pm    Post subject: Reply with quote

Disciple

Joined: 06 Nov 2009
Posts: 171

Provide more information..

Like MQRC or what is the error message your getting while try to connect local QM in MQ explorer, etc.,
Back to top
View user's profile Send private message Send e-mail
Veera B
PostPosted: Thu Feb 21, 2013 11:57 pm    Post subject: Reply with quote

Voyager

Joined: 16 Jan 2013
Posts: 76

I dont have a mqrc .. in my MQ explorer the Local queue managers are getting displayed in some pale color and none of the sub folders or objects are visible. but i am able to view and use all objets of remote queue managers.

when i try to user mqsireadlog command i get the below error in Command console.

BIP8032E: Unable to connect to a WebSphere MQ queue.
An attempt was made to connect to the component's WebSphere MQ Queue Manager and queue, this attempt was unsuccessful.
Ensure that the components WebSphere MQ Queue Manager and queue are available, running and that the user has sufficient authority to access them.
Back to top
View user's profile Send private message
ceteareth
PostPosted: Fri Feb 22, 2013 12:20 am    Post subject: Reply with quote

Acolyte

Joined: 12 Aug 2012
Posts: 51

you may try checking if your user account is a member of mqm and mqbrkrs user groups.
Back to top
View user's profile Send private message
Veera B
PostPosted: Fri Feb 22, 2013 12:44 am    Post subject: Reply with quote

Voyager

Joined: 16 Jan 2013
Posts: 76

ceteareth wrote:
you may try checking if your user account is a member of mqm and mqbrkrs user groups.


That's already taken care. If the user is not a memeber of mqm and mqbrkrs, i think i cannot access the remote queue managers aswell ...
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Feb 22, 2013 4:18 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Veera B wrote:
ceteareth wrote:
you may try checking if your user account is a member of mqm and mqbrkrs user groups.


That's already taken care. If the user is not a memeber of mqm and mqbrkrs, i think i cannot access the remote queue managers aswell ...

On Windows you will more likely as not also need to be member of the administrator group, or need to run this from an elevated state. (right click and run as administrator)

run as without space = contact admin!!!

Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
mgk
PostPosted: Fri Feb 22, 2013 7:01 am    Post subject: Reply with quote

Padawan

Joined: 31 Jul 2003
Posts: 1642

Quote:
On Windows you will more likely as not also need to be member of the administrator group,


Not the case with more recent versions of Broker - We have tried hard to reduce the number of occasions on which you need to elevate. The most common reason is creating a new Broker which needs elevation as it creates a new Windows Service. Other than that, for most things you just need to be a member of the mqbrkrs group. There is certainly no requirement to be an Administrator or to run the broker with a service user id that is an Administrator either - again membership of mqbrkrs is the only requirement.

Kind regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
Back to top
View user's profile Send private message
Veera B
PostPosted: Sun Feb 24, 2013 11:14 pm    Post subject: Reply with quote

Voyager

Joined: 16 Jan 2013
Posts: 76

fjb_saper wrote:
On Windows you will more likely as not also need to be member of the administrator group, or need to run this from an elevated state. (right click and run as administrator)

run as without space = contact admin!!!

Have fun


mgk wrote:
Not the case with more recent versions of Broker - We have tried hard to reduce the number of occasions on which you need to elevate. The most common reason is creating a new Broker which needs elevation as it creates a new Windows Service. Other than that, for most things you just need to be a member of the mqbrkrs group. There is certainly no requirement to be an Administrator or to run the broker with a service user id that is an Administrator either - again membership of mqbrkrs is the only requirement.



My account is part of Administrator , mqm and mqbrkrs user groups.

dont know why this is happening ...
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Feb 25, 2013 3:36 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

bounce the box and try again...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Veera B
PostPosted: Tue Feb 26, 2013 6:48 am    Post subject: Reply with quote

Voyager

Joined: 16 Jan 2013
Posts: 76

fjb_saper wrote:
bounce the box and try again...


Bounce the box means restart right ?

but this is a windows machine and i restarted it a few times ..
Back to top
View user's profile Send private message
mayheminMQ
PostPosted: Tue Feb 26, 2013 8:25 am    Post subject: Reply with quote

Voyager

Joined: 04 Sep 2012
Posts: 77
Location: UK beyond the meadows of RocknRoll

By any chance is the local IBM Websphere MQ Service running? If it is not ruuning, you will still be able to connect to your remote queue managers but your Queue manager will be greyed out.
_________________
A Colorblind man may appear disadvantaged but he always sees more than just colors...
Back to top
View user's profile Send private message
Veera B
PostPosted: Wed Feb 27, 2013 1:00 am    Post subject: Reply with quote

Voyager

Joined: 16 Jan 2013
Posts: 76

Yes, local MQ service is running ...
Back to top
View user's profile Send private message
longng
PostPosted: Wed Feb 27, 2013 10:40 am    Post subject: Reply with quote

Apprentice

Joined: 22 Feb 2013
Posts: 42

What's the response/return code when you run the sample amqsput/amqsputc to the local queue manager?
Back to top
View user's profile Send private message
ramires
PostPosted: Wed Feb 27, 2013 3:34 pm    Post subject: Reply with quote

Knight

Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa

try to run MQ Explorer as administrator, from here:

https://www.ibm.com/developerworks/forums/message.jspa?messageID=14778337

"We need to execute the MQ Explorer as an administrator (On Windows) in case the permissions for that particular local account is not set properly."
Back to top
View user's profile Send private message
Veera B
PostPosted: Thu Feb 28, 2013 11:23 pm    Post subject: Reply with quote

Voyager

Joined: 16 Jan 2013
Posts: 76

longng wrote:
What's the response/return code when you run the sample amqsput/amqsputc to the local queue manager?


I am not seeing any error code, but in event viewer i am getting warning as follows ..

Access was denied when attempting to retrieve group membership information for user 'na@portald'.

WebSphere MQ, running with the authority of user 'brka@dell-XXX', was unable to retrieve group membership information for the specified user.

Ensure Active Directory access permissions allow user 'brka@dell-XXX' to read group memberships for user 'na@portald'. To retrieve group membership information for a domain user, MQ must run with the authority of a domain user.

ramires wrote:
We need to execute the MQ Explorer as an administrator (On Windows) in case the permissions for that particular local account is not set properly


I dont understand my used id is part of Admin group. what do you mean by not set properly ..
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Can't connect to Local Queue manager
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.