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: LE2013 to LE2015 signing fail!, How to configure LE to find signtool
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
‎Sep 08, 2015
05:43 PM
LE2013 to LE2015 signing fail!, How to configure LE to find signtool
I upgrade my project from LE20013 to LE2015 without any reported errors. However the updated project fails with the following error:
TypeLib table successfully built
UIText table successfully built
Upgrade table successfully built
Verb table successfully built
_Validation table successfully built
ISEXP : fatal error -4340: Internal build error
I believe this failing at the signing of the installer, since I do see an unsigned .msi file in the DiskImages/Disk1 directory.
I read the release notes and help file that both mention about the signtool.exe being removed, but at least to me it implied the LE2015 would just use the msft signtool instead from the local machine. What is missing is from the documentation is how to configure LE such that it can point to the signtool.exe on my local machine..
TypeLib table successfully built
UIText table successfully built
Upgrade table successfully built
Verb table successfully built
_Validation table successfully built
ISEXP : fatal error -4340: Internal build error
I believe this failing at the signing of the installer, since I do see an unsigned .msi file in the DiskImages/Disk1 directory.
I read the release notes and help file that both mention about the signtool.exe being removed, but at least to me it implied the LE2015 would just use the msft signtool instead from the local machine. What is missing is from the documentation is how to configure LE such that it can point to the signtool.exe on my local machine..
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 09, 2015
09:24 AM
Hi,
2015 should be using SignerSignEx function rather than Signtools.
However, signing does not occur until the dialogs are built. The next item in the build should be:
Searching project for extract-at-build components...
Do you have any COM extract options enabled?
2015 should be using SignerSignEx function rather than Signtools.
However, signing does not occur until the dialogs are built. The next item in the build should be:
Searching project for extract-at-build components...
Do you have any COM extract options enabled?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 23, 2015
12:33 PM
kyi wrote:
Do you have any COM extract options enabled?
I am not sure where this option is located to check the value of it.
If there is COM, its in signed .net components that are installed into the GAC.
My installer is pretty much the minimal stock installshield LE 2013 project template.
Installing Application in directory
Installing signed .net components in GAC
Signing .msi file
Signing setup.exe file.
There is a power shell script to add some relative paths and version information for TFS, but that is working since its finding all the artifacts.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 30, 2015
02:26 PM
If you right click and selecr Properties, there should be a COM & .NET Settings tab.
The Registration Type option will have Extract COM Information selected.
The Registration Type option will have Extract COM Information selected.
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)