MQSeries.net :: View topic

anantha sreenivasan · Posted: Mon Oct 01, 2007 11:21 pm Post subject:

Mqsichangeflowstats error

C:\Program Files\IBM\MQSI\6.0>mqsichangeflowstats BROKER1 -s -e default -f Test1
-c active -t basic -n advanced -o usertrace
BIP2087E: Broker BROKER1 was unable to process the internal configuration messag
e.
The entire internal configuration message failed to be processed successfully.
The internal configuration message failed to be processed, use the messages foll
owing this message to determine the reasons for the failure.
BIP2062E: Broker BROKER1 (UUID 7e41395a-1501-0000-0080-f6790977332c) execution g
roup 'default' (UUID e5594a5a-1501-0000-0080-f6790977332c) detected that the dep
loyed configuration message received contained an invalid XML tag.
The configuration message received could not be applied to the broker's configur
ation. This could occur for either of the following reasons: (a) The configurati
on message XML tag directs an execution group to be created but the execution gr
oup already exists. (b) The configuration message XML tag directs an execution g
roup to be changed but the execution group does not exist. The configuration mes
sage is rejected.
Use the Message Brokers Toolkit, mqsideploy command or Config Manager Proxy to r
edeploy to the execution group. Contact your IBM support center if you are unabl e to resolve the problem.

BIP8045E: The message flow is not available.
The message flow could not be found; it may have been deleted by the Message Bro
kers Toolkit or a Config Manager Proxy application.
Use the Message Brokers Toolkit or Config Manager Proxy to see if the message fl
ow exists.

C:\Program Files\IBM\MQSI\6.0>mqsichangeflowstats BROKER1 -s -e default -j -c ac
tive -t basic -n advanced -o usertrace
BIP2087E: Broker BROKER1 was unable to process the internal configuration messag
e.
The entire internal configuration message failed to be processed successfully.
The internal configuration message failed to be processed, use the messages foll
owing this message to determine the reasons for the failure.
BIP2062E: Broker BROKER1 (UUID 7e41395a-1501-0000-0080-f6790977332c) execution g
roup 'default' (UUID e5594a5a-1501-0000-0080-f6790977332c) detected that the dep
loyed configuration message received contained an invalid XML tag.
The configuration message received could not be applied to the broker's configur
ation. This could occur for either of the following reasons: (a) The configurati
on message XML tag directs an execution group to be created but the execution gr
oup already exists. (b) The configuration message XML tag directs an execution g
roup to be changed but the execution group does not exist. The configuration mes
sage is rejected.
Use the Message Brokers Toolkit, mqsideploy command or Config Manager Proxy to r
edeploy to the execution group. Contact your IBM support center if you are unable
to resolve the problem.

BIP8036E: Negative response received.
This command sends an internal configuration message to the broker, the response
received indicated that the internal configuration message was unsuccessful.
Check that the WebSphere MQ transport is available. Check the system log for fur
ther information.

The Execution Group and message flow exists and when i try to delta deploy, the following error occurs.

BIP1536S: The Configuration Manager was unable to register for internal subscriptions with broker BROKER1.

Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker BROKER1 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 BROKER1.

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.

No errors were recorded in the Windows Event Viewer

What should be done to remedy this situation?