Wednesday, August 01, 2012 5:49 PM
All of the sudden, whenever I try to use SignCode on my main release computer to sign a binary, SignCode simply hangs until I kill it with Task Manager. No error messages are displayed. After some investigation, I've discovered the following:
* If I remove the timestamp switch from the command line, it works fine without hanging.
* I can sign just fine from other computers, even with the timestamp switch.
So, it seems the timestamp call is causing problems on my release computer. Any ideas what could be causing this, or how I could troubleshoot?
- Moved by Mike Dos ZhangMicrosoft Contingent Staff Thursday, August 02, 2012 2:33 AM SDK tools issue (From:General Windows Desktop Development Issues)
Wednesday, August 01, 2012 6:25 PMMaybe it waits for an external web site to provide timestamp (unless you're running your own service). Getting a stack trace while it's waiting may be helpful.
Friday, August 03, 2012 12:24 AM
Yes, signtool was hanging on the network call, yet other apps could use the network just fine (e.g., I submitted the post above on the same computer where this problem was happening).
Turns out, the problem was that I have two network adapters on this computer, and one of them had lost a network connection. Whereas my browser seemed to find and use the connected adapter, signtool was plugging away using the disconnected one. Once the connection was reestablished, the problem went away.
- Marked As Answer by seandr Friday, August 03, 2012 12:25 AM