Author |
Message
|
ACE |
Posted: Wed Jan 04, 2006 4:37 am Post subject: MB6.0: BIP2210E: Invalid configuration message.. |
|
|
 Novice
Joined: 24 Oct 2005 Posts: 10
|
Hi,
I have migrated from mb5.0 to mb 6.0, I get the following error but I don't exactly know how to fix it.
Any ideas anyone?
Thanks!
BIP2210E: Invalid configuration message: attribute name 'serializationToken' not valid for target object 'SUBInput.MQInput'.
The message broker received a configuration message containing the attribute name 'serializationToken' which is not valid for the target object 'SUBInput.MQInput'. This can be caused by a mismatch in levels between the Message Brokers Toolkit, the Configuration Manager and the Broker, or as a result of a user or third party written user-defined node where the implementation library installed at the broker does not match the node definition held at the Configuration manager and Message Brokers Toolkit.
Ensure that the levels of code installed at the Message Brokers Toolkit, Configuration Manager and Broker are all consistent. If they are, identify the supplier of the target object and report the problem to them. If this is IBM, contact your IBM support center. |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Jan 04, 2006 4:45 am Post subject: Re: MB6.0: BIP2210E: Invalid configuration message.. |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
ACE wrote: |
Ensure that the levels of code installed at the Message Brokers Toolkit, Configuration Manager and Broker are all consistent. If they are, identify the supplier of the target object and report the problem to them. If this is IBM, contact your IBM support center. |
_________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
ACE |
Posted: Wed Jan 04, 2006 4:59 am Post subject: Re: MB6.0: BIP2210E: Invalid configuration message.. |
|
|
 Novice
Joined: 24 Oct 2005 Posts: 10
|
That's what I am not sure how to verify. |
|
Back to top |
|
 |
mqmatt |
Posted: Wed Jan 04, 2006 6:58 am Post subject: |
|
|
 Grand Master
Joined: 04 Aug 2004 Posts: 1213 Location: Hursley, UK
|
If you're deploying from the v6 tools to a v5 broker, ensure that the broker has a recent fixpack (e.g. 05) applied. |
|
Back to top |
|
 |
ACE |
Posted: Wed Jan 04, 2006 7:48 am Post subject: |
|
|
 Novice
Joined: 24 Oct 2005 Posts: 10
|
How do I determine the levels of code installed at the Message Brokers Toolkit, Configuration Manager and Broker? |
|
Back to top |
|
 |
mqmatt |
Posted: Wed Jan 04, 2006 9:16 am Post subject: |
|
|
 Grand Master
Joined: 04 Aug 2004 Posts: 1213 Location: Hursley, UK
|
|
Back to top |
|
 |
ACE |
Posted: Wed Jan 04, 2006 12:36 pm Post subject: |
|
|
 Novice
Joined: 24 Oct 2005 Posts: 10
|
|
Back to top |
|
 |
|