MQSeries.net :: View topic

syangloo · Posted: Tue Nov 05, 2002 4:08 pm Post subject:

Dear All,

I install a config manager and broker in different server, config manager in a normal PC with Win2k server and broker in HPUX server.

Now i want to remove the old config manager from the server and install it in to a new PC. Broker still remain the same.

I naming cfgmgr qmgr as the old cfgmgr qmgr. After created the cfgmgr and qmgr i create the broker as the same name with the exisitng one in the topology.

When i try to deploy the new config manager with the broker, i hit the error message as below:
-------------------------------------------------------------------------------------
BIP1536S: Configuration Manager unable to register for internal subscriptions with broker QD.BK.KL.001.

Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker QD.BK.KL.001 was not successful. This means that the Control Center Operations view may not reliably show the correct status of the resources assigned to broker QD.BK.KL.001. 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.
--------------------------------------------------------------------------------------

BIP2087E: Broker QD.BK.KL.001 was unable to process the internal configuration message.

The entire internal configuration message failed to be processed successfully.

The internal configuration message failed to be processed, use the messages following this message to determine the reasons for the failure.
--------------------------------------------------------------------------------------

BIP2045E: Broker QD.BK.KL.001 (UUID 4f57a263-ee00-0000-0080-e82c4881cabe) running on WebSphere MQ queue manager 'QD.BK.KL.001' could not process an internal configuration message because the broker identity received in the message (UUID d9c86a52-f100-0000-0080-cc7aecfa6d7d) did not match that of this broker.

An internal configuration message could not be processed and was rejected. Each broker is identified by a universally unique identifier called a UUID which is allocated when the Control Center user creates a definition for the broker. The configuration message received contained a broker UUID (d9c86a52-f100-0000-0080-cc7aecfa6d7d) that does not match the UUID of broker QD.BK.KL.001 running on WebSphere MQ queue manager QD.BK.KL.001. There are two possible reasons for this. Either a Control Center user has accidentally specified queue manager QD.BK.KL.001 when defining another broker so that messages destined for the other broker have arrived at this broker, or the definition for broker QD.BK.KL.001 was deleted and recreated on the Control Center which has the effect of giving broker QD.BK.KL.001 a new, different UUID.

If the queue manager name specified in the Control Center was incorrect then use the Control Center to correct the broker definition in error. The mqsilist command may be used to display broker queue manager names. Otherwise, if the broker definition was deleted and recreated, you must use the mqsideletebroker and mqsicreatebroker commands to recreate the broker, then redeploy the configuration for the broker in order to reestablish the correct broker identity. To avoid loss of data when recreating the broker, make sure that you follow the sequence of actions defined in the WebSphere MQ Integrator Administration Guide section 'Recovery and restart'.

--------------------------------------------------------------------------------------

We can't have a same Cfgmgr qmgr in same broker?
or other issue cause for this errors?

Thanks