Author |
Message
|
rkford11 |
Posted: Fri Oct 29, 2004 8:37 am Post subject: toolkit communication with configmgr |
|
|
Partisan
Joined: 06 Jun 2004 Posts: 316
|
i try to create a new domain connection from my toolkit to the configmgr on the remote system, it gives me an error saying
MQSeriess queue manager ABC is not running and/or listener on port 1000 is not started. Start MQSeries queue manager ABC if necessary and/or ensure that listener on port 1000 is running. then, retry the operation
But my queue manager and listener are running on the remote machine. i have also made the user the memeber of the groups on the remote system.
what could be the problem.
Thanks |
|
Back to top |
|
 |
siliconfish |
Posted: Fri Oct 29, 2004 8:49 am Post subject: |
|
|
 Master
Joined: 12 Aug 2002 Posts: 203 Location: USA
|
Queue manager must exist on the same physical system as the Configuration Manager. _________________ siliconfish |
|
Back to top |
|
 |
rkford11 |
Posted: Fri Oct 29, 2004 8:54 am Post subject: |
|
|
Partisan
Joined: 06 Jun 2004 Posts: 316
|
siliconfish wrote: |
Queue manager must exist on the same physical system as the Configuration Manager. |
It does exist on the same system.
Thanks |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Oct 29, 2004 8:58 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Are there errors in the system log on your Toolkit machine?
How about on your ConfigMgr machine? _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
rkford11 |
Posted: Fri Oct 29, 2004 9:02 am Post subject: |
|
|
Partisan
Joined: 06 Jun 2004 Posts: 316
|
jefflowrey wrote: |
Are there errors in the system log on your Toolkit machine?
How about on your ConfigMgr machine? |
System log does not show any errors on both the machines.
Thanks |
|
Back to top |
|
 |
rkford11 |
Posted: Fri Oct 29, 2004 9:10 am Post subject: |
|
|
Partisan
Joined: 06 Jun 2004 Posts: 316
|
siliconfish wrote: |
What do u mean by this statement?
Quote: |
But my queue manager and listener are running on the remote machine. |
|
I meant all the components except toolkit is installed on the machine(which i am calling remote) and i am trying to interact with these components from the toolkit installed on my personal machine. |
|
Back to top |
|
 |
siliconfish |
Posted: Fri Oct 29, 2004 9:11 am Post subject: |
|
|
 Master
Joined: 12 Aug 2002 Posts: 203 Location: USA
|
Sorry, I misread your post. _________________ siliconfish |
|
Back to top |
|
 |
siliconfish |
Posted: Fri Oct 29, 2004 9:53 am Post subject: |
|
|
 Master
Joined: 12 Aug 2002 Posts: 203 Location: USA
|
Can you check if you were able to connect to the remote config qmgr using mqexplorer? _________________ siliconfish |
|
Back to top |
|
 |
rkford11 |
Posted: Fri Oct 29, 2004 10:16 am Post subject: |
|
|
Partisan
Joined: 06 Jun 2004 Posts: 316
|
siliconfish wrote: |
Can you check if you were able to connect to the remote config qmgr using mqexplorer? |
no, i am not able to connect.
Thanks |
|
Back to top |
|
 |
siliconfish |
Posted: Fri Oct 29, 2004 10:18 am Post subject: |
|
|
 Master
Joined: 12 Aug 2002 Posts: 203 Location: USA
|
ok then check the Application logs in event viewer, may be the SYSTEM.ADMIN.SVRCONN channel is not defined on the configmgr qmgr. _________________ siliconfish |
|
Back to top |
|
 |
rkford11 |
Posted: Fri Oct 29, 2004 10:57 am Post subject: |
|
|
Partisan
Joined: 06 Jun 2004 Posts: 316
|
siliconfish wrote: |
ok then check the Application logs in event viewer, may be the SYSTEM.ADMIN.SVRCONN channel is not defined on the configmgr qmgr. |
Thank you, i am able to connect to the configmgr but it gives the following error
TopicRoot information was not received from the Configuration Manager. Either the Configuration Manager is not available or the user 'ABC' does not have authority to view the object. (UUID='TopicRoot', required attribute='topicroot.defaultpolicy')
and it gives Broker Toplogy(Restricted access) and Topics (Restricted access)
Thanks |
|
Back to top |
|
 |
rkford11 |
Posted: Fri Oct 29, 2004 1:42 pm Post subject: |
|
|
Partisan
Joined: 06 Jun 2004 Posts: 316
|
[quote="rkford11"]
siliconfish wrote: |
ok then check the Application logs in event viewer, may be the SYSTEM.ADMIN.SVRCONN channel is not defined on the configmgr qmgr. |
Thank you, i am able to connect to the configmgr but it gives the following error
TopicRoot information was not received from the Configuration Manager. Either the Configuration Manager is not available or the user 'ABC' does not have authority to view the object. (UUID='TopicRoot', required attribute='topicroot.defaultpolicy')
and it gives Broker Toplogy(Restricted access) and Topics (Restricted access) and Event log gives the following error
[Configmgr] unknown user encountered within the configuration manager.
An unknown user exception was caught by the configuration manager Role manager class when calling the UGRegistry class. The user has not been given access to the resource.
Retry the operation. If the exception still occurs, turn on configuration manager tracing to capture details of the exception.
Thanks |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Oct 29, 2004 2:22 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Now you have a security configuration issue. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
kman |
Posted: Thu Nov 04, 2004 12:15 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2003 Posts: 309 Location: Kuala Lumpur, Malaysia
|
The user needs to be in mqm, mqbrkrs group. But this last error is misleading. It does not necessarily be because of user authority issue. Google search would return some different hits on this. |
|
Back to top |
|
 |
EddieA |
Posted: Thu Nov 04, 2004 7:30 am Post subject: |
|
|
 Jedi
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
|
No. Only the userid that the Broker runs under has to be in this group. The Toolkit user needs to be in the "other" groups, depending on the security requirements.
Cheers, _________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
Back to top |
|
 |
|