Signing problems

Paquet Builder
1

Which timestamp server URL are you using? Such an error generally happens when the timestamp server is not working correctly.

2

In 2 out of 3 builds the signing of the package fails with this error:

Signing…
Digital Sign API FAILED error code #-2147024864
Code signing successfu

Why?

3

I use this:

http://timestamp.verisign.com/scripts/timstamp.dll

4

OK. Error code means “The process cannot access the file because it is being used by another process”.
Have you any third-party software like antivirus that could block access to the EXE file?

5

Hi, I have a very similar problem. Here is the compilation log entry:

  • Digitally signing internal DLL:
    GSignCode – simple code signing utility
    Copyright G.D.G. Software 2011-2013. All rights reserved.
    Certificate:
    Signing…
    Digital Sign API FAILED error code #-2147012889
    Code signing successful.

I use AVG Antivirus, and it is disabled. My OS is Windows 8.1. My timestamp server is http://timestamp.digicert.com.

What is your advice, please?

6

This error means: ERROR_INTERNET_NAME_NOT_RESOLVED
Is http://timestamp.digicert.com accessible by GSignCode.exe?
For instance, did you allow GSignCode.exe to access the Internet if you have a firewall?

7

Thank you for the prompt reply.
I have made an explicit exception for GSignCode.exe in the Windows firewall.
I am not running any other firewall on my computer.
I have no trouble signing with Visual Studio Command Prompt, however I can only sign the package components and the package itself this way. I cannot sign the internal DLL and uninstaller. Besides, that’s a pain when Paquet Builder is supposed to do the signing.

8

Sorry … continuing …
On retesting I still have the same error. It errors on each component, the internal DLLs, the uninstaller, and the final EXE.

Is it possible that the problem is with the way the DigiCert timestamp link works, i.e., it does not specify a specific timestamp DLL on their end?

9

Please try another timestamp server: Verisign or Comodo.

http://timestamp.verisign.com/scripts/timstamp.dll

You are not obligated to use the server of the company which issued your certificate.

10

Same issue here.

Was failing 2 out of 3. Just keep trying over and over until get success. Real pain, actually big pain when trying to get software completed.

Using default time stamp URL:

http://timestamp.verisign.com/scripts/timstamp.dll

Now if fails everytime. No change on my end, everything the same. Disabled firewall completely after reading above replies, same issues:

GSignCode – simple code signing utility
Copyright G.D.G. Software 2011-2013. All rights reserved.
Certificate:
Signing…
Digital Sign API FAILED error code #-2147024864
Code signing successful.
Closing the package file and cleaning memory…
Note: the archive file was stored in the temporary cache for future builds.

Any help getting this solved would be greatly appreciated. Have software to get ready for school in the morning.

Thanks!

11

Are you using an antivirus or antispyware solution? Some third-party program that would block the EXE file because the error code you reported is not the same as previously. It means:
ERROR_SHARING_VIOLATION / “The process cannot access the file because it is being used by another process”.

12

I disabled everything. Firewall and Panda. After laying my head on desk for 1 hour nap. Tired again and worked. Just to test, 5 minutes later rebuilt and failed.

13

White list the output folder in your Panda.
And make sure you have no other application opened, even Explorer windows opened to display the output folder.