SECREPAIR: CryptAcquireContext: Could not create the default key container

classic Classic list List threaded Threaded
57 messages Options
123
Reply | Threaded
Open this post in threaded view
|

SECREPAIR: CryptAcquireContext: Could not create the default key container

Neil Sleightholm
Has anyone seen the issue below?

We are deploying MSIs via a remote PowerShell script and last week it suddenly started failing with this error. We have tracked the problem down to Hotfix 2918614 (released 12 Aug 2014) but were curious if anyone else is experiencing the problem or know what is causing it.

MSI (s) (04:A0) [11:10:07:189]: SECREPAIR: Hash Database: C:\Windows\Installer\SourceHash{0853D2F3-3147-45BE-A153-23E5915150B3}
MSI (s) (04:A0) [11:10:07:189]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (04:A0) [11:10:07:221]: Note: 1: 2262 2: SourceHash 3: -2147287038
MSI (s) (04:A0) [11:10:07:314]: SECREPAIR: New Hash Database creation complete.
MSI (s) (04:A0) [11:10:07:938]: SECREPAIR: CryptAcquireContext: Could not create the default key container
MSI (s) (04:A0) [11:10:07:938]: SECREPAIR: Crypt Provider not initialized. Error:-2146892987
MSI (s) (04:A0) [11:10:07:938]: SECUREREPAIR: Failed to CreateContentHash of the file: xxxxxxxxxx.msi: for computing its hash. Error: -2146892987
MSI (s) (04:A0) [11:10:07:938]: SECREPAIR: Failed to create hash for the install source files
MSI (s) (04:A0) [11:10:07:938]: Note: 1: 2262 2: SourceHash 3: -2147287038
MSI (s) (04:A0) [11:10:07:938]: SECUREREPAIR: SecureRepair Failed. Error code: 80090345F56034B8
Action start 11:10:07: ProcessComponents.
MSI (s) (04:A0) [11:10:07:938]:
The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation.

Neil

Neil Sleightholm
X2 Systems Limited
[hidden email]<mailto:[hidden email]>

------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: SECREPAIR: CryptAcquireContext: Could not create the default key container

Phill Hogland
Reply | Threaded
Open this post in threaded view
|

Re: SECREPAIR: CryptAcquireContext: Could not create the default key container

Neil Sleightholm
Thanks, seen that one and this one https://community.logos.com/forums/p/87997/617278.aspx. Both look similar.

Neil

-----Original Message-----
From: Phill Hogland [mailto:[hidden email]]
Sent: 18 August 2014 20:13
To: [hidden email]
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb2918614-causing-overlapped-i-o-operation-progress-errors.html




--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7596414p7596418.html
Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
moc
Reply | Threaded
Open this post in threaded view
|

Re: SECREPAIR: CryptAcquireContext: Could not create the default key container

moc
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
Our customers with the issue are usually running some sort of antivirus
and we presumed it's some kind of conflict with that but we've had no
success with disabling Anti-virus with msconfig. However removing the kb
update has fixed it for at least one customer. I'm hoping to find a
recipe to replicate it but we're not there yet.

I'm hoping MS find a fix an re-issue the update.:-)

On 18/08/2014 22:54, Neil Sleightholm wrote:

> Thanks, seen that one and this one https://community.logos.com/forums/p/87997/617278.aspx. Both look similar.
>
> Neil
>
> -----Original Message-----
> From: Phill Hogland [mailto:[hidden email]]
> Sent: 18 August 2014 20:13
> To: [hidden email]
> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container
>
> FYI
> http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb2918614-causing-overlapped-i-o-operation-progress-errors.html
>
>
>
>
> --
> View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7596414p7596418.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> ------------------------------------------------------------------------------
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
moc
Reply | Threaded
Open this post in threaded view
|

Re: SECREPAIR: CryptAcquireContext: Could not create the default key container

moc
We get a slightly different error out of CryptAcquireContext, ours
follow this pattern:
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: Hash Database:
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file
already exists. Deleting it.
MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038
MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation
complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running
CryptAcquireContext
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt Provider not
initialized. Error:0
MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: A general error running
CryptAcquireContext
MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: Crypt Provider not
initialized. Error:0
MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: A general error running
CryptAcquireContext
MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt Provider not
initialized. Error:0
MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: A general error running
CryptAcquireContext
MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: Crypt Provider not
initialized. Error:0
MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: A general error running
CryptAcquireContext
MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt Provider not
initialized. Error:997
MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: Failed to
CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG: for computing its
hash. Error: 997
MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Failed to create hash for the
install source files
MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
code: 3e5F6C634B8

Error 997 being the Windows error 'Overlapped I/O operation is in
progress.'

On 26/08/2014 11:05, Matt O'Connell wrote:

> We've started seeing this a lot recently.
> Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
> Our customers with the issue are usually running some sort of
> antivirus and we presumed it's some kind of conflict with that but
> we've had no success with disabling Anti-virus with msconfig. However
> removing the kb update has fixed it for at least one customer. I'm
> hoping to find a recipe to replicate it but we're not there yet.
>
> I'm hoping MS find a fix an re-issue the update.:-)
>
> On 18/08/2014 22:54, Neil Sleightholm wrote:
>> Thanks, seen that one and this one
>> https://community.logos.com/forums/p/87997/617278.aspx. Both look
>> similar.
>>
>> Neil
>>
>> -----Original Message-----
>> From: Phill Hogland [mailto:[hidden email]]
>> Sent: 18 August 2014 20:13
>> To: [hidden email]
>> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
>> create the default key container
>>
>> FYI
>> http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb2918614-causing-overlapped-i-o-operation-progress-errors.html 
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7596414p7596418.html
>> Sent from the wix-users mailing list archive at Nabble.com.
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> WiX-users mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> WiX-users mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>


------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: SECREPAIR: CryptAcquireContext: Could not create the default key container

Rob Mensching-7
How are you installing the MSIs? Just double-click the .MSI directly, as part of a Bundle, some other mechanism?

_______________________________________________________________
 FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

-----Original Message-----
From: Matt O'Connell [mailto:[hidden email]]
Sent: Tuesday, August 26, 2014 3:35 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

We get a slightly different error out of CryptAcquireContext, ours follow this pattern:
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: Hash Database:
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt Provider not initialized. Error:997 MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: Failed to CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG: for computing its hash. Error: 997 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Failed to create hash for the install source files MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
code: 3e5F6C634B8

Error 997 being the Windows error 'Overlapped I/O operation is in progress.'

On 26/08/2014 11:05, Matt O'Connell wrote:

> We've started seeing this a lot recently.
> Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
> Our customers with the issue are usually running some sort of
> antivirus and we presumed it's some kind of conflict with that but
> we've had no success with disabling Anti-virus with msconfig. However
> removing the kb update has fixed it for at least one customer. I'm
> hoping to find a recipe to replicate it but we're not there yet.
>
> I'm hoping MS find a fix an re-issue the update.:-)
>
> On 18/08/2014 22:54, Neil Sleightholm wrote:
>> Thanks, seen that one and this one
>> https://community.logos.com/forums/p/87997/617278.aspx. Both look
>> similar.
>>
>> Neil
>>
>> -----Original Message-----
>> From: Phill Hogland [mailto:[hidden email]]
>> Sent: 18 August 2014 20:13
>> To: [hidden email]
>> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
>> create the default key container
>>
>> FYI
>> http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb29186
>> 14-causing-overlapped-i-o-operation-progress-errors.html
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPA
>> IR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7
>> 596414p7596418.html Sent from the wix-users mailing list archive at
>> Nabble.com.
>>
>> ---------------------------------------------------------------------
>> ---------
>>
>> _______________________________________________
>> WiX-users mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>> ---------------------------------------------------------------------
>> ---------
>>
>> _______________________________________________
>> WiX-users mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>


