|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
How to remotely connect to Config Manager of WBIMB V5? |
« View previous topic :: View next topic » |
Author |
Message
|
pamorn |
Posted: Wed May 17, 2006 11:22 pm Post subject: How to remotely connect to Config Manager of WBIMB V5? |
|
|
Newbie
Joined: 03 May 2006 Posts: 7 Location: Bangkok, Thailand
|
I have a WBIMB V5 Config Mgr installed on W2K Machine, the configuration domain was created here. It can deploy and manage broker running on AIX properly. My situation is i want to have another development machine (WinXP) installing Message Broker Toolkit to remotely connect to the Config Mgr (W2K). On Broker Administration Perspective, after supplying the remote domain Queue Mgr+Host+Port, connection to the domain raised the following exception prompt:
------------------------------------------------------------------------------------
BIP0889E: An exception occured while communicating with the Config Mgr
Details:
TopicRoot information was not received from the Configuration Manager. Either the Configuration Manager is not available or the user 'mqsicf@winxp' does not have authority to view the object. (UUID='TopicRoot', required attribute='topicroot.defaultpolicy')
------------------------------------------------------------------------------------
Additionally, in Domains View, '(Restricted Access)' was marked after Broker Topology & Topics and can not proceed anything under the Broker Topology.
I logged in to WinXP machine with User/Password that match with User/Password running config mgr service on W2K. The user on WinXP belongs to all the mq* groups already.
On W2K machine, there were many errors raised on Event Viewer, as followings:
#Warning#=======================================
Unable to obtain account details for channel MCA user ID.
WebSphere MQ was unable to obtain the account details for MCA user ID 'mqsicf@winxp'. This user ID was the MCA user ID for channel 'SYSTEM.BKR.CONFIG' on queue manager CONFIGMGRQM' and may have been defined in the channel definition, or supplied either by a channel exit or by a client.
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.
==============================================
#Error#=========================================
( ConfigMgr ) Error in call LookupAccountSid() to the NT security domain with return code 87.
A component of WebSphere Business Integration Message Brokers is attempting to call the NT security domain. The security subsystem returned an error code.
Check NT security subsystem documentation for the reported error. Restart the relevant service component (UserNameServer, or Configuration Manager). Ensure that a Domain Controller, either Primary or Backup, is available.
==============================================
Anyone know the trick to solve this problem, please give me an advice. Thank you. |
|
Back to top |
|
 |
mqmatt |
Posted: Thu May 18, 2006 5:40 am Post subject: |
|
|
 Grand Master
Joined: 04 Aug 2004 Posts: 1213 Location: Hursley, UK
|
If you're not authenticating using Windows domains, then try disabling domain support:
Code: |
mqsichangeconfigmgr -l 0 |
Regards
-Matt |
|
Back to top |
|
 |
pamorn |
Posted: Thu May 18, 2006 8:33 pm Post subject: |
|
|
Newbie
Joined: 03 May 2006 Posts: 7 Location: Bangkok, Thailand
|
Bravo!!
It works!!!
Thank you Matt..  |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|