OS = Windows 2003 Server
Wix Version = 3.0.4519
Certificate does not install.
MSI (s) (C4:08) [15:50:50:560]: Invoking remote custom action. DLL: C:\WINNT\Installer\MSI13A.tmp, Entrypoint: InstallCertificates
InstallCertificates: Error 0x80070057: Failed to open PFX file.
InstallCertificates: Error 0x80070057: Failed to get SHA1 hash of certificate.
InstallCertificates: Error 0x80070057: Failed to resolve certificate: ID_IDSAPICert
This worked in Wix 2.0 and we recently converted to Wix 3.0. The source file and certificate have not changed.
Repro available at:
\a-iaelli-dev\share\Cert_Installer
I am also seeing this behavior.
C:\
Microsoft Windows [Version 5.2.3790]
XP 64-bit
This is related to the fix for bug #1930640
Here is the log file output:
MSI (s) (C8!90) [07:17:41:352]: Doing action: AddMachineCertificate
MSI (s) (C8!90) [07:17:41:352]: Note: 1: 2205 2: 3: ActionText
Action 7:17:41: AddMachineCertificate.
Action start 7:17:41: AddMachineCertificate.
AddMachineCertificate:
Action ended 7:17:41: AddMachineCertificate. Return value 1.
InstallCertificates: Error 0x80070057: Failed to open PFX file.
InstallCertificates: Error 0x80070057: Failed to get SHA1 hash of certificate.
InstallCertificates: Error 0x80070057: Failed to resolve certificate: dr.client.certificate
Action ended 7:17:41: InstallCertificates. Return value 3.
Since the error code returned is "invalid argument", I'm wondering if the PKCS12_NO_PERSIST_KEY flag is valid in pre-Vista OS versions. Here's a thread that may suggest that flag is not supported on XP:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=2631214&SiteID=1
I'm going to isolate the issue with a test app and will post code to demonstrate.
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 15 days (the time period specified by
the administrator of this Tracker).