SignTool error - Certificate is not valid for signing 0x80880253


  • 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.

    -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?



    Friday, October 13, 2006 7:09 PM


  • 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.
    Thursday, November 23, 2006 7:38 AM

All replies