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 » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » FmcAssertionException ?

Post new topic  Reply to topic
 FmcAssertionException ? « View previous topic :: View next topic » 
Author Message
praveenchhangani
PostPosted: Wed May 28, 2003 9:51 pm    Post subject: FmcAssertionException ? Reply with quote

Disciple

Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL

Hi all,

I seem to be getting an error during the creation of my buildtime database using the configuration utility. The following is the error I am getting:

Code:
FMC33999E Internal error: 'FmcAssertionException, Condition=*** Pre-condition failed in e:\v340\src\fmczcfil.cxx(129): !strValue.IsNull()':


Installs specs are: wf 3.4, mq 5.3 csd 1, db2 8.1 ee. The Os is a winxp professional machine and all installs were carried out successfully, but I got stuck on the above error during the configuration portion of it.

Anyone know what's going on here??? Any input is appreciated.
_________________
Praveen K. Chhangani,

IBM Certified Solutions Designer -
MQ Workflow 3.4.
Back to top
View user's profile Send private message Send e-mail
Andy
PostPosted: Wed May 28, 2003 11:07 pm    Post subject: Reply with quote

Centurion

Joined: 14 May 2003
Posts: 122

Have you applied ServicePack 1? Not sure but you can give a shot:o
_________________
Andy
Back to top
View user's profile Send private message
Prahasith
PostPosted: Thu May 29, 2003 8:42 am    Post subject: Reply with quote

Disciple

Joined: 16 May 2003
Posts: 184
Location: Kansas City

I guess its SP4
Back to top
View user's profile Send private message Send e-mail
Ratan
PostPosted: Thu May 29, 2003 8:43 am    Post subject: Reply with quote

Grand Master

Joined: 18 Jul 2002
Posts: 1245

Prahasith, I guess you are confused between wf332 and wf 34. For wf3.4 only sp1 is released, as far as I know.
_________________
-Ratan
Back to top
View user's profile Send private message Send e-mail
Prahasith
PostPosted: Thu May 29, 2003 8:47 am    Post subject: Reply with quote

Disciple

Joined: 16 May 2003
Posts: 184
Location: Kansas City

yup i am wrong
i answered for wf3.3.2
Back to top
View user's profile Send private message Send e-mail
praveenchhangani
PostPosted: Thu May 29, 2003 12:23 pm    Post subject: Reply with quote

Disciple

Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL

I think you folks might be right about applying the service pack 1. I am more curious as to why this problem may be occuring. The reason for this concern is because when I had no problems with wf 3.4 and mq 5.2, so could this be an MQ issue perhaps? I personally don't think it is, but at the same time based on my workflow logs that contain hardly anything and the fact that all I see for an error is an fmcassertionexception, I am contemplating on a few things.

Anyone know where I may be able to find more information on workflow exception such as the fmcassertionexception?
_________________
Praveen K. Chhangani,

IBM Certified Solutions Designer -
MQ Workflow 3.4.
Back to top
View user's profile Send private message Send e-mail
Ratan
PostPosted: Thu May 29, 2003 12:32 pm    Post subject: Reply with quote

Grand Master

Joined: 18 Jul 2002
Posts: 1245

Are you getting this error when you are creating a new buildtime database? check with your DB2 utilities if the buildtime database name already exists. I believe if you try to delete a buildtime database with WF configuration utility it doesnot delete it completely.

I get some error (I dont remember which), when I create a new buildtime database with an old name which was deleted with the configuration utility.
_________________
-Ratan
Back to top
View user's profile Send private message Send e-mail
praveenchhangani
PostPosted: Thu May 29, 2003 12:37 pm    Post subject: Reply with quote

Disciple

Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL

Ratan,

You are right on the money here! I did indeed attemp to delete the existing databases from the configuration utility and it gave me an error of some sort. After this I decided to delete from DB2's client configuration assistant and this time it worked. (i.e. deletion of older databases). However now everytime I want to create a new BTDB, it spits out this error.

I guess at this point, since I know that others too have experienced something similar, I might have to uninstall and re-install the whole darn thing! Oh well, fun fun fun..... Thanks again Ratan.
_________________
Praveen K. Chhangani,

IBM Certified Solutions Designer -
MQ Workflow 3.4.
Back to top
View user's profile Send private message Send e-mail
Ratan
PostPosted: Thu May 29, 2003 12:40 pm    Post subject: Reply with quote

Grand Master

Joined: 18 Jul 2002
Posts: 1245

Praveen,

Are you trying to create a new Buildtime database with a different name?

Also enable tracing and try to reinstall. May be you can get more info out of it.
_________________
-Ratan
Back to top
View user's profile Send private message Send e-mail
praveenchhangani
PostPosted: Fri May 30, 2003 5:30 am    Post subject: Reply with quote

Disciple

Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL

No, Actually I was trying with the same database names that I had before which although I deleted from the client configuration assistant, didn't seem to do much, because it kept thinking that the database still existed.

When I try with different database names, it works just fine, but when using the existing database names, workflow complains. After a re-install of db2 8.1 ee, this issue was resolved.

Thanks very much
_________________
Praveen K. Chhangani,

IBM Certified Solutions Designer -
MQ Workflow 3.4.
Back to top
View user's profile Send private message Send e-mail
jmac
PostPosted: Wed Jun 04, 2003 9:15 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC

praveenchhangani wrote:
No, Actually I was trying with the same database names that I had before which although I deleted from the client configuration assistant, didn't seem to do much, because it kept thinking that the database still existed.

When I try with different database names, it works just fine, but when using the existing database names, workflow complains. After a re-install of db2 8.1 ee, this issue was resolved.

Thanks very much


I think this has to do with the fact that there are really "two" levels of delete. If you understand mainframe terminology, its like Delete, vs Delete and Uncatalog. In DB2 at least on the Windows platform we have the same issue, there are 2 comands:
    Remove
    Drop

I never remember which one is which, so I end up having to look at the doc each time, so you might want to check this out, but if I am remembering correctly Remove takes the DB out of the catalog, and Drop physically deletes the DB.
_________________
John McDonald
RETIRED
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
vennela
PostPosted: Wed Jun 04, 2003 9:36 am    Post subject: Reply with quote

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India

Quote:
I never remember which one is which, so I end up having to look at the doc each time, so you might want to check this out, but if I am remembering correctly Remove takes the DB out of the catalog, and Drop physically deletes the DB.

I think it's the other way around.
Drop is the one which is delete and remove the registry keys.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
jmac
PostPosted: Wed Jun 04, 2003 9:41 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC

Thanks Venny.... Thats why I always look at the doc. I'm just getting too old.
_________________
John McDonald
RETIRED
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » FmcAssertionException ?
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.