Compiler error GEN1053: Code signing process failed. Error Code: 2

[NewsArchive]

With all of this talk regarding code-signing 3rd-party DLLs, I decided
to go ahead and sign all of the ones that I distribute with my
vertical market products. I added the script command to code-sign
*.dll, and all were processed successfully except ClarionDrv.dll,
which resulted in the message, "Compiler error GEN1053: Code signing
process failed. Error Code: 2".

I see lots of mentions here regarding error code -1, but nothing about
this.

Mike Hanson
www.boxsoft.net

[NewsArchive]

BTW, the compilation failed on that error, but when I ran it again, it
proceeded fine. It even said that ClarionDrv.dll was already
code-signed.

Mike Hanson
www.boxsoft.net

[NewsArchive]

No idea in truth about the error code but I noticed (and reported in
NG) about locked clarion dll's

You explained about the RTL etc (so I dropped that idea and close my
app and IDE before code signing)

maybe this is what caused this error ?
IDE opened after compiling and app or the app itself opened ?

What is that dll or whose is it ?
(careful to what you answer on "who" as for Didier it could be "you" -
<g>)

--
JP
__________________________________________________ _____

For those who do not understand ... : "Qui bene amat bene castigat."
__________________________________________________ _____

DMC - Data Management Center : a tool to let you Migrate Import Export
Transfer your Data
www.dmc-fr.com

[NewsArchive]

> BTW, the compilation failed on that error, but when I ran it again,
> it proceeded fine. It even said that ClarionDrv.dll was already
> code-signed.

It's very well possible that your protection software was too protective
(buggy) and blocked some code-signing processes in this case.

Friedrich

[NewsArchive]

I suppose anything's possible. I'm still using Norton 360, which I
intend to replace with ESET NOD32 when I get my new machine. It
sometimes does odd stuff, but this doesn't fit the regular mould.

Mike Hanson
www.boxsoft.net

[NewsArchive]

Mike,

Do you have the "Skip if already code-signed" option enabled?

Error code 2 means that the code-signed process completed but there were
unspecified warnings. So in fact, this code-signing process did not succeed
100%.

Friedrich

[NewsArchive]

Yes, it's told to skip if already signed, and to sign permanently.

Mike Hanson
www.boxsoft.net

[NewsArchive]

>
> Yes, it's told to skip if already signed, and to sign permanently.
>

Then your protection software blocked access to timestamp. It only sent
parts (or incorrect) values to the timestamp server and Authenticode was
unable to proceed with the returned (if any) values. So you have a signed
file now, but it is not correctly timestamped. As a result, the signing
tool returned Error Code 2.

Friedrich

[NewsArchive]

Understood. I'll check that file to see if there's anything odd.

In this case, it's ClarionDrv.dll, copied into my application
directory during build, so it will be replaced and given another
chance to be signed later. <g>

Mike Hanson
www.boxsoft.net

[NewsArchive]

Friedrich

This is with antivirus shutdown
I don't get it?

Dan

[NewsArchive]

Dan,

> This is with antivirus shutdown
> I don't get it?

Is the password correct? Is the code-signing certificate still valid? Is
the timestamp server accessible? Can the application file be code signed
(valid PE header)?

It's (at least) caused by one of the above ;-)

Friedrich

[NewsArchive]

BTW, and you'll get this error if your "regset.exe" is already code-signed
and you did not enable the "Skip if file is already code-signed" checkbox in
the "#code-sign application..." directive.

Friedrich

[NewsArchive]

Similar to this...

Friedrich

[NewsArchive]

I will certainly check these things, but it is a Clarion app just like the
rest that do not error out in the same project.

Thanks

Dan