none
signer's certificate is not valid

    Question

  • I have programmed succesfully with VB 4.0 for years and have recently started to "Update" myself with Visual Basic 2005.  I tried to build an application to distribute via CD.  I received the following error:

    Error 2 SignTool reported an error 'Failed to sign bin\Release\Counting Stewards data entry.publish\\setup.exe. SignTool Error: ISignedCode::Sign returned error: 0x80880253

     The signer's certificate is not valid for signing.

    SignTool Error: An error occurred while attempting to sign: bin\Release\Counting Stewards data entry.publish\\setup.exe

    '. CSDE
     

    I am totally "out to lunch." I have no clue of what this is about and cannot find anything in my references which address it.  I have found no code on line that enlightens me.  Is there a simple explanation and/or fix?  Where can I learn more in order to avoid this in the future?

    Thanks in advance for any help.

     

    Wednesday, November 15, 2006 3:50 PM

Answers


  • -In VB2005
    -Go to the property of the Project
    -Select the Signing tab
    -Click 'create test certificate' button
    - it will ask for new password 2 times and you have another 1 year extension!
    • Proposed as answer by HunB Tuesday, December 09, 2008 9:28 AM
    • Marked as answer by Mike FengModerator Thursday, July 05, 2012 5:00 AM
    Saturday, November 24, 2007 5:57 AM

All replies

  • Thank you for your quick response.  I believe I understand.  The purpose of the signer's certificate is to improve security for sending stuff over the internet.  Is this correct?  If it is, then this is more than I need.  I am not interested in sending applications or data over the internet.  All I want to do is create an application that I can install on  my church's computer so that the people who count Sunday's offering will have a tool to organize their work, which can be a complex and error-prone process.  Is there any way that I can do that?  Must I have a signer's certificate?
    Wednesday, November 15, 2006 10:13 PM
  • I modified the url in the setup.exe file clickonce creates and then tried to resign the file using the following command

     signtool sign /f TradingPlatform.pfx setup.exe
     

    where TradingPlatform.pfx is a valid certificate in the same directory as setup.exe.

     Here is my output

    Done Adding Additional Store
    SignTool Error: ISignedCode:Tongue Tiedign returned error: 0x80070057
            The parameter is incorrect.

     

     

    If i use the signtool wizard i get the very informative error:

    SignTool Error: An error occurred while signing: <>

     

    If i try to sign the setup.exe file before i modify it, it works fine.  Does this mean you can not modify an already signed file and then resign it using this tool????

     

    Thursday, July 05, 2007 9:00 PM

  • -In VB2005
    -Go to the property of the Project
    -Select the Signing tab
    -Click 'create test certificate' button
    - it will ask for new password 2 times and you have another 1 year extension!
    • Proposed as answer by HunB Tuesday, December 09, 2008 9:28 AM
    • Marked as answer by Mike FengModerator Thursday, July 05, 2012 5:00 AM
    Saturday, November 24, 2007 5:57 AM
  • I had the very same problem, your answer solved it. Thanks!!!
    Wednesday, November 28, 2007 7:20 PM
  •  

    oh

    u solved my problem too

    many thx!!!

     

    one more question,

    for the next expired date, i am supposed to do the same thing?

     

    many thx

    HunB

    ^__*

    Tuesday, December 18, 2007 7:19 AM
  •  

    Wednesday, December 19, 2007 4:34 PM
  •  

    My problem is solved.

     

    Thanks Smile

     

    Wednesday, December 19, 2007 4:36 PM
  • jam66,

     

    thank you very much. The official MS workaround to this issue involves creating a new C++ program to generate a new certificate (http://support.microsoft.com/kb/925521), I was sure there was a simpler way to do it!

     

     

    Friday, January 11, 2008 9:52 PM
  • That solved my problem too in C#.

     

    Go to Signing (Properties>Signing)

    Create test certificate.

     

    and thats it.

     

    Thanks.

     

    Monday, January 21, 2008 10:03 PM
  • THANKS so much!   Works also in VB 2008 for projects migrated from VB 2005.

     

    Wednesday, January 23, 2008 7:31 PM
  • Is it possible to just extend an existing certificate, or to make the certificate last more than the year?

     

    I ask because when a new certificate is created, all the users where the application is deployed will need to do a certain amount of work. (such as remove the old link and create the new link to the install url.)

     

    Friday, February 01, 2008 12:53 PM
  • Click the CREATE NEW SIGN, leave passwords blank...

     

    No More sign required.

     

    Friday, February 29, 2008 6:33 PM
  • This really helped me too.

     

    Thanks.

     

    Dan

     

    Monday, May 12, 2008 8:51 PM
  • The Microsoft workaround allows to keep your user's certificates valid.  (Otherwise all your users will have to authorize the "new" application...

    You can get an already compiled version at

    http://www.may.be/renewcert/

    Once you get the new certificate, don't forget to select the new file from Visual Studio's signature tab.  Visual Studio won't re-read it, even if the file has changed :-(

    Yves
    Friday, July 04, 2008 2:29 PM
  • Where do I find this information for Visual Studio 2005 or VS 2008?
    Wednesday, August 20, 2008 11:45 AM
  • Great. it is working
    Thursday, May 21, 2009 5:35 PM
  • Thanks a bunch. It solved the problem!
    Wednesday, June 17, 2009 5:50 PM
  • Thanks,
    Resolved my problem.

    Airton
    JOAB
    Friday, December 18, 2009 11:30 AM
  • It's the advice that keeps on giving!  thx
    Monday, April 05, 2010 5:57 PM
  • thanks a ton.

    U solved my problem

     

    Tuesday, June 29, 2010 11:16 AM
  • Brilliant, it even worked in VS2008.

    Thanks,

    Ray

     


    Software Outsourcing by Beztec.com

    Thursday, October 07, 2010 2:29 PM
  • Thanks, it solved my problem at VS2005

     

    Osvaldo

    Wednesday, October 20, 2010 4:41 PM
  • Thanks man really usefull.

     

     

    Zubarik

    Saturday, June 25, 2011 9:57 AM
  • Also in Visual studio 2010 I solved the problem in project properties.

    The message colud be more clear  "signer's certicate is EXPIRED" (in my case) and not a generic 'not valid'...

    Any way, many thanks.

    Cesare

     

     

     

    Monday, August 01, 2011 10:12 AM
  • simplest solution is to uncheck the sign click once manifests checkbox in project properties
    Monday, October 10, 2011 3:24 PM
  • Great answer, works in VS2010 also.

     


    Mark Harby Nottingham, UK
    Friday, December 23, 2011 1:19 PM
  • Thank you!!! Solve it!!
    Friday, December 23, 2011 9:01 PM
  • THANKS MAN, THIS IS THE SOLUTION ONE
    Wednesday, May 09, 2012 5:08 PM
  • Saint Immediately. You have saved my life with this information.

    :-) THANKS :-) THANKS:-) THANKS:-) THANKS:-) THANKS:-) THANKS:-) THANKS


    Federico

    Thursday, June 21, 2012 1:53 PM
  • Also works for me using VB 2008

    Thanks a lot.

    Tuesday, July 10, 2012 2:22 PM