Author |
Message
|
Vitor |
Posted: Fri Nov 11, 2005 1:17 am Post subject: Configuration Error? |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Hi,
I've recently got back in MQSI after something of a break, and think I'm missing something straightforward.
I've got a really simple Compute node transforming an XML messge into CWF using MQSI 2.1 on WinXP. The trace shows it going fine until the transformed message is sent to the out terminal, when I get the following message:
Error BIP5304E: Resource Manager: Dictionary not found for message set MS_FMS_004.
As per the message, I've checked that the message set is associated with the broker, the ID matches in the properties and the deploy has no apparent error messages. I've tried deleting and redefining the broker to no avail. XML messages being transformed to XML messages work fine, but these do not have message sets associated with them. From this I infer there's something wrong with my message repository configuration, but what?
What am I missing please?
Many Thanks. |
|
Back to top |
|
 |
elvis_gn |
Posted: Fri Nov 11, 2005 2:07 am Post subject: |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
Hi Vitor,
What is MS_FMS_004 in your message.....is that the Message Definition.........
RM Dictionary ONLY means that your message set is not deployed or the one that is deployed is not the one that the flow is referencing......
Regards. |
|
Back to top |
|
 |
dipankar |
Posted: Fri Nov 11, 2005 2:45 am Post subject: |
|
|
Disciple
Joined: 03 Feb 2005 Posts: 171
|
refresh the operations tab of the control center. Then see the required message set is in the specific broker or not. If not, then your message set has not been deployed. |
|
Back to top |
|
 |
Vitor |
Posted: Fri Nov 11, 2005 3:20 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Hi,
MS_FMS_004 is the name of the message set containing the CWF definition. According to the opperations tab it exists in the broker running the flow, even after a refresh.
Regards |
|
Back to top |
|
 |
elvis_gn |
Posted: Fri Nov 11, 2005 3:36 am Post subject: |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
Is the flow and the Set under the same Execution Group....??
Check the name of the set in the Input Node in your flow....i hope its the same .......
Deploy again and check details after a successful deploy.....verify that no errors or warnings are thrown.
Regards. |
|
Back to top |
|
 |
dipankar |
Posted: Fri Nov 11, 2005 4:17 am Post subject: |
|
|
Disciple
Joined: 03 Feb 2005 Posts: 171
|
what is in the event viewer? can you post the description of the event here? |
|
Back to top |
|
 |
Vitor |
Posted: Fri Nov 11, 2005 5:20 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Both the flow and the message set are under execution group "default" in the same broker. There is nothing in the application event log except the informational messages for MQSI componments starting.
Regards, |
|
Back to top |
|
 |
wschutz |
Posted: Fri Nov 11, 2005 6:48 am Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
Quote: |
MS_FMS_004 is the name of the message set containing the CWF definition |
It is? How did it get that name? My message sets usually have names like: "N5DIOFO002001". _________________ -wayne |
|
Back to top |
|
 |
Vitor |
Posted: Fri Nov 11, 2005 7:03 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Apologies for my lack of clarity. "MS_FMS_004" is the name of the message set, it's identifier is "E6T3F5G076001" |
|
Back to top |
|
 |
wschutz |
Posted: Fri Nov 11, 2005 7:31 am Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
Sorry, don't you need to set Properties.MessageSet to: "E6T3F5G076001" ?
It seems that its being set to: "MS_FMS_004" _________________ -wayne |
|
Back to top |
|
 |
Vitor |
Posted: Sat Nov 12, 2005 11:45 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Clearly you do - that seems to have helped! I knew it would be "pilot error".
Changing it to the identifier yields the following:
2005-11-12 19:19:09.000000 2660 Error BIP5518E: Dictionary load error.
An unknown error occurred while reading in the dictionary.
Please contact your IBM support center.
2005-11-12 19:19:09.000000 2660 Error BIP5286E: Message Translation Interface Writing Errors have occurred.
Errors have occurred during writing.
Review further error messages for an indication to the cause of the errors.
I understand 5286 is most commonly caused by a problem in the MRM so a thorough review of that is the next step.
Many thanks for your assistance in this. |
|
Back to top |
|
 |
kimbert |
Posted: Mon Nov 14, 2005 2:58 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Vitor,
BIP5286 is a top-level catch-all exception for the MRM message writer. BIP5518E is the more interesting error message. Where did the dictionary come from?
( by the way, 'Configuration Error?' is not a very useful subject line. Most questions on this forum would fit that description. 'BIP5304E: Resource Manager: Dictionary not found' would have caught my attention immediately.) |
|
Back to top |
|
 |
Vitor |
Posted: Mon Nov 14, 2005 3:04 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Kimbert,
Apologies for the subject line - I'm new here!
The dictionary is my own creation, defined by hand in a new message set & deployed to the broker running the flow. An initial squint through it has failed to spot an obvious issue. This means I'm either missing the obvious (which was the explaination for the original problem) or the fault is more subtle.
Smart money says obvious.
Regards, |
|
Back to top |
|
 |
kimbert |
Posted: Mon Nov 14, 2005 9:06 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
I'm afraid nothing obvious springs to mind. If you take a user trace of the deploy operation, you should get a slightly more detailed error. |
|
Back to top |
|
 |
schofier |
Posted: Tue Nov 15, 2005 5:08 am Post subject: |
|
|
Novice
Joined: 10 Dec 2003 Posts: 14 Location: IBM Hursley
|
Just for reference, from 2.1 CSD4 onwards, you should be able to refer to either the message set name or the identifier when parsing/writing an MRM message |
|
Back to top |
|
 |
|