Publish Failed Error

I am using VB.NET, trying to publish changes and I am receiving this error

Error 94  -  SignTool reported an error 'Failed to sign .\bin\STS System.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\STS System.publish\\setup.exe


Can anyone tell me what this means?  I have a full version, licensed and have published 27 other versions of the application that I have built
chellertAsked:
Who is Participating?
 
EE_AutoDeleterCommented:
chellert,
Because you have presented a solution to your own problem which may be helpful to future searches, this question is now PAQed and your points have been refunded.

EE_AutoDeleter
0
 
chellertAuthor Commented:
Found the issue.  The ClickOnce Manifest signature key had expired.
0
 
ChristopherSmithCommented:
I'm trying to find a solution that allows me to continue publishing updates to my application without causing a problem with the existing user base.  My understanding is if the certificate expiration date isn't updated a certain way, clients will not only be unable to update to the latest version but may be unable to run the previous version which could cause work stoppage.
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
ChristopherSmithCommented:
I finally managed to resolve this problem such that my users would not have to uninstall and reinstall the application.  On the Signing tab in my project properties, my certificate Issued To and Issued By myself (MYDOMAIN\myusername) showed that it expired on 9/27/2007 so I was getting the error reported in this thread.  I downloaded a file named renewcert.exe from http://www.may.be/renewcert  and copied the file into my application folder which contained my certificate file which in my case was named Shell_TemporaryKey.pfx.  As a precaution, I made a copy of the pfx file in another folder for safety.  Then, from a command prompt and from that same application folder, I entered the following command:

renewcert Shell_TemporaryKey.pfx Shell_TemporaryKey.pfx CN=MYDOMAIN\myusername

Note that I did not specify a password originally so I didn't include any password on the command line.  Next, I went back to the Signing tab and chose the Select From File option to choose the updated Shell_TemporaryKey.pfx file and the Issued To and Issued By names were the same as before and the expiration date was now 5 years into the future or 10/12/2012.  After that, I was able to publish again successfully and my users were able to update the application normally without getting the error "The deployment identity does not match the subscription" and without having to uninstall / reinstall.
0
 
shieldguyCommented:
When i try to execute the renewcert  I received the error the system cannont execute the specified program
0
 
ChristopherSmithCommented:
I'm presuming that you downloaded the renewcert.exe from the website shown and that you followed my instructions.  Perhaps it is an operating system difference?  I was working on a Windows XP Pro system.  
0
 
shieldguyCommented:
It is windows xp professional, I am executing the file using the dos command prompt which is availabel in the winxp

Or sould I do it using some other way ???
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.