------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
moc
Reply | Threaded
Open this post in threaded view
|

Re: SECREPAIR: CryptAcquireContext: Could not create the default key container

moc
Custom Autorun/Setup.exe (elevating) that's been working fine for years,
OR on the CMD line line msiexec /i path to msi (where it will prompt to
elevate as well).
On 26/08/2014 16:15, Rob Mensching wrote:

> How are you installing the MSIs? Just double-click the .MSI directly, as part of a Bundle, some other mechanism?
>
> _______________________________________________________________
>   FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/
>
> -----Original Message-----
> From: Matt O'Connell [mailto:[hidden email]]
> Sent: Tuesday, August 26, 2014 3:35 AM
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container
>
> We get a slightly different error out of CryptAcquireContext, ours follow this pattern:
> MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: Hash Database:
> C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
> MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file already exists. Deleting it.
> MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation complete.
> MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt Provider not initialized. Error:997 MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: Failed to CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG: for computing its hash. Error: 997 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Failed to create hash for the install source files MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
> code: 3e5F6C634B8
>
> Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
>
> On 26/08/2014 11:05, Matt O'Connell wrote:
>> We've started seeing this a lot recently.
>> Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
>> Our customers with the issue are usually running some sort of
>> antivirus and we presumed it's some kind of conflict with that but
>> we've had no success with disabling Anti-virus with msconfig. However
>> removing the kb update has fixed it for at least one customer. I'm
>> hoping to find a recipe to replicate it but we're not there yet.
>>
>> I'm hoping MS find a fix an re-issue the update.:-)
>>
>> On 18/08/2014 22:54, Neil Sleightholm wrote:
>>> Thanks, seen that one and this one
>>> https://community.logos.com/forums/p/87997/617278.aspx. Both look
>>> similar.
>>>
>>> Neil
>>>
>>> -----Original Message-----
>>> From: Phill Hogland [mailto:[hidden email]]
>>> Sent: 18 August 2014 20:13
>>> To: [hidden email]
>>> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
>>> create the default key container
>>>
>>> FYI
>>> http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb29186
>>> 14-causing-overlapped-i-o-operation-progress-errors.html
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPA
>>> IR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7
>>> 596414p7596418.html Sent from the wix-users mailing list archive at
>>> Nabble.com.
>>>
>>> ---------------------------------------------------------------------
>>> ---------
>>>
>>> _______________________________________________
>>> WiX-users mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>>
>>> ---------------------------------------------------------------------
>>> ---------
>>>
>>> _______________________________________________
>>> WiX-users mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users



------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: SECREPAIR: CryptAcquireContext: Could not create the default key container

Rob Mensching-7
Okay. That points to the fix having issues and not being isolated to Burn. Which, fortunately or unfortunately, means Microsoft probably needs to fix the fix.

_______________________________________________________________
 FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

-----Original Message-----
From: Matt O'Connell [mailto:[hidden email]]
Sent: Tuesday, August 26, 2014 9:02 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Custom Autorun/Setup.exe (elevating) that's been working fine for years, OR on the CMD line line msiexec /i path to msi (where it will prompt to elevate as well).
On 26/08/2014 16:15, Rob Mensching wrote:

> How are you installing the MSIs? Just double-click the .MSI directly, as part of a Bundle, some other mechanism?
>
> _______________________________________________________________
>   FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/
>
> -----Original Message-----
> From: Matt O'Connell [mailto:[hidden email]]
> Sent: Tuesday, August 26, 2014 3:35 AM
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container
>
> We get a slightly different error out of CryptAcquireContext, ours follow this pattern:
> MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: Hash Database:
> C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
> MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file already exists. Deleting it.
> MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation complete.
> MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt Provider not initialized. Error:997 MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: Failed to CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG: for computing its hash. Error: 997 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Failed to create hash for the install source files MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
> code: 3e5F6C634B8
>
> Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
>
> On 26/08/2014 11:05, Matt O'Connell wrote:
>> We've started seeing this a lot recently.
>> Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
>> Our customers with the issue are usually running some sort of
>> antivirus and we presumed it's some kind of conflict with that but
>> we've had no success with disabling Anti-virus with msconfig. However
>> removing the kb update has fixed it for at least one customer. I'm
>> hoping to find a recipe to replicate it but we're not there yet.
>>
>> I'm hoping MS find a fix an re-issue the update.:-)
>>
>> On 18/08/2014 22:54, Neil Sleightholm wrote:
>>> Thanks, seen that one and this one
>>> https://community.logos.com/forums/p/87997/617278.aspx. Both look
>>> similar.
>>>
>>> Neil
>>>
>>> -----Original Message-----
>>> From: Phill Hogland [mailto:[hidden email]]
>>> Sent: 18 August 2014 20:13
>>> To: [hidden email]
>>> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
>>> create the default key container
>>>
>>> FYI
>>> http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb29186
>>> 14-causing-overlapped-i-o-operation-progress-errors.html
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPA
>>> IR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7
>>> 596414p7596418.html Sent from the wix-users mailing list archive at
>>> Nabble.com.
>>>
>>> ---------------------------------------------------------------------
>>> ---------
>>>
>>> _______________________________________________
>>> WiX-users mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>>
>>> ---------------------------------------------------------------------
>>> ---------
>>>
>>> _______________________________________________
>>> WiX-users mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users



------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: SECREPAIR: CryptAcquireContext: Could not create the default key container

Keith.Douglas
Has anyone with a support contract or the like with Microsoft asked about this? I've pre-emptively raised a concern with some of my colleagues but people don't know what to make of a bunch of isolated forum posts/this list's thread.




Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
[hidden email]
Telephone | Téléphone 613-854-5589
Facsimile | Télécopieur 613-951-4674
Government of Canada | Gouvernement du Canada


-----Original Message-----
From: Rob Mensching [mailto:[hidden email]]
Sent: August-26-14 12:45 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Okay. That points to the fix having issues and not being isolated to Burn. Which, fortunately or unfortunately, means Microsoft probably needs to fix the fix.

_______________________________________________________________
 FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

-----Original Message-----
From: Matt O'Connell [mailto:[hidden email]]
Sent: Tuesday, August 26, 2014 9:02 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Custom Autorun/Setup.exe (elevating) that's been working fine for years, OR on the CMD line line msiexec /i path to msi (where it will prompt to elevate as well).
On 26/08/2014 16:15, Rob Mensching wrote:

> How are you installing the MSIs? Just double-click the .MSI directly, as part of a Bundle, some other mechanism?
>
> _______________________________________________________________
>   FireGiant  |  Dedicated support for the WiX toolset  |  
> http://www.firegiant.com/
>
> -----Original Message-----
> From: Matt O'Connell [mailto:[hidden email]]
> Sent: Tuesday, August 26, 2014 3:35 AM
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
> create the default key container
>
> We get a slightly different error out of CryptAcquireContext, ours follow this pattern:
> MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: Hash Database:
> C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
> MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file already exists. Deleting it.
> MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation complete.
> MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt Provider not initialized. Error:997 MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: Failed to CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG: for computing its hash. Err!
 or: 997 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Failed to create hash for the install source files MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error

