Constantly having to restart Windows 7 to time-stamp installer... Why?

1

I am using a Windows 7 (64-bit) machine as a build server and have encountered a strange problem.

One of my build steps is to apply a code signing certificate using a command like this:

signtool sign /v /sm /s my /n "Company" /t http://timestamp.verisign.com/scripts/timestamp.dll /d "Software Name" "installer.msi"

After starting up the machine, this command works time after time for a while... and then it returns the error:

SignTool Error: The specified timestamp server either could not be reached or returned an invalid response.

The problem cannot be resolved until the computer is rebooted. The problem is also specific to this particular machine.

Does anyone have any ideas?

Thanks, Alan

Alan Spark

Posted 2012-05-30T11:46:54.760

Reputation: 243

Having exactly the same problem here. :( – sean717 – 2013-05-16T18:45:16.543

1@sean717 Hopefully you have resolved this by now but if not, see my answer below. – Alan Spark – 2013-05-22T08:04:09.710

My problem is solved. It turned out that the account under which tfs build runs has no access to Web. By enable it back. Everything works now. Yeah. This is embarrassing. – sean717 – 2013-06-04T17:02:15.277

Answers

0

In case it is helpful for anyone else, we "resolved" the problem by putting the signing code into a batch file and retrying the timestamp a few times if it fails.

signtool sign /a /v /sm /s  my /n "Company" /d "Software Name" "installer.msi"
signtool timestamp /t http://timestamp.verisign.com/scripts/timestamp.dll "Software Name" "installer.msi"
if ERRORLEVEL 0 GOTO END
signtool timestamp /t http://timestamp.verisign.com/scripts/timestamp.dll "Software Name" "installer.msi"
if ERRORLEVEL 0 GOTO END
signtool timestamp /t http://timestamp.verisign.com/scripts/timestamp.dll "Software Name" "installer.msi"
:END

Alan Spark

Posted 2012-05-30T11:46:54.760

Reputation: 243

Asked: 2012-05-30T11:46:54.760

Viewed: 1 392 times

Active: 2013-05-22T08:03:08.987