MQSeries.net :: View topic - BIP1536S: ConfigMgr unable to register for internal subscrip

slaney · Posted: Tue Aug 24, 2004 9:41 am Post subject:

Greetings MQ'ers,

I have a small problem that is annoying. Please help out.

Environment:
Broker running on Solaris with a service user id of wbim6160
ConfigMgr service ID is a domain user on AD DOMAIN\wbim6162
Broker is WBIMBv5 CSD03 and the config mgr is WBIMBv5 CSD03

I have just created the broker domain and done a complete deploy.

Error
Each time I do I deply I get in the config mgr event log:

BIP1536S: Configuration Manager unable to register for internal subscriptions with broker UKBRKR1U_B.

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

In the Windows event log I get a few messages which are here in order:
---------------------------------------------------------------------------------
( ConfigMgr ) Broker UKBRKR1U_B 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.

---------------------------------------------------------------------------------
( 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 ) 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.
---------------------------------------------------------------------------------
'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'UKCFMR1U' 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 WebSphere Business Integration settings for this queue, or using an alternative userid which is authorized.
---------------------------------------------------------------------------------

Reading through some previous post I notice this could be to do with the Broker using the context information when replying. i.e. in our case it is replying using the wbim6162 id as the user context for the mqput on the broker queue manager. Since this is not a solaris user I guess that this gets an RC2035. However I would have expected to see this in the AMQERR01.LOG for the broker queue manager and I don't. Additionally I do not want to add the wbim6162 user to the solaris box. Any ideas on how I might fix this problem???

Many Thanks in Advance,

Regards
Steve