| Author |
Message
|
| Gemz |
 Posted: Wed Jan 23, 2008 5:00 am Post subject: Error while deploying the Bar file. |
 |
|
Centurion
Joined: 14 Jan 2008
Posts: 124
|
While deploy the bar file i am getting the following Error in Event Viewer.
BIP1536S: The Configuration Manager was unable to register for internal subscriptions with broker WBRK61_DEFAULT_BROKER.
Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker WBRK61_DEFAULT_BROKER 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 WBRK61_DEFAULT_BROKER.
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.
Thanks |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Wed Jan 23, 2008 5:03 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
| Quote: |
| 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. |
could you please be so kind and post all your system log here so that we all can have a look at it for you? 
_________________
Regards, Butcher |
|
| Back to top |
|
|
| Gemz |
| Posted: Wed Jan 23, 2008 5:55 am Post subject: |
|
|
Centurion
Joined: 14 Jan 2008
Posts: 124
|
Hi,
While deploying I am getting the following error in the System log. But My deployment is successful and message flows are running fine.
----------------------------------------
( WBRK61_DEFAULT_CONFIGURATION_MANAGER ) Source field ''69006e0074006500720066006100630065007500730065007200'' is too long for a target field of length ''12'' when converting from unicode to codepage ''5348''.
When the character data in the source field is converted to the target codepage, the resulting character string was longer than the defined length of the target field.
Correct the application or compute expression that generated the message. Ensure that the definition of the field in the output message is correctly specified bearing in mind the codepage required for the message and check that the origin of the data within the source field is providing correct data.
---------------------------------------
( WBRK61_DEFAULT_CONFIGURATION_MANAGER ) 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.
---------------------------------------
( WBRK61_DEFAULT_CONFIGURATION_MANAGER ) Broker 'WBRK61_DEFAULT_BROKER' 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.
-----------------------------------------
In this What value is sending by the configuration manager....?
Thanks
Gemz |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 23, 2008 6:10 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Have none of the other threads concerning that error message been of value then?
No point us suggesting solutions which have already failed to help.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Gemz |
| Posted: Wed Jan 23, 2008 9:04 am Post subject: |
|
|
Centurion
Joined: 14 Jan 2008
Posts: 124
|
Hi,
I was using the user_name with 13 character length. MB accepts only 12 characters. so that i got this error.
Now i have changed and its working fine.
Thanks for your help....
Gemz  |
|
| Back to top |
|
|
|
|
