NewsArchive
03-10-2014, 02:59 AM
I had to uninstall then reinstall SetupBuilder, all of my settings (Tools >
Options) were retained. At first I got a compile error related to having mixed
.lib file versions. Doing a clean install of the latest version fix that.
Now, every time I try to compile and code sign either a file using either a
Preprocessor: Code-sign Application or having the setup executable itself
signed, I get the following error:
SIGNTOOL: D:\Projects\ThPro3\Program\ThPro.exe
Compiler error GEN1053: Code signing process failed. Error Code: 1
I have looked back for others experiencing this error and, according to
Friedrich, it is caused by something outside of SetupBuilder. The problem I
have with this is that the signing program (SignTool.exe+capicom.dll) haven't
changed, the certificate (fairly new) hasn't changed or expired, the password
is entered correctly (I re-entered it to be sure) but still I get this error.
The only thing that has changed, so far as I can tell, is a reinstallation of
SetupBuilder.
I tried using SignTool outside of SetupBuilder with the command line:
SIGNTOOL sign /f bcs.pfx /p [MySecretPassword] d:\Projects\ThPro3\Program\ThPro.exe
I get the following error:
SignTool Error: Signtool requires CAPICOM version 2.1.0.1 or higher. Please
copy the latest version of CAPICOM.dll into the directory that contains
SignTool.exe. If CAPICOM.dll exists, you may not have proper
permissions to install CAPICOM.
I checked and Capicom.dll in the same folder is 2.1.0.1 and is the same one
that used to work. I looked to see if there were any other Capicom.dll files
on the path or in Windows or Windows\System32 folder. Negative.
Anybody have any idea what's going on?
Peter Gysegem
Beaver Creek Software
Options) were retained. At first I got a compile error related to having mixed
.lib file versions. Doing a clean install of the latest version fix that.
Now, every time I try to compile and code sign either a file using either a
Preprocessor: Code-sign Application or having the setup executable itself
signed, I get the following error:
SIGNTOOL: D:\Projects\ThPro3\Program\ThPro.exe
Compiler error GEN1053: Code signing process failed. Error Code: 1
I have looked back for others experiencing this error and, according to
Friedrich, it is caused by something outside of SetupBuilder. The problem I
have with this is that the signing program (SignTool.exe+capicom.dll) haven't
changed, the certificate (fairly new) hasn't changed or expired, the password
is entered correctly (I re-entered it to be sure) but still I get this error.
The only thing that has changed, so far as I can tell, is a reinstallation of
SetupBuilder.
I tried using SignTool outside of SetupBuilder with the command line:
SIGNTOOL sign /f bcs.pfx /p [MySecretPassword] d:\Projects\ThPro3\Program\ThPro.exe
I get the following error:
SignTool Error: Signtool requires CAPICOM version 2.1.0.1 or higher. Please
copy the latest version of CAPICOM.dll into the directory that contains
SignTool.exe. If CAPICOM.dll exists, you may not have proper
permissions to install CAPICOM.
I checked and Capicom.dll in the same folder is 2.1.0.1 and is the same one
that used to work. I looked to see if there were any other Capicom.dll files
on the path or in Windows or Windows\System32 folder. Negative.
Anybody have any idea what's going on?
Peter Gysegem
Beaver Creek Software