| Author |
Message
|
| ngoanhtuan |
 Posted: Wed Oct 10, 2007 3:21 am Post subject: error when deploy .bar file to execution group |
 |
|
Newbie
Joined: 07 Sep 2007
Posts: 5
|
hi all
I encountered the error message below when deploy .bar file to the execution group. I have 2 PC run XP SP2 - 1 dev machine and 1 production machine. My .bar file has been successfully deployed in dev machine but I got this message in production machine (same .bar file). Does anyone knows the root cause of it.
many thanks
TuanSandman
----------------------------
BIP1536S: The Configuration Manager was unable to register for internal subscriptions with broker POC_BROKER.
Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker POC_BROKER was not successful. This means that Message Brokers Toolkit and Config Manager Proxy applications may not show the correct status of the resources assigned to broker POC_BROKER.
Look in the system log for messages that indicate the cause of this problem. Correct the cause and redeploy to this broker. If this problem persists, contact your IBM support center. |
|
| Back to top |
|
 |
| vgollakota |
| Posted: Wed Oct 10, 2007 4:10 am Post subject: Re: error when deploy .bar file to execution group |
|
|
Apprentice
Joined: 19 Feb 2007
Posts: 37
|
| ngoanhtuan wrote: |
hi all
I encountered the error message below when deploy .bar file to the execution group. I have 2 PC run XP SP2 - 1 dev machine and 1 production machine. My .bar file has been successfully deployed in dev machine but I got this message in production machine (same .bar file). Does anyone knows the root cause of it.
many thanks
TuanSandman
----------------------------
BIP1536S: The Configuration Manager was unable to register for internal subscriptions with broker POC_BROKER.
Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker POC_BROKER was not successful. This means that Message Brokers Toolkit and Config Manager Proxy applications may not show the correct status of the resources assigned to broker POC_BROKER.
Look in the system log for messages that indicate the cause of this problem. Correct the cause and redeploy to this broker. If this problem persists, contact your IBM support center. |
Hi,
Did u try with this option...!
Go to the control center while connected to the
old CM and unregister the broker in question. Deploy the topology.
Reconnect the control center to the new CM and register the broker. Deploy
that topology. Depending on your version and CSD, you may have to do a bit
of cleanup of the old broker UUID in the database, but you should not have
to do this. You will see UUID errors when trying to register the broker in
the new domain. And try to resolve them...if any..
_________________
G.VANDANA |
|
| Back to top |
|
|
| mqmatt |
| Posted: Wed Oct 10, 2007 4:28 am Post subject: Re: error when deploy .bar file to execution group |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| vgollakota wrote: |
Did u try with this option...!
Go to the control center while connected to the
old CM and unregister the broker in question. Deploy the topology.
Reconnect the control center to the new CM and register the broker. Deploy
that topology. Depending on your version and CSD, you may have to do a bit
of cleanup of the old broker UUID in the database, but you should not have
to do this. You will see UUID errors when trying to register the broker in
the new domain. And try to resolve them...if any.. |
Woah, I would certainly not recommend this. At least, if you need to keep your broker alive. Only remove the broker from the domain as a last resort.
Instead, work out why the subscriptions cannot be registered (search this forum for advice, and look in the syslog for clues) and fix it. |
|
| Back to top |
|
|
| ngoanhtuan |
| Posted: Fri Oct 12, 2007 12:59 am Post subject: |
|
|
Newbie
Joined: 07 Sep 2007
Posts: 5
|
I tried but got still the same error  . I have just used MQ Explorer to check channels in 2 environments.
- In the environment that I got the error, only channel SYSTEM.BRK.CONIFG is running
- In the environment that it runs well, there're 3 channels: SYSTEM.BRK.CONFIG, SYSTEM.ADMIN.SRVCONN and SYSTEM.DEF.SRVCONN are running.
does anyone know why
many thanks
TuanSandman |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Oct 12, 2007 1:57 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Those channels have nothing to do with your issue -those are all used by things like MQExplorer or Toolkit, and not by ConfigMgr.
You need to confirm that you have working channels (like TO.BROKER and TO.CONFIG) on Broker qmgr and ConfigMgr queue manager.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Fri Oct 12, 2007 3:04 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| Do what Jeff says... and as I said above, search the forum and look in the system log for clues. |
|
| Back to top |
|
|
|
|
