| Author |
Message
|
| wmqiadmin |
 Posted: Tue Mar 14, 2006 8:06 am Post subject: Config mgr error while connecting from toolkit |
 |
|
Disciple
Joined: 19 Jun 2005
Posts: 163
Location: epping UK
|
Hi Guys,
We are setting up QA envt. Config Mgr on win 2003, toolkit on Xp. Fix pack is installed on the toolkit and ACL entry's have been created. user has been added to mqm and mqbrks groups.
We are getting a problem while connecting to config Mgr :
| Quote: |
BIP099IE Failure response from config mgr.
Exception was thrown while processing the request for updates/config
com.ibm.broker.ConfigmanagerFatalException:[3221232488] com.ibm.broker.security.unregistery.UGRegistry Exception: Native security system error : &1
|
On Config Q manager log file say's "user doesn't have enough access authority"
Can any buddy please help me.
Thanks
in advance. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Mar 14, 2006 8:08 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
restart the configmgr and try again.
Also, what version?
What specific ACLs have been created?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wmqiadmin |
| Posted: Tue Mar 14, 2006 8:16 am Post subject: |
|
|
Disciple
Joined: 19 Jun 2005
Posts: 163
Location: epping UK
|
Sorry forgot to write version: its V6 for Config Mgr, Toolkit and Broker.
I resarted config mgr, ACL with all authority to user have been created, I tried starting toolkit from cmd line also. One more thing here we are trying to connect accross domain as we have same set up in dev. In dev we were able to connect across domain after installing toolkit's fix pack. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 14, 2006 9:13 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Okay, let's be clear about why the fixpack solved your problem in dev.
In the GA, the Toolkit would always report the user as "machineName/username". This doesn't help in a Windows domain environment that is expecting the form "domainName/username".
The RP1 for the Toolkit fixed this so that it would report "domainName/username" to the configMgr.
Now, this means that your ACLs need to be built that way too, to assign priviledges to "domainName/username".
You will also need to authorize your domain users to the configmgr's queue manager - and that can get tricky across domains. You need to ensure that the MQ service user has priviledges to all the domains your users are in.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| srikanth av |
| Posted: Tue Mar 14, 2006 9:24 am Post subject: |
|
|
Apprentice
Joined: 30 Jun 2005
Posts: 37
|
Hi wmqiadmin,
Can you please post how you have created your ACL entry.
_________________
a v srikanth |
|
| Back to top |
|
|
| wmqiadmin |
| Posted: Tue Mar 14, 2006 9:56 am Post subject: |
|
|
Disciple
Joined: 19 Jun 2005
Posts: 163
Location: epping UK
|
| Using mqsicreateaclentry cmd |
|
| Back to top |
|
|
| wmqiadmin |
| Posted: Mon Apr 24, 2006 10:26 am Post subject: |
|
|
Disciple
Joined: 19 Jun 2005
Posts: 163
Location: epping UK
|
Hi Guys,
This issue is not solved yet, Can any buddy please help me here.
As i mentioned the Dev and QA are similar, they are not similar, we have domain mqm mqbrks groups which we don't have in DEV.
Briefly:
We have Broker V6 with fix pack1, Config MgrV6 on Win 2003 and Toolkit with fix pack1 on Windows 2003 all on seperate m/cs.
Toolkit is on different domain say domain1 and Config mgr and broker are on Dev Domain. We are able to connect to dev from domain1. Now we are setting up the QA envt. we are using the same toolkit and QA is based on the DEV setup just one difference, we have created the domain mqm and mqbrks groups in this envt. as per the document we have added the users in the domain mqm groups and domain mqm mqbrks in the local administartor mqm mqbrks groups.
Still we are unable to connect through the toolkit to the config manager.
I am able to add the Configmanager Q manager on domain1 machine's MQ explorer in Hide/Show Q manager.
Error in QManager/Error folder says:
| Quote: |
WebSphere MQ was unable to obtain the account details for MCA user ID
'user@machine'. This user ID was the MCA user ID for channel
'SYSTEM.BKR.CONFIG' on queue manager 'QMANAGER' and may have been defined in
the channel definition, or supplied either by a channel exit or by a client.
ACTION:
Ensure that the user ID is correct and that it is defined on the Windows local
system, the local domain or on a trusted domain. For a domain user ID, ensure
that all necessary domain controllers are available.
|
|
|
| Back to top |
|
|
| mqmatt |
| Posted: Tue Apr 25, 2006 3:51 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| I think this was a bug that was fixed in runtime FP01. |
|
| Back to top |
|
|
| wmqiadmin |
| Posted: Tue Apr 25, 2006 4:21 am Post subject: |
|
|
Disciple
Joined: 19 Jun 2005
Posts: 163
Location: epping UK
|
| mqmatt wrote: |
| I think this was a bug that was fixed in runtime FP01. |
Yup, even i thought so, it worked for us in dev envt but its not working in the QA envt.
Is there any thing i am missing or do i have to install any other support pack other than Toolkit FP01. Today I am planning to install Broker Fixpack on Config manager server, lets hope so some thing should come up. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 25, 2006 4:43 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Toolkit FP1 will obviously not contain any fixes for runtime components, like ConfigMgr.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
