I have recently had the Signtool not being able to sign files:
Done Adding Additional Store SignTool Error: An unexpected internal error has occurred. Error information: "Error: SignerSign() failed." (-2146893818/0x80090006)
If I use a different server, or don't specific use the timestamp option, then I am able to sign a file.
Is it just me?
Solved! Go to Solution.
Same issue for a few days. Just found this thread. Anyone have a good substitute time stamp server? The suggested server (http://timestamp.verisign.com/scripts/timstamp.dll) does not work. Not an internal error, but message is could not be reached or invalid response.
I am having a similar problem using jarsigner to sign Java packages.
The signing seems to work OK, but when you attempt to verify the signature it fails.
Using an alternative TSA (e.g. http://timestamp.digicert.com) works fine.
Has anyone got a response or fix for this ?
Is it OK to use an alternative TSA or will that somehow break in future ?
GoDaddy rep says the limit is 50 timestamp requests per hour. Nothing they can do about it. Since my solution has 138 files, I simply cannot use their server. I would think a lot of coders are in the same situation. Sorry GoDaddy, but you are forcing me to use another vendor for this. It's a problem created by someone at GoDaddy that has no clue about code-signing obviously. If they had set a limit per DAY (600/day for example) instead of per hour then we would be good to go.