PDA

View Full Version : SB8 and Signcode error



NewsArchive
11-07-2013, 02:39 AM
Just upgraded from 6 to 8 and this message prevents signing. Here is a bit
from the result script.

Processing Uninstall Code-Signing...
Adding Digital Certificate to Uninstall...
SIGNCODE
Compiler warning GEN1061: File not found:
Compiler warning GEN1061: File not found:
Compiler error GEN1053: Code signing process failed. Error Code: -1

Tried the three options forthe Timestamp URL but all the same result
Nothing in Credentials Line
Nothing in PK file
pfx file in the PFX line (worked in v6)
Password in pw line ( worked in v6)

SB8 read in the old SB6 file to convert to later format.
Where am I going wrong?
Thanks
Nev

NewsArchive
11-07-2013, 02:39 AM
Located SignTool.exe and now only get the ErrorCode -1.
Nev

NewsArchive
11-07-2013, 02:39 AM
Nev,

> Located SignTool.exe and now only get the ErrorCode -1.

That means, Microsoft Authenticode was unable to code-sign.

Post again the "Processing Uninstall Code-Signing..." compiler part to
verify that you are really using the correct Authenticode tool.

Assuming, you are using the Microsoft SignTool.exe in Tools | Options | File
Locations and all required Authenticode components are registered on your
machine, it's caused by (at least) one of the following:

1. The certificate that you are using expired. Please check the
code-signing certificate expiration date.

-and/or-

2. The certificate configuration information is incorrect (e.g. wrong
password). Please check the configuration.

-and/or-

3. If you support timestamp, then "something" might block access to the
timestamp server. Try to disable timestamping to see if this makes a
difference. If it works fine, put the signtool.exe to the exclusion list to
avoid real-time monitoring or switch to another timestamp server and re-try.

Hope this helps a bit.

BTW, this has absolutely nothing to do with the SetupBuilder version you are
using.

Friedrich

NewsArchive
11-07-2013, 02:40 AM
Thanks Friederich
Just checked the password again and see that I missed an upper case letter.
All is working again.
Thanks
Nev

NewsArchive
11-07-2013, 02:40 AM
Hi Nev,

> Thanks Friederich
> Just checked the password again and see that I missed an upper case
> letter. All is working again.

Perfect. Thanks for the update.

Friedrich