This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: MAJOR ISSUE! Fatal error with IsSaBld; can't replicate in IDE
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 27, 2010
09:56 AM
MAJOR ISSUE! Fatal error with IsSaBld; can't replicate in IDE
when i try to build my merge module project with the following command line
%IS_BLD% -p "%WORKING_DIR%\Install\Product\ModuleForProduct.ism" -r ModuleForProduct" -c COMP -a "Release" -b "%WORKING_DIR%\Install\Product"
i get the following result:
ISDEV : fatal error -5005: Internal build error
ISDEV : fatal error -6199: Internal build error
can't release something if it doesn't build on the build machine. this is not good. please help!
%IS_BLD% -p "%WORKING_DIR%\Install\Product\ModuleForProduct.ism" -r ModuleForProduct" -c COMP -a "Release" -b "%WORKING_DIR%\Install\Product"
i get the following result:
ISDEV : fatal error -5005: Internal build error
ISDEV : fatal error -6199: Internal build error
can't release something if it doesn't build on the build machine. this is not good. please help!
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 27, 2010
11:26 AM
Try re-running this with an additional parameter: -v. This will create a verbose build log, and may help to isolate what leads up to those errors.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 27, 2010
12:09 PM
This is all i get:
there is no problem trying to build from the IDE, and the merge module validation suite doesn't report any errors. I just repaired my standalone build also.
Build started at Oct 27 2010 12:54 PM
Building Release: ProductModule -c COMP -a Release -b D:\Builds\BuildNum\Product\Install\Product -v
ISDEV : fatal error -5005: Internal build error
ISDEV : fatal error -6199: Internal build error
Build finished at Oct 27 2010 12:54 PM
there is no problem trying to build from the IDE, and the merge module validation suite doesn't report any errors. I just repaired my standalone build also.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 27, 2010
12:16 PM
also, should point out that this doesn't give me any confidence whatsoever...especially considering that a general search for this error code finds people with unanswered questions about it dating back before IS12...
http://kb.flexerasoftware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q109832&sliceId=1&docTypeID=DT_ERRDOC_1_1&dialogID=97761247&stateId=0%200%2097755914
IS people haven't even documented the error after at least 4-5 YEARS of people having the problem...
http://kb.flexerasoftware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q109832&sliceId=1&docTypeID=DT_ERRDOC_1_1&dialogID=97761247&stateId=0%200%2097755914
IS people haven't even documented the error after at least 4-5 YEARS of people having the problem...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 27, 2010
05:19 PM
Given the output
Building Release: ProductModule -c COMP -a Release -b D:\Builds\BuildNum\Product\Install\Product -vI think it's not trying to build the correct release name. Furthermore, this release name is probably invalid. Try fixing your quotes on the -r parameter's value - the sample you gave has only a trailing quote.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 27, 2010
05:42 PM
Note to self: if it builds through the IDE and it doesn't build from the commandline, look really carefully at the command line.
For posterity: the configuration name "release" is perfectly valid, but not properly quoting the release name: not valid. 😛 (Funny how staring at something for too long makes you blind to it's flaws.)
I'll still maintain that the parsing of the command line in IsSaBld.exe should definitely be able to pick up on something like that, and if Error 5005 means that there was an error on the command line, it should be documented. Actually, no matter what it means, it should be documented.
For posterity: the configuration name "release" is perfectly valid, but not properly quoting the release name: not valid. 😛 (Funny how staring at something for too long makes you blind to it's flaws.)
I'll still maintain that the parsing of the command line in IsSaBld.exe should definitely be able to pick up on something like that, and if Error 5005 means that there was an error on the command line, it should be documented. Actually, no matter what it means, it should be documented.