ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Receiving Error BIP2213E, BIP4041E

Post new topic  Reply to topic
 Receiving Error BIP2213E, BIP4041E « View previous topic :: View next topic » 
Author Message
nu1
PostPosted: Fri Nov 12, 2004 1:41 pm    Post subject: Receiving Error BIP2213E, BIP4041E Reply with quote

Apprentice

Joined: 28 Nov 2003
Posts: 26

Hi,
I am wokring on WMQI 2.1, DB2 7, CSD 05 .

When I tried to deploy I am receiving the following error
BIP2213E: Invalid configuration message containing folder 'ComIbmMtiParserFactory' which is not valid for target object 'ComIbmResourceManager'.

The message broker received a configuration message containing the folder 'ComIbmMtiParserFactory' which is not valid for the target object 'ComIbmResourceManager'. This can be caused by a mismatch in levels between the Control Center, the Configuration Manager and the Broker, or as a result of a user or third party written plug-in node where the implementation library installed at the broker does not match the node definition held at the Configuration manager and Control Center.

Ensure that the levels of code installed at the Control Center, 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.


BIP4041E: Execution group 'default' 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



Can anybody help me in resolving this?
_________________
-nu1
Back to top
View user's profile Send private message
dilse
PostPosted: Fri Nov 12, 2004 2:13 pm    Post subject: Reply with quote

Master

Joined: 24 Jun 2004
Posts: 270

Are your Config and broker are on different levels?
what about the error information in event viwer application log?

These could be helpful in analyzing the situation.
_________________
DilSe..

Take life as it comes..
Back to top
View user's profile Send private message
JT
PostPosted: Fri Nov 12, 2004 7:49 pm    Post subject: Reply with quote

Padawan

Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.

From an IBM thread regarding BIP4001E & BIP2213E errors:
Quote:
Solution
It is possible that your message set is incomplete.
You can check this by attempting to freeze the message set (remember to lock it first) - it should fail with 'BIP1838' if it is not complete.

If this is the case, there are a couple of ways in which your Message Set may be incomplete.

Have you used the C or COBOL importer to create the message set?
If so, are any of the names of your elements reserved words in COBOL ?
If yes then the COBOL language name property of these elements will not have been populated during the import.
This is a mandatory field. You can check out the offending element(s), manually input this field, then check it back in. You should now be able to export the message set.

Secondly, do any of your messages contain an element which is defined of a compound type which, in turn, contains no elements? (that is, do you have an empty type nested in any messages?)
This currently renders your MessageSet incomplete. The best work-around is to add a 'dummy' element to the offending type.

NOTE - A Message defined of an immediately empty type is not incomplete. That is, you can have a completely empty message.

Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Receiving Error BIP2213E, BIP4041E
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.