MQSeries.net :: View topic

Nizam · Posted: Wed Sep 29, 2004 4:51 pm Post subject:

wbimb v 5 csd 4, mq 5.3 csd7, win 2000 server.

Hi all,
This is what happened.
I saw Broker(Restricted Access) in my broker domain.
This is what i did.
1. stopped config manager and queue manager.
2. deleted config manager's database.
3. restarted the server.
4. created config manager's database.
5. created config manager.
6. started config manager.
7. Added my broker to the broker domain.
I got the following errors.
BIP2045E, BIP1536S, BIP2087E

What do you think i should do...
Thanks

Error Details from Event log:
BIP2045E: Broker WBRKTST (UUID e8673c77-fe00-0000-0080-deb6aa804b55) running on WebSphere MQ queue manager WBRKTST could not process an internal configuration message because the broker identity received in the message (UUID 1b81694c-ff00-0000-0080-deb6aa804b55) 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 user creates a definition for the broker. The configuration message received contained a broker UUID (1b81694c-ff00-0000-0080-deb6aa804b55) that does not match the UUID of broker WBRKTST running on WebSphere MQ queue manager WBRKTST. There are two possible reasons for this. Either a user has accidentally specified queue manager WBRKTST when defining another broker so that messages destined for the other broker have arrived at this broker, or the definition for broker WBRKTST was deleted and recreated on the Message Brokers Toolkit which has the effect of giving broker WBRKTST a new, different UUID.

If the queue manager name specified in the Message Brokers Toolkit was incorrect then use the Message Brokers Toolkit 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 re-establish 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 online documentation section "Recovery and restart".

BIP1536S: Configuration Manager unable to register for internal subscriptions with broker WBRKTST.

Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker WBRKTST was not successful. This means that the Message Brokers Toolkit may not reliably show the correct status of the resources assigned to broker WBRKTST. 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 WBRKTST 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.