| Author |
Message
|
| ayanc |
 Posted: Sun Jul 31, 2005 9:13 pm Post subject: Broker (Restricted Access) |
 |
|
Voyager
Joined: 15 Nov 2004
Posts: 88
|
Hi All,
I have the following configuration:
v5.0 config manager and toolkit installed in Windows 2000 m/c. Websphere MQ CSD08 installed in the same m/c.
v5.0 broker installed in HP-UX. Websphere MQ CSD07 installed on the unix m/c.
I am using Remote Desktop to connect to the windows m/c and my user is added to the appropriate groups.
I am getting Broker (Restricted Access) problem. I searched the posts and found the domain awareness issue. I therefore used the command mqsichangeconfigmgr -l 0 to make the config mgr domain unaware. However the problem persists.
Any ideas??? Also could some one tell me how to find out the CSD level of WBIMB? The mqver command shows the CSD level of Websphere MQ.
Thanks. |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Sun Jul 31, 2005 10:48 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi ayanc,
I have noticed this error once in a while. The causes can be many but they are mostly not related to CSD's etc.
Have a look in your users and check if db2admin user or MQAdmin has been locked out...it will be a tick mark in the user properties.
Check if all the db2 and MQSeries and ConfigMgr, Broker are running on LocalSystem in the services...
Let us know if these dont fix it. |
|
| Back to top |
|
|
| ayanc |
| Posted: Sun Jul 31, 2005 11:21 pm Post subject: |
|
|
Voyager
Joined: 15 Nov 2004
Posts: 88
|
Hi elvis,
Thanx for ur reply.
I checked that the users are not locked out, the services are up and running.
My CSD question was not related to the current topic. However since I wanted to provide the info ... I could not obtain it. |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Mon Aug 01, 2005 12:42 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
If you go to help--> About Message Broker.....
You will find something like 5.0.x.....x will state the CSD of WBIMB.
Your restricted access is due to the user not having rights. But there are many places where you can give rights...one was the users, second services...
The problem has to be that you do not have admin rights over MQSeries or DB2...u'll have to find out which one... |
|
| Back to top |
|
|
| ayanc |
| Posted: Mon Aug 01, 2005 1:04 am Post subject: |
|
|
Voyager
Joined: 15 Nov 2004
Posts: 88
|
Hi elvis,
Thanks for the CSD info. My WBIMB CSD level is 4.
The user I am using to log-on has full admin rights. I checked it out from the groups. I found that the id has been added to all the mq related groups and administrators.
Services: MQSeries log - on Local System, Config Mgr Log on User.
I can start or stop config mgr using services.
However if u suggest some specific checks I can do it. |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Mon Aug 01, 2005 1:44 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Are all the DB2 services started(and on local system)...DB2 governor and DB2-DB2-0 must be started....start all would be my suggestion...
Your user should have Administrator,5 wbimb security groups,mqm and Users. In Groups-->Users u should have db2admin,and your userid added.
I myself am running out of ideas  try these...and i'll think of some more if possible  |
|
| Back to top |
|
|
| ayanc |
| Posted: Mon Aug 01, 2005 3:50 am Post subject: |
|
|
Voyager
Joined: 15 Nov 2004
Posts: 88
|
Hi elvis,
I checked on the groups and found them to be allright. All the groups have db2admin and the userid.
As far as services are concerned ... all are up and running. 
However some are running under db2admin and some under local system. Is there a concern about the log-on user for services?
I believe the set up is as governed by the default installation proceedures.
I feel the broker has been deleted improperly and recreated. Can this be the cause of the above error? |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Mon Aug 01, 2005 10:45 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
U created the broker using the Broker application or the command line...In either case the creation should have been "successfully
completed"
Let all the db2 services be on local system...make all the services Automatic and restart your pc...Even the configmgr and broker should be Automatic.
The log-on can be a issue as ur databases might use the db2 usernames and passwords whereas during deployment it will try ur local username and password to connect...
During the creation from Broker, u would have used the Existing User name and password, and entered the local user details.....Did you uncheck the tick box below which states something like "use this for all the db2services"......
Do uncheck that and create the configMgr again... |
|
| Back to top |
|
|
|
|