> code: 3e5F6C634B8
>
> Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
>
> On 26/08/2014 11:05, Matt O'Connell wrote:
>> We've started seeing this a lot recently.
>> Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
>> Our customers with the issue are usually running some sort of
>> antivirus and we presumed it's some kind of conflict with that but
>> we've had no success with disabling Anti-virus with msconfig. However
>> removing the kb update has fixed it for at least one customer. I'm
>> hoping to find a recipe to replicate it but we're not there yet.
>>
>> I'm hoping MS find a fix an re-issue the update.:-)
>>
>> On 18/08/2014 22:54, Neil Sleightholm wrote:
>>> Thanks, seen that one and this one
>>> https://community.logos.com/forums/p/87997/617278.aspx. Both look
>>> similar.
>>>
>>> Neil
>>>
>>> -----Original Message-----
>>> From: Phill Hogland [mailto:[hidden email]]
>>> Sent: 18 August 2014 20:13
>>> To: [hidden email]
>>> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
>>> create the default key container
>>>
>>> FYI
>>> http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb2918
>>> 6 14-causing-overlapped-i-o-operation-progress-errors.html
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREP
>>> A
>>> IR-CryptAcquireContext-Could-not-create-the-default-key-container-tp
>>> 7 596414p7596418.html Sent from the wix-users mailing list archive
>>> at Nabble.com.
>>>
>>> --------------------------------------------------------------------
>>> -
>>> ---------
>>>
>>> _______________________________________________
>>> WiX-users mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>>
>>> --------------------------------------------------------------------
>>> -
>>> ---------
>>>
>>> _______________________________________________
>>> WiX-users mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> ----------------------------------------------------------------------
> --------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> ----------------------------------------------------------------------
> --------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users



------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: SECREPAIR: CryptAcquireContext: Could not create the default key container

John Cooper-2
We have a support contract, and I have forwarded this thread to my manager as it is of some concern, although we haven't seen this yet.  If it hits us, we'll definitely be looking into it.  Meanwhile, I'll politic for further investigation.

--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext:  431050 |[hidden email]



-----Original Message-----
From: [hidden email] [mailto:[hidden email]]
Sent: Tuesday, August 26, 2014 2:52 PM
To: [hidden email]
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Has anyone with a support contract or the like with Microsoft asked about this? I've pre-emptively raised a concern with some of my colleagues but people don't know what to make of a bunch of isolated forum posts/this list's thread.




Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 [hidden email] Telephone | Téléphone 613-854-5589 Facsimile | Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada


-----Original Message-----
From: Rob Mensching [mailto:[hidden email]]
Sent: August-26-14 12:45 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Okay. That points to the fix having issues and not being isolated to Burn. Which, fortunately or unfortunately, means Microsoft probably needs to fix the fix.

_______________________________________________________________
 FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

-----Original Message-----
From: Matt O'Connell [mailto:[hidden email]]
Sent: Tuesday, August 26, 2014 9:02 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Custom Autorun/Setup.exe (elevating) that's been working fine for years, OR on the CMD line line msiexec /i path to msi (where it will prompt to elevate as well).
On 26/08/2014 16:15, Rob Mensching wrote:

> How are you installing the MSIs? Just double-click the .MSI directly, as part of a Bundle, some other mechanism?
>
> _______________________________________________________________
>   FireGiant  |  Dedicated support for the WiX toolset  |
> http://www.firegiant.com/
>
> -----Original Message-----
> From: Matt O'Connell [mailto:[hidden email]]
> Sent: Tuesday, August 26, 2014 3:35 AM
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
> create the default key container
>
> We get a slightly different error out of CryptAcquireContext, ours follow this pattern:
> MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: Hash Database:
> C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
> MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file already exists. Deleting it.
> MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation complete.
> MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt Provider not initialized. Error:997 MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: Failed to CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG: for computing its hash. Err!
 or: 997 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Failed to create hash for the install source files MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error

> code: 3e5F6C634B8
>
> Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
>
> On 26/08/2014 11:05, Matt O'Connell wrote:
>> We've started seeing this a lot recently.
>> Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
>> Our customers with the issue are usually running some sort of
>> antivirus and we presumed it's some kind of conflict with that but
>> we've had no success with disabling Anti-virus with msconfig. However
>> removing the kb update has fixed it for at least one customer. I'm
>> hoping to find a recipe to replicate it but we're not there yet.
>>
>> I'm hoping MS find a fix an re-issue the update.:-)
>>
>> On 18/08/2014 22:54, Neil Sleightholm wrote:
>>> Thanks, seen that one and this one
>>> https://community.logos.com/forums/p/87997/617278.aspx. Both look
>>> similar.
>>>
>>> Neil
>>>
>>> -----Original Message-----
>>> From: Phill Hogland [mailto:[hidden email]]
>>> Sent: 18 August 2014 20:13
>>> To: [hidden email]
>>> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
>>> create the default key container
>>>
>>> FYI
>>> http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb2918
>>> 6 14-causing-overlapped-i-o-operation-progress-errors.html
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREP
>>> A
>>> IR-CryptAcquireContext-Could-not-create-the-default-key-container-tp
>>> 7 596414p7596418.html Sent from the wix-users mailing list archive
>>> at Nabble.com.
>>>
>>> --------------------------------------------------------------------
>>> -
>>> ---------
>>>
>>> _______________________________________________
>>> WiX-users mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>>
>>> --------------------------------------------------------------------
>>> -
>>> ---------
>>>
>>> _______________________________________________
>>> WiX-users mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> ----------------------------------------------------------------------
> --------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> ----------------------------------------------------------------------
> --------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users



------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.


------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: SECREPAIR: CryptAcquireContext: Could not create the default key container

Rob Mensching-7
FWIW, we haven't seen this with any FireGiant customers yet. That's a large part of why I'm at a loss.

However, we have been hearing stories of other issues in the last couple batches of updates from Microsoft. Quality control may have slipped up there a bit recently.
_______________________________________________________________
 FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

-----Original Message-----
From: John Cooper [mailto:[hidden email]]
Sent: Tuesday, August 26, 2014 1:10 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

We have a support contract, and I have forwarded this thread to my manager as it is of some concern, although we haven't seen this yet.  If it hits us, we'll definitely be looking into it.  Meanwhile, I'll politic for further investigation.

--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext:  431050 |[hidden email]



-----Original Message-----
From: [hidden email] [mailto:[hidden email]]
Sent: Tuesday, August 26, 2014 2:52 PM
To: [hidden email]
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Has anyone with a support contract or the like with Microsoft asked about this? I've pre-emptively raised a concern with some of my colleagues but people don't know what to make of a bunch of isolated forum posts/this list's thread.




Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 [hidden email] Telephone | Téléphone 613-854-5589 Facsimile | Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada


-----Original Message-----
From: Rob Mensching [mailto:[hidden email]]
Sent: August-26-14 12:45 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Okay. That points to the fix having issues and not being isolated to Burn. Which, fortunately or unfortunately, means Microsoft probably needs to fix the fix.

_______________________________________________________________
 FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

