SignTool fails

[zappbrannigan]

I get an error building using latest Advanced installer version 16.7.

DefaultBuild ]
Building package:
C:\Users\choward\Documents\Advanced Installer\Projects\test\Setup Files\Pages Workstation 8.0.msi
Prepare build
Detecting MSI incompatible resources
Preparing files
The digital signing of the ProgramFiles64Folder\SSNC Technologies\PagesWorkstation\bin\PagesBatchProcessor.exe file failed. Error message: 'Done Adding Additional Store
Error information: "Error: SignerSign() failed." (-1073741823/0xc0000001)
SignTool Error: An unexpected internal error has occurred.'
Error details

Build finished because an error was encountered.


Yet when I run a CMD window I can sign the .exe manually ok using the same signtool.exe.
App is 64bit
Seems like AI is using 64bit signtool (can't see how to verify though).


Thanks!
Zapp

[Catalin]

Hello Zapp and welcome to Advanced Installer forums,

I have tested this scenario, but I was unable to reproduce the described behavior.

Upon further investigation, I could indeed notice that we deliver two signtool.exe executables.

Their location is:

Code: Select all

WinDir:\Program Files (x86)\Caphyon\Advanced Installer 16.7\third-party\winsdk\x64

respectively

Code: Select all

WinDir:\Program Files (x86)\Caphyon\Advanced Installer 16.7\third-party\winsdk\x86

With that being said, could you please try to manually sign your setup (from a command line shell) using the signtool.exe located in the x64 folder and let me know if the issue reproduces?

Looking forward to hearing from you.

Best regards,
Catalin

[zappbrannigan]

The 32bit signtool fails in cmd
The 64bit works in manual cmd.

How do I force Advanced Installer to user the 64bit signtool? Or is it by default?

[Catalin]

Hello,

Since you have mentioned your application is an x64 application, you can maybe try to set your package as an x64 package as well (since your target audience most probably is people running 64-bit machines). To do so, please go to "Install Parameters" page and change the "Package Type" to "64-bit package for x64 processors (AMD64, EM64T)"

Hope this helps.

Best regards,
Catalin

[zappbrannigan]

It turned out to be 2 issues:

1. My work blocks the timestamp gather url that AI defaults to causing an error (could be better message).
I found another timestamp URL that wasn't blocked and it started working.
2. Through a VPN my IP address looks different, this caused the personal digital Cert to not work properly on runtime validation to get the cert, when I'm onsite and not using a VPN I got digital sign to work!

Hope this helps others.
Cheers!

[Catalin]

Hello Zapp,

Thank you for your followup on this and for sharing your solution with us.

I am sure this will be of help for further users facing a similar scenario!

Best regards,
Catalin