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: Error when using IsSABld.exe
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
Jun 23, 2009
10:39 AM
Error when using IsSABld.exe
We seem to consistently get the following error from building our installation packages with IsSABld.exe.
These builds used to work fine until we upgraded to 2009.
The actual section from the log is:
Upgrading table MsiPatchOldAssemblyName
ISDEV : error 5001: Failed to resolve a field value.
MsiPatchOldAssemblyName
Our command line arguments are:
-p "$(CURAWORK)\Modules\Assessor\Installation\InstallShield\Assessor.ism"
-r "Assessor Full Install"
-c "UNCOMP"
-a "FULL"
-h
-b "$(CURAWORK)\Modules\Assessor\Installation\InstallShield\Media"
-o "C:\Program Files\Macrovision\IS 2008 StandaloneBuild\Objects"
-t "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727"
I know the -o argument is still pointing to the installshield 2008 location, but changing it does not make a difference.
The build subsequently fails with this message:
ISDEV : fatal error -6199: Internal build error
These builds used to work fine until we upgraded to 2009.
The actual section from the log is:
Upgrading table MsiPatchOldAssemblyName
ISDEV : error 5001: Failed to resolve a field value.
MsiPatchOldAssemblyName
Our command line arguments are:
-p "$(CURAWORK)\Modules\Assessor\Installation\InstallShield\Assessor.ism"
-r "Assessor Full Install"
-c "UNCOMP"
-a "FULL"
-h
-b "$(CURAWORK)\Modules\Assessor\Installation\InstallShield\Media"
-o "C:\Program Files\Macrovision\IS 2008 StandaloneBuild\Objects"
-t "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727"
I know the -o argument is still pointing to the installshield 2008 location, but changing it does not make a difference.
The build subsequently fails with this message:
ISDEV : fatal error -6199: Internal build error
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 24, 2009
03:04 AM
Ok,
Switching to using
C:\Program Files\InstallShield\2009\System\IsCmdBld.exe
solved it.
Switching to using
C:\Program Files\InstallShield\2009\System\IsCmdBld.exe
solved it.
![](/skins/images/8C9D13A71C7F7695F3262372C0172D68/responsive_peak/images/icon_anonymous_message.png)