| Author |
Message
|
| cvanmook |
 Posted: Tue Oct 05, 2004 1:04 pm Post subject: Configuration Manager unable to register for internal subscr |
 |
|
Novice
Joined: 16 Jan 2004
Posts: 23
|
Hello,
After each deployment we've got an error in the errorlog of the configmgr. We're using WBIMB 5.0 csd03. The deployment are working ..
The error is :
=============================================
Description:
( ConfigMgr ) Configuration Manager unable to register for internal subscriptions with broker WBRK01.
Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker WBRK01 was not successful. This means that the Message Brokers Toolkit may not reliably show the correct status of the resources assigned to broker WBRK01. The Configuration Manager also writes this message to the system event log, accompanied by other messages giving details of the problem.
Look at the messages for this problem in the system event log. Determine and correct the cause of the problem before attempting to deploy to this broker again. If this problem persists, contact your IBM support center.
Data:
============================================
If we look futher we got the error :
============================================
Description:
( ConfigMgr ) User id 'mqmadmin' not authorized to put to queue 'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'WCFM' using accounting token '0000000000000000000000000000000000000000000000000000000000000000'.
The user is not authorized to put a message on the named queue.
Ensure the user is allowed to perform this operation. This may involve configuring the WebSphere Business Integration settings for this queue, or using an alternative userid which is authorized.
============================================
We've normally created the configmgr and if we try to put on the queue it is no problem. Does anybody have any ideas.
Thanx,
Christan |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Oct 05, 2004 4:27 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You have a broker on one machine, and a configuration manager on the other, yes?
You have different service users configured for each broker component on each machine, yes?
The service user of the Configuration manager is not authorized on the broker queue manager, or the other way around.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| cvanmook |
| Posted: Wed Oct 06, 2004 1:34 pm Post subject: |
|
|
Novice
Joined: 16 Jan 2004
Posts: 23
|
Yes we've a Broker running on a AIX5.2 system. The configmgr is running on WIN2000 with the queuemanager WCFM. The configmgr is running with user mqmadmin the WCFM queuemanager also ... both in mqm group so i don't understand the message. I've tried to put an message on the queue when i was logged on with user mqmadmin and that works ... but we keep getting these errors after each deployment.
( ConfigMgr ) User id 'mqmadmin' not authorized to put to queue 'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'WCFM'
Christan. |
|
| Back to top |
|
|
| cvanmook |
| Posted: Wed Oct 06, 2004 1:37 pm Post subject: |
|
|
Novice
Joined: 16 Jan 2004
Posts: 23
|
Oh , on the unix system we have only user mqm ... this user is running the broker and is in the mqm group. Must we need to create a mqmadmin user on the unix ??
Thanx,
Christan |
|
| Back to top |
|
|
| devasis_sahu |
| Posted: Mon Oct 11, 2004 4:33 am Post subject: Environment |
|
|
Newbie
Joined: 11 Oct 2004
Posts: 3
|
Can you please tell the Environment. where is the Configmanager installed and what are the configurations of the domain. If your broker domain is on Windows , Check if the File and Print service and Client for Microsoft networks are installed. If it is Windows , chances are that it will be solved instantly.
Regds |
|
| Back to top |
|
|
| kirani |
| Posted: Mon Oct 11, 2004 10:20 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
| cvanmook wrote: |
Oh , on the unix system we have only user mqm ... this user is running the broker and is in the mqm group. Must we need to create a mqmadmin user on the unix ??
|
Yes.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| venkat kurra |
| Posted: Mon Feb 07, 2005 10:06 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
Right now i am in the same situation and need more expalnation about this problem.
We are planning to run a configuration manager in the "DOMAIN1" domain and the server is Windows 2003. But the broker want to be on Windows 2000 in the "DOMAIN2" domain.
Created a configuration with the service-id called DOMAIN1/mq_2003 (mq_2003 id was defined in the DOMAIN1 domain).
mqsicreateconfigmgr -i DOMAIN1\mq_2003 -a <passwd> -q MQSICMQ1 -n MQSICMDB -u db2_id -p db2_passwd -l 2
Service up and running and no problem to connect to the configuration manager with my ID(part of win2000 domain and added to all groups)
Broker is created with a different local id called mqbk_2000 on the windows 2000 server.
The broker deploy was unsuccessfull with the following errrors,
( ConfigMgr ) Configuration Manager unable to register for internal subscriptions with broker BROKER.
Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker BROKER was not successful. This means that the Message Brokers Toolkit may not reliably show the correct status of the resources assigned to broker BROKER. The Configuration Manager also writes this message to the system event log, accompanied by other messages giving details of the problem.
Look at the messages for this problem in the system event log. Determine and correct the cause of the problem before attempting to deploy to this broker again. If this problem persists, contact your IBM
Error on the config EventViewer
( ConfigMgr ) Error detected whilst processing a message in node 'DynamicSubscriptionEngine'.
The message broker detected an error whilst processing a message in node 'DynamicSubscriptionEngine'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
( ConfigMgr ) User id 'mq_2003' not authorized to put to queue 'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'MQSICMQ1' using accounting token '0000000000000000000000000000000000000000000000000000000000000000'.
The user is not authorized to put a message on the named queue.
Ensure the user is allowed to perform this operation. This may involve configuring the WebSphere Business Integration settings for this
Now the question is adding an ID, DOMAIN1/mq_2003 to the wbimb groups on the Broker server(DOMAIN2 domain). Shell we create just a local id, mq_2003 on the Broker server? or do we need any additional domain level setup?
Also do we need the broker id(mqbk_2000) on the configuration box?[/quote]
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
|
|
