|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Undetermined ESQL Level Error adding to Broker Archive File |
« View previous topic :: View next topic » |
Author |
Message
|
jensinaus |
Posted: Tue May 04, 2004 7:14 pm Post subject: Undetermined ESQL Level Error adding to Broker Archive File |
|
|
Newbie
Joined: 04 May 2004 Posts: 5
|
I'm currently in the midst of migrating WMQI 2.1 CSD2 message flows to WBIMBv5 FixPak3. When generating a broker archive file, I get the following error message
Adding to Broker Archive File
Processing file blablab.msgflow
Failed to add blablab.msgflow to archive file
The ESQL level for blablab.msgflow is undetermined
Narrowed it down to an embedded subflow which has an output node's destination list promoted. The promoted destination list displays a drop down list box with the following options: fixed, reply, and list. When compiled with reply the broker archive file gets generated. However, when compiled with fixed, I get the above error.
Has anyone encountered this error before or has an insight into what is going wrong? |
|
Back to top |
|
 |
MSAT |
Posted: Wed Dec 21, 2005 1:58 am Post subject: Bar file addition problem |
|
|
Acolyte
Joined: 17 Aug 2005 Posts: 62 Location: Bengalooru
|
Hi,
I also get the similar error message when tried to add message flow to the BAR file. ( The main flow is having subflow flows and these subflows are in different message flow project). The message in the Detail section looks like
"Failed to add file ABCD.msgflow to archive file
The reference to ESQL Module XNXNX_Compute with function 'Main' cannot be resolved. Ensure the ESQL module exists in the correct schema, and that it contains function 'Main' and try again."
After building all the projects in the Workspace (Project --> Rebuild All)
the flow added to the BAR file successfully.
I guess the problem may be due to some internal references... which got refreshed after building all the projects.
Bye |
|
Back to top |
|
 |
elvis_gn |
Posted: Wed Dec 21, 2005 2:45 am Post subject: |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
Hi,
I have faced this issue.
My first assumption was that the ESQL i was referencing was wrong.
But I understand that when u import a subflow of a Main flow and redelpoy the whole thing, this problem occurs. Try Rebuilding the project entirely.
Regards |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|