locked
SignTool error - Certificate is not valid for signing 0x80880253 RRS feed

  • Question

  • We got this error the other day when trying to publish. After some searching I came across the Certificate for signing ClickOnce manifests. It has an expiration date of 10/06/2006. So we thought we could just create a new test certificate and then publish. This got us past the error but then the next day a user brought over a detail report.

    System.deployment.application.deploymentexception
    -the deployment identity does not match the subscription

    This is a VB 2005 app that gets publish to a network share so I don't know if I need all this signing security. But I eneded up having to set my machines clock back prior to Oct 6, roll back to a earlier version and then rebuilding the project and redeploying Otherwise I'd have to do a unisntall of one version and then a new install after creating a new Test certificate. This obviously isn't the right way. How do I fix this without ahving to reinstall the app every year after the certificate expires?

     

    Thanks,
    Phil

    Friday, October 13, 2006 7:09 PM

Answers

  • You can change the certificate used to sign the application from the project
    properties screen. just go to the signing tab, and in the ClickOnce manifest
    section Click one create test certificate button.
    • Marked as answer by RobinDotNet Tuesday, June 8, 2010 6:04 PM
    Thursday, November 23, 2006 7:38 AM

All replies

  • You can change the certificate used to sign the application from the project
    properties screen. just go to the signing tab, and in the ClickOnce manifest
    section Click one create test certificate button.
    • Marked as answer by RobinDotNet Tuesday, June 8, 2010 6:04 PM
    Thursday, November 23, 2006 7:38 AM
  • Don't do that! Your users will have to uninstall and reinstall. Instead, see this: http://support.microsoft.com/default.aspx/kb/925521

     

    David

    Saturday, October 18, 2008 12:38 AM
  • Thanks Y_Not,

    it is working with me.
    Sunday, October 4, 2009 11:21 AM
  • I'm not sure what is not working for you. Can you be more specific?

    RobinDotNet
    Click here to visit my ClickOnce blog!
    Microsoft MVP, Client App Dev
    Sunday, October 4, 2009 6:52 PM
  • I said it is working with me.


     I face that problem "SignTool error - Certificate” and when I use the steps in given by Y_Not_, it is solved. I hope it is clear.

    Monday, October 5, 2009 3:40 AM
  • Gotcha. Thanks, and glad it helped.

    RobinDotNet


    Click here to visit my ClickOnce blog!
    Microsoft MVP, Client App Dev
    Monday, October 5, 2009 3:41 AM
  • Thank you so much Y_NOT it works great!!!!

    I love you... make me a child...

    Tuesday, June 8, 2010 8:25 AM
  •  

    Just to clarify about the post in this thread saying you haev to uninstall and reinstall if you create a new certificate: This is true if you are targeting .NET 2.0 and you have any Vista machines running that don't have .NET 3.5 installed, or you are doing manual updates. They fixed this problem in .NET 3.5 for automatic updates, and it is fixed for all cases in .NET 4.0. Here's an article explaining the cases and how to work around the problem if you're unlucky enough to have it:

    http://msdn.microsoft.com/en-us/library/ff369721.aspx

    RobinDotNet


    Click here to visit my ClickOnce blog!
    Microsoft MVP, Client App Dev
    Tuesday, June 8, 2010 6:06 PM