-----Original Message-----
From: Matt O'Connell [mailto:[hidden email]]
Sent: Tuesday, August 26, 2014 9:02 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Custom Autorun/Setup.exe (elevating) that's been working fine for years, OR on the CMD line line msiexec /i path to msi (where it will prompt to elevate as well).
On 26/08/2014 16:15, Rob Mensching wrote:

> How are you installing the MSIs? Just double-click the .MSI directly, as part of a Bundle, some other mechanism?
>
> _______________________________________________________________
>   FireGiant  |  Dedicated support for the WiX toolset  |
> http://www.firegiant.com/
>
> -----Original Message-----
> From: Matt O'Connell [mailto:[hidden email]]
> Sent: Tuesday, August 26, 2014 3:35 AM
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
> create the default key container
>
> We get a slightly different error out of CryptAcquireContext, ours follow this pattern:
> MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: Hash Database:
> C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
> MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file already exists. Deleting it.
> MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation complete.
> MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt Provider not initialized. Error:997 MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: Failed to CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG: for computing its hash. Err!
 or: 997 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Failed to create hash for the install source files MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error

> code: 3e5F6C634B8
>
> Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
>
> On 26/08/2014 11:05, Matt O'Connell wrote:
>> We've started seeing this a lot recently.
>> Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
>> Our customers with the issue are usually running some sort of
>> antivirus and we presumed it's some kind of conflict with that but
>> we've had no success with disabling Anti-virus with msconfig. However
>> removing the kb update has fixed it for at least one customer. I'm
>> hoping to find a recipe to replicate it but we're not there yet.
>>
>> I'm hoping MS find a fix an re-issue the update.:-)
>>
>> On 18/08/2014 22:54, Neil Sleightholm wrote:
>>> Thanks, seen that one and this one
>>> https://community.logos.com/forums/p/87997/617278.aspx. Both look
>>> similar.
>>>
>>> Neil
>>>
>>> -----Original Message-----
>>> From: Phill Hogland [mailto:[hidden email]]
>>> Sent: 18 August 2014 20:13
>>> To: [hidden email]
>>> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
>>> create the default key container
>>>
>>> FYI
>>> http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb2918
>>> 6 14-causing-overlapped-i-o-operation-progress-errors.html
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREP
>>> A
>>> IR-CryptAcquireContext-Could-not-create-the-default-key-container-tp
>>> 7 596414p7596418.html Sent from the wix-users mailing list archive
>>> at Nabble.com.
>>>
>>> --------------------------------------------------------------------
>>> -
>>> ---------
>>>
>>> _______________________________________________
>>> WiX-users mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>>
>>> --------------------------------------------------------------------
>>> -
>>> ---------
>>>
>>> _______________________________________________
>>> WiX-users mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> ----------------------------------------------------------------------
> --------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> ----------------------------------------------------------------------
> --------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users



------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.


------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
moc
Reply | Threaded
Open this post in threaded view
|

Re: SECREPAIR: CryptAcquireContext: Could not create the default key container

moc
For those without a support contract, where's the most visible place to
post? msdn forums (clickonce and setup & deployment projects, I've never
found an MSI one...) or microsoft.public.platformsdk.msi newsgroup?  The
installer team blog would've been a good place but its not updated anymore..

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: SECREPAIR: CryptAcquireContext: Could not create the default key container

roberthyang
In reply to this post by Neil Sleightholm
We just started seeing a possibly-related error recently.  We have a burn bootstrapper in Wix 3.8 and among the bundle MSI's is SQL Server Compact SP2 x64 (SSCERuntime-ENU-x64.msi).  When the bootstrapper attempts to repair the application, the repair of SQL Server Compact SP2 x64 fails with "Error 1316.The specified account already exists."

An excerpt from the log is as follows :

Action start 12:09:35: PublishFeatures.
MSI (s) (D4:54) [12:09:35:006]: Doing action: PublishProduct
Action ended 12:09:35: PublishFeatures. Return value 1.
Action start 12:09:35: PublishProduct.
MSI (s) (D4:54) [12:09:35:008]: Resolving source.
MSI (s) (D4:54) [12:09:35:008]: Resolving source to launched-from source.
MSI (s) (D4:54) [12:09:35:008]: Setting launched-from source as last-used.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding SourceDir property. Its value is 'C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\'.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is 'C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\'.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}'.
MSI (s) (D4:54) [12:09:35:008]: SOURCEDIR ==> C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\
MSI (s) (D4:54) [12:09:35:008]: SOURCEDIR product ==> {D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}
MSI (s) (D4:54) [12:09:35:008]: Determining source type
MSI (s) (D4:54) [12:09:35:008]: Note: 1: 2203 2: C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi 3: -2147287038
MSI (s) (D4:54) [12:09:35:008]: Note: 1: 1316 2: C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi
MSI (s) (D4:54) [12:09:35:008]: SECREPAIR: Error determining package source type
MSI (s) (D4:54) [12:09:35:008]: SECUREREPAIR: SecureRepair Failed. Error code: 524F5C634B8
MSI (s) (D4:54) [12:09:38:487]: Product: Microsoft SQL Server Compact 3.5 SP2 x64 ENU -- Error 1316.The specified account already exists.

Repair of SQL Server Compact SP2 x64 works fine from the Control Panel and from Explorer.  I know this used to work, as I tested it earlier this year.  Here is our Wix code to include the MSI :

      <MsiPackage
        Id="SSCERuntime_x64"
        Cache="no"
        Compressed="no"
        Permanent="yes"
        Visible="yes"
        Vital="yes"
        Name="SQL Server Compact Edition\SSCERuntime-ENU-x64.msi"
        SourceFile="$(var.MSSDKBootstrapperPath)Packages\SQL Server Compact Edition\EN\SSCERuntime-ENU-x64.msi"
        DownloadUrl="http://go.microsoft.com/fwlink/?LinkID=166086"/>

I'm guessing it has to do with this :

https://technet.microsoft.com/library/security/MS14-049

I'm hoping there is a workaround.  Thanks for any advice !
-Rob
Reply | Threaded
Open this post in threaded view
|

Re: SECREPAIR: CryptAcquireContext: Could not create the default key container

Neil Sleightholm
In reply to this post by moc
I have seen that reported but I think it is slightly different. Does removing kb2918614 fix it?

-----Original Message-----
From: Matt O'Connell [mailto:[hidden email]]
Sent: 26 August 2014 11:35
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

We get a slightly different error out of CryptAcquireContext, ours follow this pattern:
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: Hash Database:
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt Provider not initialized. Error:997 MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: Failed to CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG: for computing its hash. Error: 997 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Failed to create hash for the install source files MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
code: 3e5F6C634B8

Error 997 being the Windows error 'Overlapped I/O operation is in progress.'

On 26/08/2014 11:05, Matt O'Connell wrote:

> We've started seeing this a lot recently.
> Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
> Our customers with the issue are usually running some sort of
> antivirus and we presumed it's some kind of conflict with that but
> we've had no success with disabling Anti-virus with msconfig. However
> removing the kb update has fixed it for at least one customer. I'm
> hoping to find a recipe to replicate it but we're not there yet.
>
> I'm hoping MS find a fix an re-issue the update.:-)
>
> On 18/08/2014 22:54, Neil Sleightholm wrote:
>> Thanks, seen that one and this one
>> https://community.logos.com/forums/p/87997/617278.aspx. Both look
>> similar.
>>
>> Neil
>>
>> -----Original Message-----
>> From: Phill Hogland [mailto:[hidden email]]
>> Sent: 18 August 2014 20:13
>> To: [hidden email]
>> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
>> create the default key container
>>
>> FYI
>> http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb29186
>> 14-causing-overlapped-i-o-operation-progress-errors.html
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPA
>> IR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7
>> 596414p7596418.html Sent from the wix-users mailing list archive at
>> Nabble.com.
>>
>> ---------------------------------------------------------------------
>> ---------
>>
>> _______________________________________________
>> WiX-users mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>> ---------------------------------------------------------------------
>> ---------
>>
>> _______________________________________________
>> WiX-users mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>


