| Author |
Message
|
| smyers |
 Posted: Mon Jan 12, 2004 1:22 pm Post subject: Internal Exception Arised: FmcAssertionException |
 |
|
Novice
Joined: 18 Jul 2002
Posts: 17
|
Hello Everyone,
I have done an export from MQWorkflow v3.3 and want to import into MQWorkflow v3.4. Everything seems to be ok, except for the data structures. Whenever I try to import my v3.3 data structures (and choosing overwrite) into v3.4, I keep getting the error:
Internal Exception Arised: FmcAssertionException=***Assertion failed in e:\v340\src\fmcfmodl.txx(1896):member.IsValid(). The number for this error message is FMC22010E.
It also mentions a data structure name from my import file (i.e. a datastructure named "X"), and says that Entity "X" of type DataStructure exists already (tried to create).. The number for this error message is FMC21029E.
I am running Win2k, have installed MQWorkflow SP4, and I can only find one other unresolved reference to this same error in these forums. Does anyone know how to resolve this problem?
Thanks! |
|
| Back to top |
|
 |
| vennela |
| Posted: Mon Jan 12, 2004 1:37 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Instead of exporting the FDL from buildtime and reimporting it into the new version, you will be better of to do a migration from 332 to 34. |
|
| Back to top |
|
|
| smyers |
| Posted: Mon Jan 12, 2004 2:30 pm Post subject: |
|
|
Novice
Joined: 18 Jul 2002
Posts: 17
|
| Would a migration still be an option for my scenario, where I have a new machine and have only ever had workflow v3.4 on it? Basically I had workflow v3.3 on another machine, exported and copied the fdl over to my new machine, and would like to install it as is. |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Jan 12, 2004 3:07 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
If I were you, I would upgrade the OLD machine and then export the FDL. Import this FDL inot the new machine. Maybe somebody else can suggest a better way.
But from my experience migration doesn't take that long. |
|
| Back to top |
|
|
| smyers |
| Posted: Tue Jan 13, 2004 12:37 pm Post subject: |
|
|
Novice
Joined: 18 Jul 2002
Posts: 17
|
| hmmm...I wish that were an option, but unfortunately the old machine is gone and all I have left is the .fdl that I exported from wfv3.3. I have been trying to do some more research into this problem, and I have even separated out just the data structures and trying to import those in an attempt to narrow down the problem. I keep getting the same error. I am also contending with the fact that the old .fdl was used with a DB2 db, while the db I am using in v3.4 is simply an MSAccess .mdb. Are there tags within .fdl files which denote what kind of db you are using, etc.? Would this make any difference? |
|
| Back to top |
|
|
| jmac |
| Posted: Tue Jan 13, 2004 2:28 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
If I understand you correctly, you are saying that you have FDL that you exported from a V3.3 system and can not import into a V3.4 system. This is indeed strange, I do this all the time. I do not think the fact that you have an MS Access buildtime database is the problem. Can you posibly narrow this down to the Data Structure that is causing the problem, and post that FDL so we can have a look? Also, have you tried creating a new MS Access BTDB and import into that.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| smyers |
| Posted: Tue Jan 13, 2004 2:48 pm Post subject: |
|
|
Novice
Joined: 18 Jul 2002
Posts: 17
|
Hi John,
Yes, that is exactly what has happened. I have a V3.3 .fdl that I exported onto a new machine, and this new machione has V3.4 on it (and has had no other configs on it whatsoever). I get that error whenever I try to import my .fdl data structures.
Is the best way to get rid of that existing .mdb to just delete it, or do I have to make an entirely new configuration by deleting my default FMC config and creating a new one? I just don't want to make things worse than they already happen to be. Is there any app out there which can test the .fdl, is there anything in regards to user input (i.e. spaces) which can cause import errors from .fdls, etc. I realize this is very general but any help would be appreciated. Thanks |
|
| Back to top |
|
|
| jmac |
| Posted: Tue Jan 13, 2004 3:23 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Based on what you are saying, I assume that this BTDB is part of your Default configuration. Before you blow that configuration away, do a simple test.... Allocate a new BT ONLY configuration using MS Access, see if you can import into this new BT. If you can, then you might want to blow away the whole thing and create a new default configuration. I have never tried to just delete the BTDB out of an exiting congifuration, and am not sure it is possible.
GOOD LUCK
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| smyers |
| Posted: Tue Jan 13, 2004 3:39 pm Post subject: |
|
|
Novice
Joined: 18 Jul 2002
Posts: 17
|
Ok, so I created a new BT with a new .mdb, and tried the import. This time, it got a little farther down in the structure file but still the same error.
When I look in BT data structure table in the .mdb I only see the default data structure. The error always seems to occur at the same line in the fdl, and when I try to remove the offending structure the fdl just picks up the next one at the same line.
It is relatively consistent, but every now and then it gets farther down the .fdl file. Very strange. I do not think there is any other recourse but to try a reinstall or try and blow away the existing .mdbs. I will let you know what I find out here.
Thanks |
|
| Back to top |
|
|
| smyers |
| Posted: Thu Jan 15, 2004 10:41 am Post subject: |
|
|
Novice
Joined: 18 Jul 2002
Posts: 17
|
| OK, so I deleted everything - did a full reinstall of mqworkflow, etc. and I am still getting the same error message. The error seems to be originating from a specific .dll here: C:\Program Files\IBM WebSphere MQ Workflow\BIN\fmcfffdn.dll. I am using IBM MQSeries Client, Version 5.2. Is there anything else I can do? I really do not feel like manually recreating all my data structures within v3.4! |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Jan 15, 2004 12:38 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
e-mail me the FDL file (if that is not a problem)
Let me know the versions of MQWF buildtime (old and new) and DB2 versions (old and new) and what DB's you were using for each (whether DB2 or MS Access). I will try to port it. |
|
| Back to top |
|
|
| jmac |
| Posted: Fri Jan 16, 2004 6:34 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Venny:
Assuming you get the FDL, If you can narrow this down to one Data Structure maybe you could post just that piece to the Forum so we all can have a look.
Thanks
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| smyers |
| Posted: Fri Jan 16, 2004 9:42 am Post subject: |
|
|
Novice
Joined: 18 Jul 2002
Posts: 17
|
| I will have to check and see what the policy is in regards to releasing the .fdl file. |
|
| Back to top |
|
|
| jmac |
| Posted: Fri Jan 16, 2004 9:52 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
To diagnose your problem, we probably do not need the process models. We would need all of the data structures, but I don't see how that could be giving away any secrets. I am not certain that Venny would agree with this, but I think we could start with just the data structures.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Jan 16, 2004 10:10 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| I am not certain that Venny would agree with this |
I never dared to disagree with you 
| Quote: |
| but I think we could start with just the data structures. |
That is what I asked for too. |
|
| Back to top |
|
|
|
|
