Microsoft KB Archive/925521

= You receive an error message when you try to update a Visual Studio 2005 ClickOnce application after the certificate that was used to sign the installation expires =

Article ID: 925521

Article Last Modified on 1/13/2007

-

APPLIES TO


 * Microsoft Visual Studio 2005 Standard Edition
 * Microsoft Visual Studio 2005 Professional Edition
 * Microsoft Visual Studio 2005 Express Edition

-



SYMPTOMS
When you try to update a Microsoft Visual Studio 2005 ClickOnce application after the certificate that you used to sign the installation expires, you receive the following error message:

The deployment identity does not match the subscription.



CAUSE
This problem occurs because you must sign all ClickOnce deployments by using a digital certificate. You cannot use an expired certificate to sign a ClickOnce application. To deploy an update to an application that has an expired certificate, you must assign the application a new certificate. When the new certificate does not match the original certificate, you receive the error message that is mentioned in the &quot;Symptoms&quot; section.



WORKAROUND
To work around this problem, use one of the following methods.

Method 1
Uninstall the ClickOnce application that you signed by using the expired certificate. Then, reinstall the updated ClickOnce application that uses the new certificate.

Method 2
Create a command-line assembly that updates the certificate. To do this, follow these steps.

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure. However, they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.  In Visual Studio 2005, click New on the File menu, and then click Project. Click Visual C++, click Win32 Console Application, type RenewCert in the Name box, and then click OK. In the Win32 Application Wizard dialog box, click Finish.  In the RenewCert.cpp file, replace the existing code with the following code:
 * 1) include &quot;stdafx.h&quot;

void ReadPFXFile(LPCWSTR fileName, CRYPT_DATA_BLOB *pPFX)

{

HANDLE hCertFile = NULL;

DWORD cbRead = 0;

DWORD dwFileSize = 0, dwFileSizeHi = 0;

hCertFile = CreateFile(fileName, GENERIC_READ, FILE_SHARE_READ, NULL, OPEN_EXISTING, 0, NULL);

dwFileSize = GetFileSize(hCertFile, &dwFileSizeHi);

pPFX->pbData = (BYTE *) CryptMemAlloc(dwFileSize*sizeof(BYTE));

pPFX->cbData = dwFileSize;

ReadFile(hCertFile, pPFX->pbData, pPFX->cbData, &cbRead, NULL);

CloseHandle(hCertFile);

}

void GetPrivateKey(CRYPT_DATA_BLOB pPFX, LPCWSTR szPassword, HCRYPTPROV *hCPContext)

{

HCERTSTORE hCertStore = NULL;

PCCERT_CONTEXT hCertContext = NULL;

DWORD dwKeySpec = AT_SIGNATURE;

BOOL bFreeCertKey = TRUE;

hCertStore = PFXImportCertStore(&pPFX, szPassword, CRYPT_EXPORTABLE);

hCertContext = CertEnumCertificatesInStore(hCertStore, NULL);

CryptAcquireCertificatePrivateKey(hCertContext, 0, NULL, hCPContext, &dwKeySpec, &bFreeCertKey);

CertCloseStore(hCertStore, CERT_CLOSE_STORE_FORCE_FLAG);

}

void PrintContainerName(HCRYPTPROV hCPContext)

