MQSeries.net :: View topic

Lisa · Posted: Fri Jul 19, 2002 6:01 am Post subject:

All,
I'm trying to delpoy a message flow from our SIT environment to our HP Unix production server.

The Configmgr was created with service id - mqsisit.
The Broker on the HP-Unix service id is mqsiprd2

Question:
Should service id mqsisit be defined on the HP Unix server or should the Configmgr's service id match the brokers service id?

Please note that I have no problems with deploying message flows to our SIT broker. The SIT broker's service id is mqsisit, the same as the Configmgrs.

I'm getting the following errors:

( ConfigMgr ) User id 'mqsisit' not authorized to put to queue 'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'PIINTS01' using accounting token '0000000000000000000000000000000000000000000000000000000000000000'.

The user is not authorized to put a message on the named queue.

Ensure the user is allowed to perform this operation. This may involve configuring the MQSeries settings for this queue, or using an alternative userid which is authorized.

( ConfigMgr ) Error detected whilst processing a message in node 'DynamicSubscriptionEngine'.

The message broker detected an error whilst processing a message in node 'DynamicSubscriptionEngine'. An exception has been thrown to cut short the processing of the message.

See the following messages for details of the error.

( ConfigMgr ) Invalid configuration message. See the following messages for details of the error.

The publish/subscribe function of the broker has received an invalid configuration message and has not updated its configuration. This can arise as a result of errors in the specification of the broker topology or topics which the Configuration Manager was unable to detect. It can also result from the broker having become out of step with the configuration repository or from other applications sending extraneous messages to the configuration queues of the broker (SYSTEM.BROKER.ADMIN.QUEUE and SYSTEM.BROKER.EXECUTIONGROUP.QUEUE).

Check the relevant topology and topic definitions, perform a complete redeploy of the configuration and ensure that no applications are writing to the configuration queues.

( ConfigMgr ) Broker PIIHPS03_BKR could only process parts of the internal configuration message.

Parts of the internal configuration message were not processed successfully.

This response indicates that one or more Execution Groups could not process the internal configuration message. Analyze all of the following messages to determine why the internal configuration message could not be processed.

( ConfigMgr ) Configuration Manager unable to register for internal subscriptions with broker PIIHPS03_BKR.

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

Thanks, Lisa