Compiler Error GEN 1053 appears when Digital Signature set to Yes or No

[linder]

I think 3 and 3 are already good values because they allow more retries and give the protection system more time to cool down. But we can increase it to 5 and 5, no problem. BTW, support requests for code-signing are not even on our list of Top 500 support requests. In other words, code-signing is not a general issue at all (it's machine specific). If a code-signing issue is reported then in most cases it is 1) caused by an expired code-signing certificate or 2) by a buggy or too protective anti-virus and/or anti-spyware system that blocks access to the timestamp server. I hope the new default values can help you.

Friedrich

[jgamalinda]

In other words, code-signing is not a general issue at all (it's machine specific). If a code-signing issue is reported then in most cases it is 1) caused by an expired code-signing certificate or 2) by a buggy or too protective anti-virus and/or anti-spyware system that blocks access to the timestamp server. I hope the new default values can help you.
Friedrich

In this case it started as #1 expired, but then timing showed up.

Problem is when signing fails with the "Compiler Error GEN 1053" there's no way to tell the problem. I need to see the command line output of the SignCode.exe cmd line that shows the error. It would help if SB had a way.

I tried changing Tools, Options, File Locations the SignCode.exe to my own SignCarl.BAT. It does run, but because you hide the window I cannot add a PAUSE and see what's going wrong. So one tweak you could make is if the Sign Code program is a BAT or CMD that you do not hide the window. Or add a Pragma to not hide the window.

I changed my BAT to redirect to a file and do see some info. I need to put more time into it, but I'm not sure it's possible.

Here's my BAT file replacement for SignCode.exe

echo signing  >> V:\alpha\Emem\SignCarl\signlog.txt
@echo parm 1: %1  >> V:\alpha\Emem\SignCarl\signlog.txt
@echo parm 2: %2  >> V:\alpha\Emem\SignCarl\signlog.txt
@echo parm 3: %3  >> V:\alpha\Emem\SignCarl\signlog.txt
@echo parm 4: %4  >> V:\alpha\Emem\SignCarl\signlog.txt
@echo parm 5: %5  >> V:\alpha\Emem\SignCarl\signlog.txt
@echo parm 6: %6  >> V:\alpha\Emem\SignCarl\signlog.txt
@echo parm 7: %7  >> V:\alpha\Emem\SignCarl\signlog.txt
@echo parm 8: %8  >> V:\alpha\Emem\SignCarl\signlog.txt
@echo parm 9: %9  >> V:\alpha\Emem\SignCarl\signlog.txt
@echo parm 10: %10  >> V:\alpha\Emem\SignCarl\signlog.txt
@echo parm 11: %11  >> V:\alpha\Emem\SignCarl\signlog.txt
@echo parm 12: %12  >> V:\alpha\Emem\SignCarl\signlog.txt
@echo parm 13: %13  >> V:\alpha\Emem\SignCarl\signlog.txt
@echo parm 14: %14  >> V:\alpha\Emem\SignCarl\signlog.txt
@echo parm 15: %15  >> V:\alpha\Emem\SignCarl\signlog.txt
@echo parm 16: %16  >> V:\alpha\Emem\SignCarl\signlog.txt
@echo parm 17: %17  >> V:\alpha\Emem\SignCarl\signlog.txt
@echo parm 18: %18  >> V:\alpha\Emem\SignCarl\signlog.txt
@echo parm 19: %19  >> V:\alpha\Emem\SignCarl\signlog.txt

V:\alpha\Emem\SignCarl\signcode.exe  /tr 3 /tw 4  %1 %2 %3 %4 %5 %6 %7 %8 %9 %10 %11 %12 %13 %14       >> V:\alpha\Emem\SignCarl\signlog.txt
rem pause

Here's the result (I do not get the output of signcode.exe):

signing
parm 1: -spc
parm 2: "V:\alpha\SignCodeBCS\xxxxxCredentials.spc"
parm 3: -v
parm 4: "V:\alpha\SignCodeBCS\xxxxPrivateKey.pvk"
parm 5: -i
parm 6: "http://www.xxxxx.com/"
parm 7: -n
parm 8: "xxxxxxx"
parm 9: -t
parm 10: -spc0
parm 11: -spc1
parm 12: -spc2
parm 13: -spc3
parm 14: -spc4
parm 15: -spc5
parm 16: -spc6
parm 17: -spc7
parm 18: -spc8
parm 19: -spc9

I don't see the EXE name in the command line.

[linder]

Hello,

Why don't you use the "#run..." compiler directive to run your batch file (including your PAUSE command in it) instead of the "#code-sign application..." directive? Perhaps you can then find out why your machine has a problem with code-signing? And if it still fails (e.g. because your certificate is password protected and the password embedding process is blocked by your protection software), you can try the .PFX and use SignTool.exe (which can handle passwords via the command line).

BTW, it is impossible to use a batch file via "Tools | Options | File Locations" because the file name determines the code-signing method (SignTool.exe or SignCode.exe). The SignCode.exe Location specifies the pathname of the signcode.EXE that performs the signing tasks.

Hope this helps a bit.

Friedrich

[Robin77]

The compiler error GEN 1053 occurs when the Digital Signature option is set to either Yes or No. This issue suggests that there may be a problem with the configuration or compatibility of the digital signature settings in your project. Ensure that all related settings are correctly configured and that your development environment supports the chosen digital signature option. Consider reviewing documentation or seeking support for specific guidance on resolving this error.