Hi,
None of my Setupbuilder scripts will codesign today, but stops with
Compiler error 1053, code sign error code 1.
Got a major Windows update yesterday. Could that be the reason ?
Cheers
/Poul
Hi,
None of my Setupbuilder scripts will codesign today, but stops with
Compiler error 1053, code sign error code 1.
Got a major Windows update yesterday. Could that be the reason ?
Cheers
/Poul
Certificate(s) expired?
Simon Kemp
> Got a major Windows update yesterday. Could that be the reason ?
Possible that it's the windows update is causing problems, but it's not a
complete failure across the board. The error I'm seeing is that the
timestamp server can't be reached or returned an invalid response, and I'm
getting the same error from MOST of the timestamp servers available from the
SB list. But I AM able to sign using one of the following two:
http://timestamp.globalsign.com/scripts/timestamp.dll
http://timestamp.digicert.com
So try one of those timestamp servers and see if you get the same results.
Terry
I find that to be a problem with the Timestamp URL, either temporarily down
or busy, leading to excessive delay and timeout.
Try switching. There are quite a few, Verisign and Comodo being the most
common.
Alternatively just wait a short while and try again.
Sim
Thanks guys,
I have now tried all timeservers and to no avail.
Certificate is valid another 1.5 year.
I think I have seen somewhere that a reinstall of signtool could
resolve issues after a Windows updta. Any comment on that ?
/Poul
Try:
http://timestamp.comodoca.com/authenticode
http://timestamp.verisign.com/scripts/timstamp.dll
http://trustcenter.de/codesigning/timestamp
http://timestamp.globalsign.com/scripts/timstamp.dll
http://tsa.starfieldtech.com
http://www.startssl.com/timestamp
http://sha256timestamp.ws.symantec.com/sha256/timestamp
Sim Scherer
Hi Sim,
Appreciate your answering but none of these works.
For some of them I get a code sign error code 1 and for some code sign
error code 2.
I don't know the difference ?
/Poul
Poul,
Try this combination (for SHA-1 and SHA-2):
http://timestamp.verisign.com/scripts/timstamp.dll
http://timestamp.globalsign.com/?signature=sha2
Friedrich
That happened to me several times today. But it finally worked after
re-trying.
Jeff Slarve
www.jssoftware.com
Twitter free since Jan 11, 2016
I'll search help files & Google for you.
Grammar troll's, are the worse.
Hi Paul,
Yes I'm seeing the same thing.
I managed to code sign yesterday, then applied the latest windows 10
updates, and then the code signing started to fail.
Regards,
Neil.
There are currently 1 users browsing this thread. (0 members and 1 guests)