We keep getting a "Compiler error GEN1053: Code signing process failed." on the
setup.exe file.
All other files in the installation package code sign without issue.
Any suggestions would be appreciated.
Ken Stone
We keep getting a "Compiler error GEN1053: Code signing process failed." on the
setup.exe file.
All other files in the installation package code sign without issue.
Any suggestions would be appreciated.
Ken Stone
Ken,
> We keep getting a "Compiler error GEN1053: Code signing process failed."
> on the
> setup.exe file.
> All other files in the installation package code sign without issue.
>
> Any suggestions would be appreciated.
If you are using the same certificate and configuration information, then
it's caused by your protection software (false-positive bug). If you are
interested, post the compiler window information. Perhaps we can see what
it going wrong.
BTW, are you using the "Global SHA Code-Signing Type" (Tools... | Options...
| Code-Signing)?
Friedrich
We have disabled McAfee for the duration of the build.
Still getting the attached error.
Thanks
Ken Stone
We've found the issue. Had an ELSE statement in the wrong sequence...
Ken Stone
Ken,
>
> We've found the issue. Had an ELSE statement in the wrong sequence...
>
Hmmmm, an ELSE statement in the wrong sequence caused this? Could you
please give some more information? You can reproduce this with a wrongly
set ELSE statement?
Thanks,
Friedrich
See the attached..
Ken Stone
Ken,
>
> See the attached..
>
From the technical point-of-view, it is impossible that the "Else" Statement
sequence caused this. Microsoft Authenticode handles the code-signing
process after the compilation process and this is not related to the script.
All the script commands are executed at installer runtime and not script
compile time. See attached screenshot. I have created a script snippet
with your code and it code-signs fine.
Friedrich
Friedrich,
> From the technical point-of-view, it is impossible that the "Else" Statement
> sequence caused this. Microsoft Authenticode handles the code-signing
> process after the compilation process and this is not related to the script.
> All the script commands are executed at installer runtime and not script
> compile time. See attached screenshot. I have created a script snippet
> with your code and it code-signs fine.
You missed one extraneous ELSE but I tried it and everything signed as
expected. Unsure how the runtime would handle it but...<g>
Lee White
Lee,
> You missed one extraneous ELSE but I tried it and everything signed as
> expected. Unsure how the runtime would handle it but...<g>
Else
Else
Ouch! Very interesting <g>. The compiler should catch this error. I'll
fix this.
Thank you!!!!!
Friedrich
Hi Friedrich,
Thanks for the followup.
- When we corrected the ELSE statement, the errors stopped.
- The ELSE statement was the only thing we changed.
We are completely puzzled...
Ken Stone
There are currently 1 users browsing this thread. (0 members and 1 guests)