MQSeries.net :: View topic - Unable to deploy MEssage Set in 2.1

grishagrisha · Posted: Thu Dec 14, 2006 12:23 am Post subject:

I am working with MQSI 2.1 (we are planning to migrate to 6.0 in March or April). (Fix Pack 7 I think?) This is with control center on windows2000 and also ocurring with windows 2003, the broker is running on AIX.

Trying to deploy a message set that was generated from a Discovery Agent Batch file. This is an automated process that generates an MRM for an SAP Idoc structure.

I deleted the old message set and ran the batch file, which takes a parameter file and several xsd files and imports a new MRM with the same name as the previous version, but creates a new UUID.
When I try to deploy the new MRM, I get the following errors:
BIP5318E
BIP5145E
BIP4041E
BIP2087E

BIP5318E: Resource Manager: Runtime dictionary ID mismatch.

There has been an attempt to register a resource with a message set id that does not match the message set id specified within the resource. Message set id: 47, wire format descriptor id: rmRegisterResource.

Stop the Broker and delete any pending messages from the system Queues on the broker's queue manager in MQSeries Explorer. Retry the operation and examine system logs for any errors. Check to see if any other errors are being generated. Finally record the full details provided with this message and contact your IBM support center.

BIP5145E: Error setting up runtime dictionary resource using message set identifier 'E8KK71412E001'.

An error was detected when trying to deploy message set. Use the Control Center to match the message set Identifier : E8KK71412E001, to a message set name.

Check that you have a valid broker installation. If the problem persists, contact your IBM support center.

BIP4041E: Execution group 'ace_EG1' received an invalid configuration message. See the following messages for details of the error.

The message broker received an invalid configuration message and has not updated its configuration. This can arise as a result of errors in the specification of either message flows or message sets which the configuration manager was unable to detect. It can also result from a message flow requiring a type of node that is not supported by the broker installation, from the broker having become out of step with the configuration database or from other applications sending extraneous messages to the broker's configuration queues (SYSTEM.BROKER.ADMIN.QUEUE & SYSTEM.BROKER.EXECUTIONGROUP.QUEUE).

Check the relevant message flow and message set definitions, check that all necessary plug-ins are installed, perform a complete redeploy of the broker's configuration and ensure that no applications are writing to the broker's configuration queues.

BIP2087E: Broker ESNDCMS1BRKD01 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.

I do not know how to resolve this issue, any suggestions would be very much appreciated. I did search here for similar issues, but still not sure what to try.
Thanks.
_________________
Grisha