MQSeries.net :: View topic

anantha sreenivasan · Posted: Wed Jul 04, 2007 3:15 am Post subject:

I'm Getting the following error while trying to delete the BROK1 instance from toolkit and trying to recreate it with the same name or different name

BIP1511E: Queue manager 'BROKQM' cannot be associated with broker 'BROK1'; it is already associated with broker 'BROK1'.

An attempt was made to associate broker BROK1 with WebSphere MQ queue manager BROKQM, but broker BROK1 already has this association. A WebSphere MQ queue manager can only have one broker associated with it.

Change the queue manager for one of the brokers. If this problem occurs after you have deleted broker BROK1 then tried to recreate it, you must first initiate a deploy operation to automatically delete the configuration from the real broker. It is only after all types of configuration data (message flows, message sets, topology, topics) have been successfully deleted from the real broker that the broker document is finally deleted from the configuration repository. Until that time the queue manager can not be associated with another broker. Once this has been done, you must also physically delete and recreate the real broker using the mqsideletebroker and mqsicreatebroker commands.
____________________________________________________________
BIP1711W: Broker is not accessible or does not exist.

An attempt was made to register for information on the Broker with UUID '73fbe390-1301-0000-0080-91fbe5847f4f', but either the user who asked for the information does not have sufficient authority to do so or the Broker does not exist.

Ensure that the user of the application that issued the request has sufficient authority to view the Broker. If the user has sufficient authority and the object exists, attempt to retry the operation. If the problem persists please turn on Configuration Manager tracing to capture the error and contact your IBM support center.
____________________________________________________________
BIP1711W: ExecutionGroup is not accessible or does not exist.

An attempt was made to register for information on the ExecutionGroup with UUID '74fbe390-1301-0000-0080-91fbe5847f4f', but either the user who asked for the information does not have sufficient authority to do so or the ExecutionGroup does not exist.

Ensure that the user of the application that issued the request has sufficient authority to view the ExecutionGroup. If the user has sufficient authority and the object exists, attempt to retry the operation. If the problem persists please turn on Configuration Manager tracing to capture the error and contact your IBM support center.
____________________________________________________________
BIP1510E: Unable to deploy configuration data.

An attempt was made to deploy configuration data to one or more brokers, but the Configuration Manager is already deploying to broker BROK1. You can not deploy to a set of brokers if there is an earlier deploy outstanding to any broker in the set. The deploy operation was not performed.

Wait for the outstanding deploy to complete before retrying the operation. The Event Log Editor may be used to check that all responses to the outstanding deploy have been received and processed. If the outstanding deploy does not fully complete in a suitable period of time, check that all brokers exist and are running, all WebSphere MQ queue managers are running, and that all channels between queue managers are started. Also check that deploy messages have been correctly delivered to the target brokers, and have not been put to the dead letter queue. Correct any problems you find. If it still does not complete, then cancel the deploy operation by specifying the 'Cancel' option in the Message Brokers Toolkit Note that 'Cancel' affects all outstanding deployment operations throughout the domain, so you may not have the authority to perform this.