Code sign fails GEN1053 and Error code 21

Hi all,

My client is getting an error when code signing one exe:

"Compiler error GEN1053: Code signing process failed. Error Code 21"

Anyone know what this refers to?

Best regards

--
Arnor Baldvinsson
Icetips Alta LLC

> My client is getting an error when code signing one exe:
>
> "Compiler error GEN1053: Code signing process failed. Error Code 21"
>
> Anyone know what this refers to?

Hi Arnor,

Has the code signing certificate expired perhaps?

Charles



--
-------------------------------------------------------------------------------------------------------
Charles Edmonds

cjeByteMeSpammers@lansrad.com (remove the "ByteMeSpammers" to email me)

www.learnh5fast.com - Master building web and mobile apps with Clarion H5!
www.clarionproseries.com - ProDocument, ImageEx, ProScan, ProImage, ProPath
and other Clarion developer tools!
www.seal-soft.com - The xProduct Clarion templates - xWordCOM, xToolTip,
xDataBackup Manager and more!
www.ezchangelog.com - "Free ChangeLog software to manage your projects!"
www.setupcast.com - "A revolutionary new publishing system for software
developers - enhanced for SetupBuilder users!"
www.ezround.com - "Round Corner HTML tables with matching Banners, Buttons
and Forms - Now with PNG support!
www.fotokiss.com - "World's Best Auction Photo Editor"
www.lansrad.com - "Intelligent Solutions for Universal Problems"
-------------------------------------------------------------------------------------------------------

Hi Arnor,

> "Compiler error GEN1053: Code signing process failed. Error Code 21"

Microsoft code-signing only returns "success" or "failure". So I think he
is using a wildcard in his code-signing process and all signing attempts
failed.

It failed because:

1. Code-Signing Certificate expired
2. Password incorrect
3. Timestamp server not accessible
4. SignTool component "unregistered" - see CapiCom here:
http://www.lindersoft.com/forums/sho...5074-and-later
5. The protection software blocks SignTool or the code-signing process.

Friedrich

Hi Friedrich,

> 1. Code-Signing Certificate expired
> 2. Password incorrect
> 3. Timestamp server not accessible
> 4. SignTool component "unregistered" - see CapiCom here:
> http://www.lindersoft.com/forums/sho...5074-and-later
> 5. The protection software blocks SignTool or the code-signing process.
This particular exe is a single exe install. There are several more SB
scripts that have multiple EXE and multiple dlls and all of those work
fine and are code signed correctly. He's using the global settings for
code signing and only SHA2. He has a new certificate (January) but it
has been used couple of times and it also failed on this one exe as
well. He's going to try to disable his AV and see if that helps.

Best regards,


--
Arnor Baldvinsson
Icetips Alta LLC

Hi Friedrich,

> code signing and only SHA2. He has a new certificate (January) but it
> has been used couple of times and it also failed on this one exe as

Translation:<g> The certificate has been used in 2 previous builds of
all our software and it worked fine in both cases except on this one
exe. He's going to test turning the AV off while code signing see if
that helps.

Best regards,

--
Arnor Baldvinsson
Icetips Alta LLC