GEN1053: Code signing process failed.

[KCL]

I believe my certificate is expired, so I can't compile my project--I get this error. This error doesn't really tell me anything useful. I can turn on code signing at the project level and everything works fine. I know my cert is expired, but not everybody does. How can I be sure its not expired before trying to compile, can SB10 provide this information instead of a generic fail message?

Thanks!
Kevin

[linder]

Hi Kevin,

unfortunately, that is no possible. The Microsoft Authenticode tool handles the code-signing process and it only returns SUCCEEDED or FAILED. It does not provide any specific error code.

Code-signing fails (and nothing in your SB configuration changed)...

... if the certificate expired
... if the timestamp servers are not accessible (servers down or blocked by a protection system)
... if the file to be code-signed is detected as malicious (e.g. false-positive) and the protection server blocks the signing process
... if "something" locks the file to be signed
... if a Windows update unregistered the Capicom components
... if "something" blocks the Microsoft Signtool application (in most cases caused by a buggy virus-definition update).

BTW, and up to 45 days before your certificate is due to expire, the SB compiler gives you a warning:

http://www.lindersoft.com/forums/showthread.php?34647-Reminder-Check-your-Code-Signing-Certificate-Expiry-Date!-(February-01-2012)&p=62190#post62190

Introduced in SetupBuilder 7.7 Build 3648 (April 04, 2012):

IMPROVEMENT: [SB#202031] IDE: The compiler displays the code signing expiration date in the compiler window. If the expiration date is < 45 days, it gives a compiler warning. The warning is skipped in command line compilation mode.

This check can only be done if the certificate is still "valid".

Friedrich

[KCL]

Great reference! Thanks once again Friedrich! :)

[linder]

You are very welcome, Kevin :)

Friedrich