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: IsCmdbld.exe or 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
Aug 19, 2008
07:43 PM
IsCmdbld.exe or IsSABld.exe??
Hello,
When I try to build my MSI Installscript project calling IsCmdbld.exe, using Visual Build as my automation tool, the process fails with a -7159 error: "the product license has expired or has not yet been initialized...". I've searched on this issue, and applied hotfix Q113513, but the error persists.
Acresso support has informed me that I should instead use the SAB exe IsSABld.exe, but as we are soon to upgrade to IS 2009 (from 2008), this means that we will be forced to upgrade to Premier, with the added costs that that would entail. :mad:
Based on what I've read, it seems that I should be able to use IsCmdbld.exe to automate the builds. Can someone please provide some clarification? My command line, incidentally, is -p -r -c COMP -a.
Thanks for any insight!
When I try to build my MSI Installscript project calling IsCmdbld.exe, using Visual Build as my automation tool, the process fails with a -7159 error: "the product license has expired or has not yet been initialized...". I've searched on this issue, and applied hotfix Q113513, but the error persists.
Acresso support has informed me that I should instead use the SAB exe IsSABld.exe, but as we are soon to upgrade to IS 2009 (from 2008), this means that we will be forced to upgrade to Premier, with the added costs that that would entail. :mad:
Based on what I've read, it seems that I should be able to use IsCmdbld.exe to automate the builds. Can someone please provide some clarification? My command line, incidentally, is
Thanks for any insight!
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Dec 28, 2009
01:03 PM
For the most part, the EULA for Premiere vs Pro is different when it comes to the standalone build. Premiere allows you to use up to 10 copies of the standalone build where as Pro does not. This is a licensing issue and it is something that you should think about when you next upgrade.
Personally, I think it is wrong but EULAs are EULAs.
Personally, I think it is wrong but EULAs are EULAs.