Recently Compiled .EXE files cannot be Code Signed

In two different projects, two recently compiled .EXE files are no longer able
to be code signed. I get the error: 'Compiler error GEN1053: Code signing
process failed.' Other .EXE files in one of the projects are successfully
signed and both of the problem .EXE files use to go through the signing process
without incident. Any ideas about what can cause the error above when code
signing an executable? I checked the attributes of the files and they are not
set to read-only and the executables load and run as usual. Something is
causing the code signing process to fail.

Thanks,

John

That could mean that the time stamp server you use is not available at the
moment.
If you're using the Comodo server, try switching to Verisign. Or vice
versa.
Both URLS are in the SB documentation.

Also make sure you haven't changed any paths as to where your certificate
files are stored, etc.

Jane

Hi Jane,

Thanks for these things to check.

The time stamp server not being available makes sense but other .exe files in
the same directory are being signed in the same SB compile (and I am getting a
consistent failure on the same .exe files). Also, the paths to the .exe files
are correct and the .exe location has not changed. Just to be sure, I just
checked and everything is pointing to the correct location. It is very strange
because the signing worked fine for these .exe files in previous SB
compiles.

John

Hi John,

I am sure it's not caused by the SetupBuilder compile itself. Perhaps you
are using an "expired" certificate for that file?

You can execute SignCode.exe (located in the \Lib folder) and try to sign
the .exe using the same information you have in your script. Perhaps
SignCode.exe gives you an error message.

Friedrich

Hi Friedrich,

Yes, you are right, it has nothing to do with the SetupBuilder compile. The
certificate being used is the same for all of my signed files so that doesn't
appear to be the problem. I'll try executing the SignCode.Exe directly to see
if that yields any additional info.

John

Hi Friedrich,

Thanks! Executing the SignCode.exe directly gave me the info I needed to track
down the problem. It said the file either did not exist or was read only. I
checked the attributes on the file and they were okay so I checked the task
manager and both of the problem files were in the process list! I ended those
processes and now the code signing is working as it has.

John

John - Friedrich,

This proves black on white that Setup Builder not only is "the" installer
software to have but also you can use it as a debugger app for Windows Task
Manager <BG> !

The other case were this happens is when the version ressource part of the
exe is badly done (hapened to me here) - recompiled and all went fine....

Merci - Thank you

JP

Data Management Center
A tool to help you Transfer - Import - Export your data so easily ....

http://www.dm8.fr

Hi JP,

Thanks for the tip!

John

Hi John,

I have improved the compiler. "Locked" files are detected when doing a
code-sign or embed Vista-manifest now.

Friedrich

Hi Friedrich,

That's great to hear!

Thanks,

John