Error Sign Tool Failed With Exit Code 0x1
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about signtool exit code 1 Stack Overflow the company Business Learn more about hiring developers or posting ads with signtool error: no certificates were found that met all the given criteria. us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up signtool fail with Inno Setup with exit code 0x1 up vote 2 down vote favorite 1 Suddenly my Inno Setup compiler stopped working. Since the last time I used it, I just installed a new certificate issued still to the same company. I've configured the sign tool in this way (NAME is the beginning of the string for the Subject in the certificate): mysigntool="C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Bin\signtool.exe" sign /v /a /s my /n NAME /t http://timestamp.verisign.com/scripts/timestamp.dll And then in the Inno Setup .iss file I have: SignTool=mysigntool SignedUninstaller=yes The sign always fails with exit code 0x1, also if I remove the /t and timestamp. Please note that if I run the same command from the command prompt the signing works perfectly. inno-setup code-signing signing code-signing-certificate share|improve this question asked Jun 16 '15 at 8:58 Mauro Ganswer 556621 What does the signtool.exe output? –Martin Prikryl Jun 16 '15 at 9:37 From Inno Setup I do not get much details. When I click run or compile I just get: Compiler Error! Sign Tool failed with exit code 0x1. –Mauro Ganswer Jun 16 '15 at 10:39 add a comment| 2 Answers 2 active oldest votes up vote 3 down vote accepted You need to add $f to the end of your SignTool (in the IDE settings, not the script) in order to actually pass the name of the file to be signed. This is why you're getting the "missing filename" error. See the examples in the Inno help file. share|improve this answer answered Jun 30 '15 at 6:14 Miral 6,37621747 add a comment| up vote 2 down vote First thing to try is obviously to run the signtool.exe standalone to see what errors it output. (I'm aware that you have tri
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up SignTool.exe Sporadically Fails with Exit Code 1 up vote 5 down vote favorite As part of our build system, we use signtool.exe with a certificate to sign our binaries once they've been http://stackoverflow.com/questions/30863018/signtool-fail-with-inno-setup-with-exit-code-0x1 built. Occasionally (it's hard to tell when it will strike), the signing fails: error MSB3073: The command "C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\bin\signtool.exe" [...] exited with code 1. According to the MSDN, an exit code of 1 means that there was an error signing the file. I can verify that the file didn't get signed. I've also noticed that occasionally, the timestamp portion times out with a different error message, albeit that the file still gets signed (without the timestamp). http://stackoverflow.com/questions/9380751/signtool-exe-sporadically-fails-with-exit-code-1 How can I troubleshoot and fix these seemingly random, inconsistent signature failures? cruisecontrol.net digital-certificate signtool share|improve this question edited Feb 21 '12 at 18:37 The Chairman 5,86612234 asked Feb 21 '12 at 16:01 ashes999 4,81684184 I have the same experience: signtool occasionally fails during timestamping. There seems to be no solution other than re-run signtool. –Eugene Mayevski 'EldoS Feb 21 '12 at 16:27 @EugeneMayevski'EldoSCorp some people report updating their Windows XP certificates works, and some other weird stuff like that. I want a definitive answer, since a failed build is very serious for me. But I fear you are right. –ashes999 Feb 21 '12 at 18:08 1 Suppose your timestamping server is completely unreachable (network cable unplugged etc). How would signtool or other tool for the same purpose be able to deal with this? Of course, I wish signtool were more tolerant to failures and tried to perform timestamping once again, but you must be ready for possible timestamping failure anyway. –Eugene Mayevski 'EldoS Feb 21 '12 at 18:14 True. Maybe the answer is to address this at a higher level, such as on the continuous integration server. I'm still hoping for a lower-level solution though. –ashes999 Feb 21 '12 at 20:27 add a comment| 4 Answers 4 active oldest votes up vote 4 down vote accepted I strongly suspect a failing connection to the timestamp server being responsible
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn http://stackoverflow.com/questions/39685417/inno-setup-signing-fails-with-sign-tool-failed-with-exit-code-0x1 more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags http://www.kinook.com/Forum/showthread.php?t=4686 Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Inno Setup - Signing fails with “Sign Tool failed with exit code 0x1” up vote 0 down vote favorite 1 I have Inno Setup script, exit code where I need to use the SignTool=signtool, which is configured properly and worked in past. But it's failing when I try to compile with the following error: Sign Tool failed with exit code 0x1. window windows-installer installer inno-setup installshield share|improve this question edited Sep 25 at 17:36 Martin Prikryl 34.3k1549133 asked Sep 25 at 9:38 YumYumYum 5,78924122215 3 Have you tried to run Sign command directly via command line to see if it also fails? error sign tool You'd see proper error message then. Are you able to compile your installer without Signing? I have encountered simillar issue once where Windows blocked access to installer's temporary files because it treated Compil32.exe as untrusted process. –RobeN Sep 25 at 11:40 add a comment| 1 Answer 1 active oldest votes up vote 2 down vote accepted You didn't provide us any information that we can use to debug your problem. So I'm posting generic instructions to debug issues with a "sign tool". Try command-line compiler (ISCC.exe). It will preserve a full signtool.exe error message in the output: Or temporarily prefix the sign tool command with cmd.exe /k to preserve its output even when compiling in Inno Setup GUI Compiler. E.g.: cmd.exe /k C:\path\to\signtool.exe sign /f C:\mykey.pfx $f See also signtool fail with Inno Setup with exit code 0x1. share|improve this answer answered Sep 25 at 17:34 Martin Prikryl 34.3k1549133 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Not the answer you're looking for? Browse other questions tagged window windows-installer installer inno-setup installshield or ask your own
Albums Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Rate Thread Display Modes #1 09-22-2010, 03:10 PM momsoft Registered User Join Date: 09-25-2008 Posts: 5 Signing the InnoSetup uninstaller I want to sign the InnoSetup uninstaller in addition to the installer. Starting with version 5, InnoSetup includes the possibility of just doing it. Therefore I have included on the .iss file a SignTool command and I am launching the IS compiler from VBP using a Run Program action. This is the command I am using: ISCC.exe /ssigntool=$p %PROJDIR\MyProject.iss And I include all the needed parameters right inside the iss file. The thing is that the setup file is successfully compiled and signed if it already exists, otherwise I am getting the following error: Number of errors: 1 SignTool Error: The file is being used by another process. SignTool Error: An error occurred while attempting to sign: setup.exe Thank you very much. Error in MyProject.iss: Sign Tool failed with exit code 0x1. Compile aborted. momsoft View Public Profile Find all posts by momsoft #2 09-22-2010, 03:25 PM kinook Administrator Join Date: 03-06-2001 Location: Colorado Posts: 5,399 You could also use the Inno Setup action, specifying the /s parameter in the Additional options field on the Options tab, but either way, the error is coming from the signing tool, not Visual Build, and Visual Build itself does not open the setup executable file, so there must be a conflict between signtool and iscc (or some other program using the file). http://www.kinook.com/VisBuildPro/Manual/innoopttab.htm http://www.kinook.com/Forum/showthre...?threadid=3044 kinook View Public Profile Visit kinook's homepage! Find all posts by kinook #3 09-23-2010, 03:41 PM momsoft Registered User Join Date: 09-25-2008 Posts: 5 You are right, I tried first using the Inno Setup action but I used a wrong /s parameter format and I forgot to check back afterwards. In any case, now it seems to be working following your suggestion. Thank you very much momsoft View Public Profile Find all posts by momsoft « Pre