|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Can not deploy to Execution Group |
« View previous topic :: View next topic » |
Author |
Message
|
berguss22 |
Posted: Sun Mar 14, 2004 4:41 am Post subject: Can not deploy to Execution Group |
|
|
Apprentice
Joined: 10 Mar 2004 Posts: 31
|
When trying to deploy the sample TextMessanger Flow I get the following error in the event log (I deployed it before and then deleted it)
BIP2062E: Broker WBRK_BROKER (UUID 55b7573f-fb00-0000-0080-8c03ef935156) Execution Group 'default' (UUID e711ad49-fb00-0000-0080-8c03ef935156) detected that the deployed configuration message received contained an invalid XML tag.
The configuration message received could not be applied to the broker's configuration. This could occur for any of the following reasons: The configuration message XML tag directs an execution group to be created but the execution group already exists. The configuration message XML tag directs an execution group to be changed but the execution group does not exist. The configuration message is rejected.
Use the Message Brokers Toolkit to redeploy to the Execution Group. Contact your IBM support center if you are unable to resolve the problem.
What do I do?? |
|
Back to top |
|
 |
vedbhat |
Posted: Sun Mar 14, 2004 4:58 pm Post subject: |
|
|
 Disciple
Joined: 19 Mar 2002 Posts: 186 Location: Singapore
|
Install CSD 2 for WBIMB 5 and then create your Broker and Deploy the message flows again. It should work. _________________ IBM Certified Solutions Expert - MQSeries Workflow
IBM Certified Specialist - MQSeries |
|
Back to top |
|
 |
waugh |
Posted: Fri Mar 19, 2004 5:57 am Post subject: |
|
|
 Master
Joined: 19 Feb 2004 Posts: 225
|
try this,
1) right click broker on your topology choose REMOVE DEPLOYED CHIDREN, that will delete all the exisiting execution groups, and will RE-create the default e.group.
2) Right click broker and create a new execution group, give a name you wanted...
3) deploy your flow or a bar file to new execution group instaed of default. If you do not get any errors that is success.. |
|
Back to top |
|
 |
solomita |
Posted: Wed Aug 04, 2004 8:21 am Post subject: |
|
|
Voyager
Joined: 06 May 2003 Posts: 94
|
I get the same error message during backup/recovery if I only restore my ConfigMgr dbase. In V2.1, this was not the case and as part of backup/recovery, you could simply backup/restore the ConfigMgr dbase and redeploy. Is the only way to restore in V5 to also backup all the broker dbases/tables? _________________ IBM Certified Specialist - WebSphere MQ Integrator
IBM Certified System Administrator - WebSphere MQ V5.3
IBM Certified System Administrator - WebSphere Business Integration Message Broker V5 |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|