{

DWORD containerNameLen = 0;

CHAR *szContainerName = NULL;

CryptGetProvParam(hCPContext, PP_CONTAINER, NULL, &containerNameLen, 0);

szContainerName = (CHAR *)CryptMemAlloc(sizeof(BYTE)*containerNameLen);

CryptGetProvParam(hCPContext, PP_CONTAINER, (BYTE *)szContainerName, &containerNameLen, 0);

printf(&quot;This certificate's container name is: %s&quot;, szContainerName);

}

void MakeNewCert(HCRYPTPROV hCPContext, LPCWSTR szCertName, LPCWSTR szPassword, CRYPT_DATA_BLOB *pPFX)

{

CERT_NAME_BLOB certNameBlob = {0,NULL};

PCCERT_CONTEXT hCertContext = NULL;

SYSTEMTIME certExpireDate;

HCERTSTORE hTempStore = NULL;

CertStrToName(X509_ASN_ENCODING | PKCS_7_ASN_ENCODING, szCertName, CERT_OID_NAME_STR, NULL, NULL, &certNameBlob.cbData, NULL);

certNameBlob.pbData = (BYTE *)CryptMemAlloc(sizeof(BYTE)*certNameBlob.cbData);

CertStrToName(X509_ASN_ENCODING | PKCS_7_ASN_ENCODING, szCertName, CERT_OID_NAME_STR, NULL, certNameBlob.pbData, &certNameBlob.cbData, NULL);

GetSystemTime(&certExpireDate);

certExpireDate.wYear += 5;

hCertContext = CertCreateSelfSignCertificate(hCPContext, &certNameBlob, 0, NULL, NULL, NULL, &certExpireDate, NULL);

hTempStore = CertOpenStore(CERT_STORE_PROV_MEMORY, 0, NULL, CERT_STORE_CREATE_NEW_FLAG, 0);

CertAddCertificateContextToStore(hTempStore, hCertContext, CERT_STORE_ADD_NEW, NULL);

PFXExportCertStoreEx(hTempStore, pPFX, szPassword, NULL, EXPORT_PRIVATE_KEYS);

pPFX->pbData = (BYTE *)CryptMemAlloc(sizeof(BYTE)*pPFX->cbData);

PFXExportCertStoreEx(hTempStore, pPFX, szPassword, NULL, EXPORT_PRIVATE_KEYS);

CryptMemFree(certNameBlob.pbData);

CertCloseStore(hTempStore, CERT_CLOSE_STORE_FORCE_FLAG);

CertFreeCertificateContext(hCertContext);

}

void WritePFX(CRYPT_DATA_BLOB pPFX, LPCWSTR szOutputFile)

{

HANDLE hOutputFile = NULL;

DWORD cbWritten = 0;

hOutputFile = CreateFile(szOutputFile, GENERIC_READ | GENERIC_WRITE, 0, NULL, CREATE_ALWAYS, FILE_FLAG_SEQUENTIAL_SCAN, NULL);

WriteFile(hOutputFile, pPFX.pbData, pPFX.cbData, &cbWritten, NULL);

CloseHandle(hOutputFile);

}

int _tmain(int argc, _TCHAR* argv[])

{

LPCWSTR szCertFileName = NULL;

CRYPT_DATA_BLOB pPFX;

LPCWSTR szPassword = NULL;

HCRYPTPROV hCPContext = NULL;

LPCWSTR szCertName = L&quot;CN=NewCert&quot;;

CRYPT_DATA_BLOB pPfxOutputBlob = {0,NULL};

LPCWSTR szOutFile = NULL;

// Parse the command line.

if(argc == 1)

{

printf(&quot;renewcert  [optional] \n&quot;);

printf(&quot;Example: renewcert oldcert.pfx newcert.pfx \&quot;CN=MyNewCert\&quot; MySuperSecretPassword&quot;);

return 0;

}

if(argc >= 2)

szCertFileName = argv[1];

if(argc >= 5)

szPassword = argv[4];

// Uncomment this block to add and as parameters

// NOTE: must be of format &quot;CN= &quot;

if(argc >= 3)

szOutFile = argv[2];

if(argc >= 4)

szCertName = argv[3];

ReadPFXFile(szCertFileName, &pPFX);

GetPrivateKey(pPFX, szPassword, &hCPContext);

//PrintContainerName(hCPContext);

// Uncomment this section to make a new PFX rather than just printing the container name.

// Make sure you also uncomment the command line parameter section above.

MakeNewCert(hCPContext, szCertName, szPassword, &pPfxOutputBlob);

WritePFX(pPfxOutputBlob, szOutFile);

// Clean up.

CryptReleaseContext(hCPContext, 0);

CryptMemFree(pPfxOutputBlob.pbData);

CryptMemFree(pPFX.pbData);

return 0;

}   In the stdafx.h file, replace the existing code with the following code: // stdafx.h : include file for standard system include files,

// or project specific include files that are used frequently, but

// are changed infrequently.

//


 * 1) pragma once


 * 1) define WIN32_LEAN_AND_MEAN                    // Exclude rarely used material from Windows headers.


 * 1) include 


 * 1) include 


 * 1) include <windows.h>

</li> On the Project menu, click Properties to open the property pages for this project.</li> Expand the Linker node, and then click Input.</li> Click in the blank window to the right of Additional Dependencies, and then click the ellipsis button (...) to open to the Additional Dependencies dialog box.</li> In the blank window, type Crypt32.lib, and then click OK.</li> Click Apply, and then click OK to close the property pages.</li> On the Build menu, click Build Solution.</li>  After the solution is built, excute the following command to update the certificate: renewcert <OldCertificate>.pfx <NewCertificate>.pfx \&quot;CN=<NewCertificateName>\&quot; <Password> Note is a placeholder for the old certificate,   is a placeholder for the new certificate,   is a placeholder for the name of the new certificate, and   is a placeholder for the password. </li></ol>
 * 1) include <wincrypt.h>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

Steps to reproduce this problem
<ol> Start Visual Studio 2005.</li> On the File menu, click New, and then click Project.</li> Click Visual C#, click Windows Application, type WindowsApplication1 in the Name box, and then click OK.</li> In Solution Explorer, right-click WindowsApplication1, and then click Properties.</li> Click Signing, and then assign a certificate that expires soon.</li> In Solution Explorer, right-click WindowsApplication1, and then click Publish. The Publish wizard starts.</li> On the Where do you want to publish the application? page, type a valid URL, and then click Next. Use the following format for the URL:

http:// /

</li> On the Will the application be available offline? page, click the appropriate option.

Notes <ul> If you want to let the user run the application when the user is disconnected from the network, click Yes, this application will be available online or offline. The wizard creates a shortcut for the application on the Start menu.</li> <li>If you want to run the application directly from the publish location, click No, this application is only available online. The wizard does not create a shortcut on the Start menu.</li></ul> </li> <li>Click Next to continue.</li> <li>Click Finish to publish the application.</li> <li>Install the ClickOnce application from the http:// / /publish.htm URL.</li> <li>After the certificate expires, repeat steps 6 to 10 to republish the application.</li> <li>Try to install the ClickOnce application update from the http:// / /publish.htm URL.</li></ol>

Additional query words: ClickOnce certificate

Keywords: kbtshoot kberrmsg kbbug kbprb KB925521

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.