------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: SECREPAIR: CryptAcquireContext: Could not create the default key container

Neil Sleightholm
In reply to this post by Rob Mensching-7
I think it is somehow related to the user context it is running as, in our case we using PowerShell remoting to install the MSI (using msiexec). The bit I have never seen before are the SECREPAIR messages, these only get triggered for us when we do this remote deployment. Although it works with kb2918614 installed I have also seen SECREPAIR messages if I psexec to a server and then install an MSI using msiexec.

Neil

-----Original Message-----
From: Rob Mensching [mailto:[hidden email]]
Sent: 26 August 2014 21:34
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

FWIW, we haven't seen this with any FireGiant customers yet. That's a large part of why I'm at a loss.

However, we have been hearing stories of other issues in the last couple batches of updates from Microsoft. Quality control may have slipped up there a bit recently.
_______________________________________________________________
 FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

-----Original Message-----
From: John Cooper [mailto:[hidden email]]
Sent: Tuesday, August 26, 2014 1:10 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

We have a support contract, and I have forwarded this thread to my manager as it is of some concern, although we haven't seen this yet.  If it hits us, we'll definitely be looking into it.  Meanwhile, I'll politic for further investigation.

--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext:  431050 |[hidden email]



-----Original Message-----
From: [hidden email] [mailto:[hidden email]]
Sent: Tuesday, August 26, 2014 2:52 PM
To: [hidden email]
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Has anyone with a support contract or the like with Microsoft asked about this? I've pre-emptively raised a concern with some of my colleagues but people don't know what to make of a bunch of isolated forum posts/this list's thread.




Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 [hidden email] Telephone | Téléphone 613-854-5589 Facsimile | Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada


-----Original Message-----
From: Rob Mensching [mailto:[hidden email]]
Sent: August-26-14 12:45 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Okay. That points to the fix having issues and not being isolated to Burn. Which, fortunately or unfortunately, means Microsoft probably needs to fix the fix.

_______________________________________________________________
 FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

-----Original Message-----
From: Matt O'Connell [mailto:[hidden email]]
Sent: Tuesday, August 26, 2014 9:02 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Custom Autorun/Setup.exe (elevating) that's been working fine for years, OR on the CMD line line msiexec /i path to msi (where it will prompt to elevate as well).
On 26/08/2014 16:15, Rob Mensching wrote:

> How are you installing the MSIs? Just double-click the .MSI directly, as part of a Bundle, some other mechanism?
>
> _______________________________________________________________
>   FireGiant  |  Dedicated support for the WiX toolset  |
> http://www.firegiant.com/
>
> -----Original Message-----
> From: Matt O'Connell [mailto:[hidden email]]
> Sent: Tuesday, August 26, 2014 3:35 AM
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
> create the default key container
>
> We get a slightly different error out of CryptAcquireContext, ours follow this pattern:
> MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: Hash Database:
> C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
> MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file already exists. Deleting it.
> MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation complete.
> MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt Provider not initialized. Error:997 MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: Failed to CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG: for computing its hash. Err!
 or: 997 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Failed to create hash for the install source files MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error

> code: 3e5F6C634B8
>
> Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
>
> On 26/08/2014 11:05, Matt O'Connell wrote:
>> We've started seeing this a lot recently.
>> Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
>> Our customers with the issue are usually running some sort of
>> antivirus and we presumed it's some kind of conflict with that but
>> we've had no success with disabling Anti-virus with msconfig. However
>> removing the kb update has fixed it for at least one customer. I'm
>> hoping to find a recipe to replicate it but we're not there yet.
>>
>> I'm hoping MS find a fix an re-issue the update.:-)
>>
>> On 18/08/2014 22:54, Neil Sleightholm wrote:
>>> Thanks, seen that one and this one
>>> https://community.logos.com/forums/p/87997/617278.aspx. Both look
>>> similar.
>>>
>>> Neil
>>>
>>> -----Original Message-----
>>> From: Phill Hogland [mailto:[hidden email]]
>>> Sent: 18 August 2014 20:13
>>> To: [hidden email]
>>> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
>>> create the default key container
>>>
>>> FYI
>>> http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb2918
>>> 6 14-causing-overlapped-i-o-operation-progress-errors.html
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREP
>>> A
>>> IR-CryptAcquireContext-Could-not-create-the-default-key-container-tp
>>> 7 596414p7596418.html Sent from the wix-users mailing list archive
>>> at Nabble.com.
>>>
>>> --------------------------------------------------------------------
>>> -
>>> ---------
>>>
>>> _______________________________________________
>>> WiX-users mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>>
>>> --------------------------------------------------------------------
>>> -
>>> ---------
>>>
>>> _______________________________________________
>>> WiX-users mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> ----------------------------------------------------------------------
> --------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> ----------------------------------------------------------------------
> --------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users



------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.


------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: SECREPAIR: CryptAcquireContext: Could not create the default key container

Sascha
In reply to this post by Neil Sleightholm
@Neil: Yes, for us removing KB2918614 fixed the error and got us back to
working state. No other workaround known at this time.

I've been trying to figure out why this only seems to affect certain MSIs.
Here some parameters that might be relevant:
- WiX 3.8
- per-User install, no elevated privileges
- Custom managed bootstrapper on .NET 4.0
- Custom managed action

Since this is reproducible directly with the MSI already I don't think it
has anything to do with the bundle or any of the bundle parameters.

The KB2918614 information website shows that Msi.dll and other related
binaries are being replaced, I wish there was some more information on what
they actually changed in Windows Installer, that would probably help locate
where these issues are coming from and what scenarios trigger them.

// Sascha



On Thu, Aug 28, 2014 at 1:00 PM, Neil Sleightholm <[hidden email]>
wrote:

