| Author |
Message
|
| devasis_sahu |
 Posted: Tue Oct 26, 2004 2:27 am Post subject: XSD Import in WBIMB |
 |
|
Newbie
Joined: 11 Oct 2004
Posts: 3
|
Hi,
We have 3 XSDs , which are referenced. The structure is :
XML1
XML2
XML3
XML1 ---> Parent XSD (XML2 and XML3 are imported)
XML2----> Child XSD to XML1
XML3 ----> Child XSD to XML1 and XML2
Able to make the message set successfully , but the problem comes when the bar file containing the XSDs are deployed. Getting the following error when the bar file is deployed.
1.
BIP5145E:Error setting up runtime dictionary resource using message set identifier 'N7KEL8C002001'.
An error was detected when trying to deploy message set. Use the Message Brokers Toolkit to match the message set Identifier : N7KEL8C002001, to a message set name.
Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
2.
BIP5347E: MtiImbParser2: RM has thrown an unknown exception.
Returned by the RM when an unknown exception is thrown. This is an internal error.
Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center providing system trace files where possible.
Has anybody faced this problem earlier and could anybody guide me to solve this issue.
Regds |
|
| Back to top |
|
 |
| TonyD |
| Posted: Tue Oct 26, 2004 2:46 pm Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
| You refer to the .bar file containing XSDs. The message set should contain three .mxsd files, one for each of the XSDs that you have imported...is this the case? |
|
| Back to top |
|
|
| kspranava |
| Posted: Fri Jul 28, 2006 2:27 am Post subject: |
|
|
Centurion
Joined: 27 Apr 2003
Posts: 124
|
Dear All,
Me too facing same problem; unable to deploy a bar file. I am trying to deploy it in a windows 2000professional and WBIMB 6.0.0.1 broker.
| Code: |
BIP5347E: MtiImbParser2: RM has thrown an unknown exception.
Returned by the RM when an unknown exception is thrown. This is an internal error.
Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center providing system trace files where possible. |
Even after setting EXTSHM, no luck.
Thanks,
kspranava. |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Jul 28, 2006 2:53 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
What is in the BAR file?
Any errors in the Windows application event log?
I thought EXTSHM was an AIX feature? How does that relate to your Windows 2000 broker? |
|
| Back to top |
|
|
| kspranava |
| Posted: Fri Jul 28, 2006 6:13 am Post subject: |
|
|
Centurion
Joined: 27 Apr 2003
Posts: 124
|
Hi Kimbert,
| kimbert wrote: |
| What is in the BAR file? |
BAR file has <messagesetname>.dictionary file
| kimbert wrote: |
| Any errors in the Windows application event log? |
In the Windows Application event log, same errors were reported as in Broker event log.
| kimbert wrote: |
| I thought EXTSHM was an AIX feature? How does that relate to your Windows 2000 broker? |
That is the reason probably it is not working! BTW, I don't know that it is only for AIX, pity myself.
Thanks,
-kspranava. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jul 28, 2006 6:32 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
EXTSHM is only an AIX thing.
There should be more than one entry in the Event Viewer (and the broker log) for each failed deploy.
The other associated messages might show more information that can help.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
