cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Go to solution

Signtool failing with http://tsa.starfieldtech.com as timestamp source

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?

 

Mark

1 ACCEPTED SOLUTION

I have been able to sign again using this timestamp source, so the issue - whatever it was - has been resolved.

View solution in original post

10 REPLIES 10

I'm getting the same issue with that timestamp source.

 

This one works however:  http://timestamp.verisign.com/scripts/timstamp.dll

 

dcc

I have the same problem.

Thanks, at least I am not alone.

 

No idea who to escalate this with.

Try  practices@starfieldtech.com.

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 have been using this as an alternative, http://timestamp.globalsign.com/scripts/timestamp.dll

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 ?

I have been able to sign again using this timestamp source, so the issue - whatever it was - has been resolved.

View solution in original post

Thanks for reporting this.

I can also confirm that I can now successfully sign code using tsa.starfieldtech.com.

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.