> I have seen that reported but I think it is slightly different. Does
> removing kb2918614 fix it?
>
> -----Original Message-----
> From: Matt O'Connell [mailto:[hidden email]]
> Sent: 26 August 2014 11:35
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create
> the default key container
>
> We get a slightly different error out of CryptAcquireContext, ours follow
> this pattern:
> MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: Hash Database:
> C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
> MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file
> already exists. Deleting it.
> MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038
> MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation
> complete.
> MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running
> CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt
> Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:859]:
> SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
> [10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s)
> (28:BC) [10:47:26:860]: SECREPAIR: A general error running
> CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt
> Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:861]:
> SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
> [10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s)
> (28:BC) [10:47:26:862]: SECREPAIR: A general error running
> CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt
> Provider not initialized. Error:997 MSI (s) (28:BC) [10:47:26:862]:
> SECUREREPAIR: Failed to CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG:
> for computing its hash. Error: 997 MSI (s) (28:BC) [10:47:26:862]:
> SECREPAIR: Failed to create hash for the install source files MSI (s)
> (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
> code: 3e5F6C634B8
>
> Error 997 being the Windows error 'Overlapped I/O operation is in
> progress.'
>
> On 26/08/2014 11:05, Matt O'Connell wrote:
> > We've started seeing this a lot recently.
> > Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
> > Our customers with the issue are usually running some sort of
> > antivirus and we presumed it's some kind of conflict with that but
> > we've had no success with disabling Anti-virus with msconfig. However
> > removing the kb update has fixed it for at least one customer. I'm
> > hoping to find a recipe to replicate it but we're not there yet.
> >
> > I'm hoping MS find a fix an re-issue the update.:-)
> >
> > On 18/08/2014 22:54, Neil Sleightholm wrote:
> >> Thanks, seen that one and this one
> >> https://community.logos.com/forums/p/87997/617278.aspx. Both look
> >> similar.
> >>
> >> Neil
> >>
> >> -----Original Message-----
> >> From: Phill Hogland [mailto:[hidden email]]
> >> Sent: 18 August 2014 20:13
> >> To: [hidden email]
> >> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
> >> create the default key container
> >>
> >> FYI
> >> http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb29186
> >> 14-causing-overlapped-i-o-operation-progress-errors.html
> >>
> >>
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPA
> >> IR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7
> >> 596414p7596418.html Sent from the wix-users mailing list archive at
> >> Nabble.com.
> >>
> >> ---------------------------------------------------------------------
> >> ---------
> >>
> >> _______________________________________________
> >> WiX-users mailing list
> >> [hidden email]
> >> https://lists.sourceforge.net/lists/listinfo/wix-users
> >>
> >> ---------------------------------------------------------------------
> >> ---------
> >>
> >> _______________________________________________
> >> WiX-users mailing list
> >> [hidden email]
> >> https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: SECREPAIR: CryptAcquireContext: Could not create the default key container

Neil Sleightholm
Our install isn't any of those :-)
WiX 3.7, Per Machine, No bootstrapper, No managed CA

I can reproduce the issue with a very minimal MSI, no UI, only installs 1 file.

Neil

-----Original Message-----
From: Sascha Sertel [mailto:[hidden email]]
Sent: 28 August 2014 21:31
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

@Neil: Yes, for us removing KB2918614 fixed the error and got us back to working state. No other workaround known at this time.

I've been trying to figure out why this only seems to affect certain MSIs.
Here some parameters that might be relevant:
- WiX 3.8
- per-User install, no elevated privileges
- Custom managed bootstrapper on .NET 4.0
- Custom managed action

Since this is reproducible directly with the MSI already I don't think it has anything to do with the bundle or any of the bundle parameters.

The KB2918614 information website shows that Msi.dll and other related binaries are being replaced, I wish there was some more information on what they actually changed in Windows Installer, that would probably help locate where these issues are coming from and what scenarios trigger them.

// Sascha



On Thu, Aug 28, 2014 at 1:00 PM, Neil Sleightholm <[hidden email]>
wrote:

> I have seen that reported but I think it is slightly different. Does
> removing kb2918614 fix it?
>
> -----Original Message-----
> From: Matt O'Connell [mailto:[hidden email]]
> Sent: 26 August 2014 11:35
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
> create the default key container
>
> We get a slightly different error out of CryptAcquireContext, ours
> follow this pattern:
> MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: Hash Database:
> C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
> MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file
> already exists. Deleting it.
> MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3:
> -2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash
> Database creation complete.
> MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running
> CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt
> Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:859]:
> SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
> [10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI
> (s)
> (28:BC) [10:47:26:860]: SECREPAIR: A general error running
> CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt
> Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:861]:
> SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
> [10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI
> (s)
> (28:BC) [10:47:26:862]: SECREPAIR: A general error running
> CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt
> Provider not initialized. Error:997 MSI (s) (28:BC) [10:47:26:862]:
> SECUREREPAIR: Failed to CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG:
> for computing its hash. Error: 997 MSI (s) (28:BC) [10:47:26:862]:
> SECREPAIR: Failed to create hash for the install source files MSI (s)
> (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
> code: 3e5F6C634B8
>
> Error 997 being the Windows error 'Overlapped I/O operation is in
> progress.'
>
> On 26/08/2014 11:05, Matt O'Connell wrote:
> > We've started seeing this a lot recently.
> > Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
> > Our customers with the issue are usually running some sort of
> > antivirus and we presumed it's some kind of conflict with that but
> > we've had no success with disabling Anti-virus with msconfig.
> > However removing the kb update has fixed it for at least one
> > customer. I'm hoping to find a recipe to replicate it but we're not there yet.
> >
> > I'm hoping MS find a fix an re-issue the update.:-)
> >
> > On 18/08/2014 22:54, Neil Sleightholm wrote:
> >> Thanks, seen that one and this one
> >> https://community.logos.com/forums/p/87997/617278.aspx. Both look
> >> similar.
> >>
> >> Neil
> >>
> >> -----Original Message-----
> >> From: Phill Hogland [mailto:[hidden email]]
> >> Sent: 18 August 2014 20:13
> >> To: [hidden email]
> >> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
> >> create the default key container
> >>
> >> FYI
> >> http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb291
> >> 86 14-causing-overlapped-i-o-operation-progress-errors.html
> >>
> >>
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECRE
> >> PA
> >> IR-CryptAcquireContext-Could-not-create-the-default-key-container-t
> >> p7 596414p7596418.html Sent from the wix-users mailing list archive
> >> at Nabble.com.
> >>
> >> -------------------------------------------------------------------
> >> --
> >> ---------
> >>
> >> _______________________________________________
> >> WiX-users mailing list
> >> [hidden email]
> >> https://lists.sourceforge.net/lists/listinfo/wix-users
> >>
> >> -------------------------------------------------------------------
> >> --
> >> ---------
> >>
> >> _______________________________________________
> >> WiX-users mailing list
> >> [hidden email]
> >> https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
>
>
> ----------------------------------------------------------------------
> --------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> ----------------------------------------------------------------------
> --------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: SECREPAIR: CryptAcquireContext: Could not create the default key container

Sascha
@Neil: That's good to know, and great to have an easy repro, I'm sure
Microsoft will need that to come up with a fix. But this still only affects
the upgrade case, or does it happen on first install for you as well? In my
case it's only on (minor) upgrade, fresh install works fine.

This makes me wonder even more why others aren't affected by this, maybe
most people simply don't update their Windows machines with the latest
updates that often? I update my test machine regularly exactly for this
scenario where a new KB update breaks something.

// Sascha



On Thu, Aug 28, 2014 at 2:09 PM, Neil Sleightholm <[hidden email]>
wrote:

> Our install isn't any of those :-)
> WiX 3.7, Per Machine, No bootstrapper, No managed CA
>
> I can reproduce the issue with a very minimal MSI, no UI, only installs 1
> file.
>
> Neil
>
> -----Original Message-----
> From: Sascha Sertel [mailto:[hidden email]]
> Sent: 28 August 2014 21:31
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create
> the default key container
>
> @Neil: Yes, for us removing KB2918614 fixed the error and got us back to
> working state. No other workaround known at this time.
>
> I've been trying to figure out why this only seems to affect certain MSIs.
> Here some parameters that might be relevant:
> - WiX 3.8
> - per-User install, no elevated privileges
> - Custom managed bootstrapper on .NET 4.0
> - Custom managed action
>
> Since this is reproducible directly with the MSI already I don't think it
> has anything to do with the bundle or any of the bundle parameters.
>
> The KB2918614 information website shows that Msi.dll and other related
> binaries are being replaced, I wish there was some more information on what
> they actually changed in Windows Installer, that would probably help locate
> where these issues are coming from and what scenarios trigger them.
>
> // Sascha
>
>
>
> On Thu, Aug 28, 2014 at 1:00 PM, Neil Sleightholm <[hidden email]>
> wrote:
>
> > I have seen that reported but I think it is slightly different. Does
> > removing kb2918614 fix it?
> >
> > -----Original Message-----
> > From: Matt O'Connell [mailto:[hidden email]]
> > Sent: 26 August 2014 11:35
> > To: General discussion about the WiX toolset.
> > Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
> > create the default key container
> >
> > We get a slightly different error out of CryptAcquireContext, ours
> > follow this pattern:
> > MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: Hash Database:
> > C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
> > MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file
> > already exists. Deleting it.
> > MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3:
> > -2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash
> > Database creation complete.
> > MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running
> > CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt
> > Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:859]:
> > SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
> > [10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI
> > (s)
> > (28:BC) [10:47:26:860]: SECREPAIR: A general error running
> > CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt
> > Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:861]:
> > SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
> > [10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI
> > (s)
> > (28:BC) [10:47:26:862]: SECREPAIR: A general error running
> > CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt
> > Provider not initialized. Error:997 MSI (s) (28:BC) [10:47:26:862]:
> > SECUREREPAIR: Failed to CreateContentHash of the file:
> xxxx\xxxxx\xxxx.JPG:
> > for computing its hash. Error: 997 MSI (s) (28:BC) [10:47:26:862]:
> > SECREPAIR: Failed to create hash for the install source files MSI (s)
> > (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
> > code: 3e5F6C634B8
> >
> > Error 997 being the Windows error 'Overlapped I/O operation is in
> > progress.'
> >
> > On 26/08/2014 11:05, Matt O'Connell wrote:
> > > We've started seeing this a lot recently.
> > > Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
> > > Our customers with the issue are usually running some sort of
> > > antivirus and we presumed it's some kind of conflict with that but
> > > we've had no success with disabling Anti-virus with msconfig.
> > > However removing the kb update has fixed it for at least one
> > > customer. I'm hoping to find a recipe to replicate it but we're not
> there yet.
> > >
> > > I'm hoping MS find a fix an re-issue the update.:-)
> > >
> > > On 18/08/2014 22:54, Neil Sleightholm wrote:
> > >> Thanks, seen that one and this one
> > >> https://community.logos.com/forums/p/87997/617278.aspx. Both look
> > >> similar.
> > >>
> > >> Neil
> > >>
> > >> -----Original Message-----
> > >> From: Phill Hogland [mailto:[hidden email]]
> > >> Sent: 18 August 2014 20:13
> > >> To: [hidden email]
> > >> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
> > >> create the default key container
> > >>
> > >> FYI
> > >> http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb291
> > >> 86 14-causing-overlapped-i-o-operation-progress-errors.html
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> --
> > >> View this message in context:
> > >> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECRE
> > >> PA
> > >> IR-CryptAcquireContext-Could-not-create-the-default-key-container-t
> > >> p7 596414p7596418.html Sent from the wix-users mailing list archive
> > >> at Nabble.com.
> > >>
> > >> -------------------------------------------------------------------
> > >> --
> > >> ---------
> > >>
> > >> _______________________________________________
> > >> WiX-users mailing list
> > >> [hidden email]
> > >> https://lists.sourceforge.net/lists/listinfo/wix-users
> > >>
> > >> -------------------------------------------------------------------
> > >> --
> > >> ---------
> > >>
> > >> _______________________________________________
> > >> WiX-users mailing list
> > >> [hidden email]
> > >> https://lists.sourceforge.net/lists/listinfo/wix-users
> > >
> >
> >
> >
> > ----------------------------------------------------------------------
> > --------
> > Slashdot TV.
> > Video for Nerds.  Stuff that matters.
> > http://tv.slashdot.org/
> > _______________________________________________
> > WiX-users mailing list
> > [hidden email]
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> >
> > ----------------------------------------------------------------------
> > --------
> > Slashdot TV.
> > Video for Nerds.  Stuff that matters.
> > http://tv.slashdot.org/
> > _______________________________________________
> > WiX-users mailing list
> > [hidden email]
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: SECREPAIR: CryptAcquireContext: Could not create the default key container

roberthyang
In reply to this post by roberthyang
I just tried it with KB2918614 removed, and got a different error, "Error 1316.A network error occurred while attempting to read from the file" :

Action start 14:45:54: PublishFeatures.
MSI (s) (7C:8C) [14:45:54:217]: Doing action: PublishProduct
Action ended 14:45:54: PublishFeatures. Return value 1.
Action start 14:45:54: PublishProduct.
MSI (s) (7C:8C) [14:45:54:217]: Resolving source.
MSI (s) (7C:8C) [14:45:54:217]: Resolving source to launched-from source.
MSI (s) (7C:8C) [14:45:54:217]: Setting launched-from source as last-used.
MSI (s) (7C:8C) [14:45:54:217]: PROPERTY CHANGE: Adding SourceDir property. Its value is 'C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\'.
MSI (s) (7C:8C) [14:45:54:217]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is 'C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\'.
MSI (s) (7C:8C) [14:45:54:217]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}'.
MSI (s) (7C:8C) [14:45:54:217]: SOURCEDIR ==> C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\
MSI (s) (7C:8C) [14:45:54:217]: SOURCEDIR product ==> {D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}
MSI (s) (7C:8C) [14:45:54:217]: Determining source type
MSI (s) (7C:8C) [14:45:54:217]: Note: 1: 2203 2: C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi 3: -2147287038
MSI (s) (7C:8C) [14:45:54:217]: Note: 1: 1316 2: C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi
MSI (s) (7C:8C) [14:45:58:507]: Product: Microsoft SQL Server Compact 3.5 SP2 x64 ENU -- Error 1316.A network error occurred while attempting to read from the file C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi

Error 1316.A network error occurred while attempting to read from the file C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi

Any thoughts ?

roberthyang wrote
We just started seeing a possibly-related error recently.  We have a burn bootstrapper in Wix 3.8 and among the bundle MSI's is SQL Server Compact SP2 x64 (SSCERuntime-ENU-x64.msi).  When the bootstrapper attempts to repair the application, the repair of SQL Server Compact SP2 x64 fails with "Error 1316.The specified account already exists."

An excerpt from the log is as follows :

Action start 12:09:35: PublishFeatures.
MSI (s) (D4:54) [12:09:35:006]: Doing action: PublishProduct
Action ended 12:09:35: PublishFeatures. Return value 1.
Action start 12:09:35: PublishProduct.
MSI (s) (D4:54) [12:09:35:008]: Resolving source.
MSI (s) (D4:54) [12:09:35:008]: Resolving source to launched-from source.
MSI (s) (D4:54) [12:09:35:008]: Setting launched-from source as last-used.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding SourceDir property. Its value is 'C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\'.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is 'C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\'.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}'.
MSI (s) (D4:54) [12:09:35:008]: SOURCEDIR ==> C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\
MSI (s) (D4:54) [12:09:35:008]: SOURCEDIR product ==> {D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}
MSI (s) (D4:54) [12:09:35:008]: Determining source type
MSI (s) (D4:54) [12:09:35:008]: Note: 1: 2203 2: C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi 3: -2147287038
MSI (s) (D4:54) [12:09:35:008]: Note: 1: 1316 2: C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi
MSI (s) (D4:54) [12:09:35:008]: SECREPAIR: Error determining package source type
MSI (s) (D4:54) [12:09:35:008]: SECUREREPAIR: SecureRepair Failed. Error code: 524F5C634B8
MSI (s) (D4:54) [12:09:38:487]: Product: Microsoft SQL Server Compact 3.5 SP2 x64 ENU -- Error 1316.The specified account already exists.

Repair of SQL Server Compact SP2 x64 works fine from the Control Panel and from Explorer.  I know this used to work, as I tested it earlier this year.  Here is our Wix code to include the MSI :

      <MsiPackage
        Id="SSCERuntime_x64"
        Cache="no"
        Compressed="no"
        Permanent="yes"
        Visible="yes"
        Vital="yes"
        Name="SQL Server Compact Edition\SSCERuntime-ENU-x64.msi"
        SourceFile="$(var.MSSDKBootstrapperPath)Packages\SQL Server Compact Edition\EN\SSCERuntime-ENU-x64.msi"
        DownloadUrl="http://go.microsoft.com/fwlink/?LinkID=166086"/>

I'm guessing it has to do with this :

https://technet.microsoft.com/library/security/MS14-049

I'm hoping there is a workaround.  Thanks for any advice !
-Rob
Reply | Threaded
Open this post in threaded view
|

Re: SECREPAIR: CryptAcquireContext: Could not create the default key container

Keith.Douglas
I got that once when some McAfee product or other was trying to install itself at the same time (we run its AV and a few other things on my target machines), and a few months ago - well before this update.

Somehow also when that happens one gets the McAfee product details in the install log created for *my* application.

I thought nothing of it at the time, since we know that WI is effectively not re-entrant. But ...


Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
[hidden email]
Telephone | Téléphone 613-854-5589
Facsimile | Télécopieur 613-951-4674
Government of Canada | Gouvernement du Canada


-----Original Message-----
From: roberthyang [mailto:[hidden email]]
Sent: August-28-14 5:53 PM
To: [hidden email]
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

I just tried it with KB2918614 removed, and got a different error, "Error 1316.A network error occurred while attempting to read from the file" :

Action start 14:45:54: PublishFeatures.
MSI (s) (7C:8C) [14:45:54:217]: Doing action: PublishProduct Action ended 14:45:54: PublishFeatures. Return value 1.
Action start 14:45:54: PublishProduct.
MSI (s) (7C:8C) [14:45:54:217]: Resolving source.
MSI (s) (7C:8C) [14:45:54:217]: Resolving source to launched-from source.
MSI (s) (7C:8C) [14:45:54:217]: Setting launched-from source as last-used.
MSI (s) (7C:8C) [14:45:54:217]: PROPERTY CHANGE: Adding SourceDir property.
Its value is 'C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\'.
MSI (s) (7C:8C) [14:45:54:217]: PROPERTY CHANGE: Adding SOURCEDIR property.
Its value is 'C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\'.
MSI (s) (7C:8C) [14:45:54:217]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}'.
MSI (s) (7C:8C) [14:45:54:217]: SOURCEDIR ==> C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\ MSI (s) (7C:8C) [14:45:54:217]: SOURCEDIR product ==> {D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}
MSI (s) (7C:8C) [14:45:54:217]: Determining source type MSI (s) (7C:8C) [14:45:54:217]: Note: 1: 2203 2: C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi 3: -2147287038 MSI (s) (7C:8C) [14:45:54:217]: Note: 1: 1316 2: C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi MSI (s) (7C:8C) [14:45:58:507]: Product: Microsoft SQL Server Compact 3.5
SP2 x64 ENU -- Error 1316.A network error occurred while attempting to read from the file C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi

Error 1316.A network error occurred while attempting to read from the file C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi

Any thoughts ?


roberthyang wrote

> We just started seeing a possibly-related error recently.  We have a
> burn bootstrapper in Wix 3.8 and among the bundle MSI's is SQL Server
> Compact
> SP2 x64 (SSCERuntime-ENU-x64.msi).  When the bootstrapper attempts to
> repair the application, the repair of SQL Server Compact SP2 x64 fails
> with "Error 1316.The specified account already exists."
>
> An excerpt from the log is as follows :
>
> Action start 12:09:35: PublishFeatures.
> MSI (s) (D4:54) [12:09:35:006]: Doing action: PublishProduct Action
> ended 12:09:35: PublishFeatures. Return value 1.
> Action start 12:09:35: PublishProduct.
> MSI (s) (D4:54) [12:09:35:008]: Resolving source.
> MSI (s) (D4:54) [12:09:35:008]: Resolving source to launched-from source.
> MSI (s) (D4:54) [12:09:35:008]: Setting launched-from source as last-used.
> MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding SourceDir
> property. Its value is 'C:\ProgramData\Package
> Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server
> Compact Edition\'.
> MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding SOURCEDIR
> property. Its value is 'C:\ProgramData\Package
> Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server
> Compact Edition\'.
> MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding
> SourcedirProduct property. Its value is '{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}'.
> MSI (s) (D4:54) [12:09:35:008]: SOURCEDIR ==> C:\ProgramData\Package
> Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server
> Compact Edition\ MSI (s) (D4:54) [12:09:35:008]: SOURCEDIR product ==>
> {D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}
> MSI (s) (D4:54) [12:09:35:008]: Determining source type MSI (s)
> (D4:54) [12:09:35:008]: Note: 1: 2203 2: C:\ProgramData\Package
> Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server
> Compact Edition\SSCERuntime_x64-enu.msi 3: -2147287038 MSI (s) (D4:54)
> [12:09:35:008]: Note: 1: 1316 2: C:\ProgramData\Package
> Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server
> Compact Edition\SSCERuntime_x64-enu.msi MSI (s) (D4:54)
> [12:09:35:008]: SECREPAIR: Error determining package source type MSI
> (s) (D4:54) [12:09:35:008]: SECUREREPAIR: SecureRepair Failed. Error
> code: 524F5C634B8
> MSI (s) (D4:54) [12:09:38:487]: Product: Microsoft SQL Server Compact
> 3.5
> SP2 x64 ENU -- Error 1316.The specified account already exists.
>
> Repair of SQL Server Compact SP2 x64 works fine from the Control Panel
> and from Explorer.  I know this used to work, as I tested it earlier
> this year.  Here is our Wix code to include the MSI :
>
>      
> <MsiPackage
>         Id="SSCERuntime_x64"
>         Cache="no"
>         Compressed="no"
>         Permanent="yes"
>         Visible="yes"
>         Vital="yes"
>         Name="SQL Server Compact Edition\SSCERuntime-ENU-x64.msi"
>         SourceFile="$(var.MSSDKBootstrapperPath)Packages\SQL Server
> Compact Edition\EN\SSCERuntime-ENU-x64.msi"
>         DownloadUrl="http://go.microsoft.com/fwlink/?LinkID=166086"/>
> I'm guessing it has to do with this :
>
> https://technet.microsoft.com/library/security/MS14-049
>
> I'm hoping there is a workaround.  Thanks for any advice !
> -Rob





--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7596414p7596614.html
Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
123