date:20140826

Re: [WiX-users] Cannot view RootView.xaml file in visual studio 2010

2014-08-26 Thread Rob Mensching

I'm not aware of a "wix.zip" file on the WiX toolset website. Did you download 
a different file perhaps? Or download from a different web site?

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

-Original Message-
From: linos [mailto:lino...@hotmail.com] 
Sent: Tuesday, August 26, 2014 7:58 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Cannot view RootView.xaml file in visual studio 2010

Ok I think I figured this one out.  Well what works for me.  
In case someone else runs into this problem here is what I did.

I downloaded the wix.zip file from the wix website and right clicked on the zip 
file went to properties and checked 'unblock'.
I then create a new wpf solution and named it TestBA. I then created two new 
wpf projects, one named TestBA and the other Core.  I then manually copied all 
files from the core project located under the src\ext\BalExtension\mba\core\ 
directory to my newly created Core project. 
Then I copied all files under the src\Setup\WixBA directoy to my newly created 
TestBA project directory. Now with all the files moved respectively under the 
each directory, I edited the namespaces for each project. I also updated the 
'suppress warnings'  and xml file documentation file in the core project 
properties and updated the reference assemblies to match the existing core 
project. And for the TestBA project I needed to update the namespace in the 
project properties as well as the references to match the existing WixBA 
project references.

So basically I needed to create a new solution file along with two wpf projects 
and add the source code manually.

Unless someone else can prove otherwise, I believe there is something 
inherently bad with WPF projects when zipped and shipped.  I'm not sure if its 
related to security or windows 7 security or possibly a bug within visual 
studio 2010.  



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Cannot-view-RootView-xaml-file-in-visual-studio-2010-tp7596500p7596565.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
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Cannot view RootView.xaml file in visual studio 2010

2014-08-26 Thread linos

Ok I think I figured this one out. Well what works for me.
In case someone else runs into this problem here is what I did.

I downloaded the wix.zip file from the wix website and right clicked on the
zip file went to properties and checked 'unblock'.
I then create a new wpf solution and named it TestBA. I then created two new
wpf projects, one named TestBA and the other Core. I then manually copied
all files from the core project located under the
src\ext\BalExtension\mba\core\ directory to my newly created Core project.
Then I copied all files under the src\Setup\WixBA directoy to my newly
created TestBA project directory. Now with all the files moved respectively
under the each directory, I edited the namespaces for each project. I also
updated the 'suppress warnings' and xml file documentation file in the core
project properties and updated the reference assemblies to match the
existing core project. And for the TestBA project I needed to update the
namespace in the project properties as well as the references to match the
existing WixBA project references.

So basically I needed to create a new solution file along with two wpf
projects and add the source code manually.

Unless someone else can prove otherwise, I believe there is something
inherently bad with WPF projects when zipped and shipped. I'm not sure if
its related to security or windows 7 security or possibly a bug within
visual studio 2010.

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Cannot-view-RootView-xaml-file-in-visual-studio-2010-tp7596500p7596565.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
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

2014-08-26 Thread Rob Mensching

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:jocoo...@jackhenry.com] 
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 
|jocoo...@jackhenry.com



-Original Message-
From: keith.doug...@statcan.gc.ca [mailto:keith.doug...@statcan.gc.ca]
Sent: Tuesday, August 26, 2014 2:52 PM
To: wix-users@lists.sourceforge.net
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 
keith.doug...@statcan.gc.ca 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:r...@firegiant.com]
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:techsupport...@gmail.com]
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:techsupport...@gmail.com]
> 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{xxx----}
> 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 CreateCo

Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

2014-08-26 Thread John Cooper

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 
|jocoo...@jackhenry.com



-Original Message-
From: keith.doug...@statcan.gc.ca [mailto:keith.doug...@statcan.gc.ca] 
Sent: Tuesday, August 26, 2014 2:52 PM
To: wix-users@lists.sourceforge.net
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 
keith.doug...@statcan.gc.ca 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:r...@firegiant.com]
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:techsupport...@gmail.com]
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:techsupport...@gmail.com]
> 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{xxx----}
> 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: \x\.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

Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

2014-08-26 Thread 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
keith.doug...@statcan.gc.ca
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:r...@firegiant.com] 
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:techsupport...@gmail.com]
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:techsupport...@gmail.com]
> 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{xxx----}
> 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: \x\.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:phogl...@rimage.com]
>>> Sent: 18 August 2014 20:13
>>> To: wix-users@lists.sourceforge.net
>>> Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not 
>>> create the default key container
>>>
>>> FYI
>>> http://www.edug

Re: [WiX-users] Compiled Burn executable returns immediately on command line in passive mode

2014-08-26 Thread Rob Mensching

Yes, it works with all Windows applications (i.e. non-console applications).

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

-Original Message-
From: ahar...@cox.net [mailto:ahar...@cox.net] 
Sent: Tuesday, August 26, 2014 11:01 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Compiled Burn executable returns immediately on 
command line in passive mode


 "Nicolás Alvarez"  wrote: 
>>Tried "start /wait bundle.exe"?

It worked!  I thought it would just return as fast as the bundle.exe does, but 
I'm guessing it actually waits for spawned processes too.  It even reports 
correct exit codes.

Thanks!
Anthony H.

--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Compiled Burn executable returns immediately on command line in passive mode

2014-08-26 Thread ahargan


 "Nicolás Alvarez"  wrote: 
>>Tried "start /wait bundle.exe"?

It worked!  I thought it would just return as fast as the bundle.exe does, but 
I'm guessing it actually waits for spawned processes too.  It even reports 
correct exit codes.

Thanks!
Anthony H.

--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

2014-08-26 Thread Rob Mensching

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:techsupport...@gmail.com] 
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:techsupport...@gmail.com]
> 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{xxx----}
> 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: \x\.JPG: 
> for computing its hash. Error: 997 M
 SI (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:phogl...@rimage.com]
>>> Sent: 18 August 2014 20:13
>>> To: wix-users@lists.sourceforge.net
>>> 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
>>> WiX-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>>
>>> -
>>> -
>>>
>>> __

Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

2014-08-26 Thread Matt O'Connell

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:techsupport...@gmail.com]
> 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{xxx----}
> 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: \x\.JPG: 
> for computing its hash. Error: 997 M
 SI (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:phogl...@rimage.com]
>>> Sent: 18 August 2014 20:13
>>> To: wix-users@lists.sourceforge.net
>>> 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
>>> WiX-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>>
>>> -
>>> -
>>>
>>> ___
>>> WiX-users mailing list
>>> WiX-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> --
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> --
> Slashdot TV.
>

Re: [WiX-users] Getting wrong UILevel in custom action

2014-08-26 Thread Rob Mensching

Hmm, that's not what I would expect. Wixstdba should show a MessageBox for the 
::MsiProcessMessages unless run /passive or /quiet.

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

-Original Message-
From: krupeshdhruv [mailto:krupeshdh...@gmail.com] 
Sent: Monday, August 25, 2014 11:41 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Getting wrong UILevel in custom action

Hi,

I used ::MsiProcessMessage.
It is working in normal install /uninstall mode. (i.e uninstalling form 
Add/remove program)

If I use command line options   /uninstall , then its 
suppressing all UI.
And message box is not displayed in this case.


Expected behavior should be , it would not show any dialog only in silent flag 
enabled. (i.e.  /uninstall /quiet.

Steps done by me:
I have added one MsiHandle and created custom message to be displayed on dialog.
Then I use passed those msg n handle in MsiRecordString followed by 
::MsiProcessMessage with INSTALLMESSAGE type  as INFO.

Am I doing something wrong here?

with regards,
KD




On Sun, Aug 24, 2014 at 2:30 AM, Rob Mensching-7 [via Windows Installer XML
(WiX) toolset]  wrote:

> Actually, after re-reading your scenario, if your CA calls
> ::MsiProcessMessage() (as it should) then that should pass through to 
> the BA correctly.
>
> ___
>  FireGiant  |  Dedicated support for the WiX toolset  | 
> http://www.firegiant.com/
>
> -Original Message-
> From: krupeshdhruv [mailto:[hidden email] 
> ]
> Sent: Friday, August 22, 2014 11:13 PM
> To: [hidden email] 
> 
> Subject: Re: [WiX-users] Getting wrong UILevel in custom action
>
> Thanks Rob for the help.
> Which burn variable I should use?
>
> I do not using custom ba where I can get data from Custom class/structure.
>
> with regards,
> KD
>
>
> On Fri, Aug 22, 2014 at 9:43 PM, Rob Mensching-7 [via Windows 
> Installer XML
> (WiX) toolset] <[hidden email]
> > wrote:
>
> > Don't use the MSI UI. Pass in a Bundle Variable to the MsiProperty.
> >
> > ___
> >  FireGiant  |  Dedicated support for the WiX toolset  | 
> > http://www.firegiant.com/
> >
> > -Original Message-
> > From: krupeshdhruv [mailto:[hidden email] 
> > ]
> > Sent: Friday, August 22, 2014 7:59 AM
> > To: [hidden email]
> > 
> > Subject: [WiX-users] Getting wrong UILevel in custom action
> >
> > Hello Everyone,
> >
> > I am creating installer in wix 3.8
> > I have two msi created (32 and 64 bit each)
> >
> > I am using standard bootstrapper application to run them depending 
> > on platform.
> >
> > Problem:
> > I have one custom action which is invoked in un installation.
> > It checks the UI level and if it is >=5 then it will show one 
> > message box to user to delete one folder.
> >
> > Depending on users response, processing will be done.
> >
> > Problem:
> > I am passing UILevel in customaction data , but in any 
> > un-installation (Add/remove, app.exe /uninstall, app.exe /quiet 
> > /uninstall) its giving UILevel=2.
> >
> > I do not have custom ba dll for bootstrapper. I am using bundle.wxs
> only.
> > I even tried to show message box with out checking UILevel, but its 
> > not getting displayed. (may be due to UILevel is set as 2).
> >
> > Please let me know how to handle this type of scenario?
> >
> > Thanks in advance.
> > KD
> >
> >
> >
> >
> >
> >
> > --
> > View this message in context:
> > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Gettin
> > g- wrong-UILevel-in-custom-action-tp7596484.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
> >
> >
> > --
> >  If you reply to this email, your message will be added to the 
> > discussion
> > below:
> >
> > http://windows-installer-xm

Re: [WiX-users] Light error LGHT0204 : ICE83: Both MsiPublishAssemblies AND MsiUnpublishAssem blies actions MUST be present in InstallExecuteSequence table.

2014-08-26 Thread Rob Mensching

Yes, that Merge Module sounds busted. You can work around by adding those 
actions yourself.

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

-Original Message-
From: Uday [mailto:uday.kalhap...@gmail.com] 
Sent: Tuesday, August 26, 2014 2:16 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Light error LGHT0204 : ICE83: Both MsiPublishAssemblies 
AND MsiUnpublishAssem blies actions MUST be present in InstallExecuteSequence 
table.

Hi, 

   I am using  element to include existing merge module. But Light fails 
with errors. 
   One of the error is: 
  
  Light error LGHT0204 : ICE83: Both MsiPublishAssemblies AND
MsiUnpublishAssem blies actions MUST bepresent in InstallExecuteSequence
table. 

   Is there any issue in merge module file ? 

Thanks,
Uday



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Light-error-LGHT0204-ICE83-Both-MsiPublishAssemblies-AND-MsiUnpublishAssem-blies-actions-MUST-be-pre-tp7596547.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
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Options for pausing the download and installation in wix custom BootStrapper

2014-08-26 Thread Rob Mensching

That and there are lots of Cache related callbacks. You can pause in many of 
those.

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

-Original Message-
From: Asbjørn Mikkelsen [mailto:asbj...@neslekkim.net] 
Sent: Tuesday, August 26, 2014 5:52 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Options for pausing the download and installation in 
wix custom BootStrapper

What if you do something clever in OnResolveSource?, it looks like the WixBA 
does something for retrying downloads there, I don't understand how it works, 
but...


On Tue, Aug 26, 2014 at 2:09 PM, Balaji R  wrote:

> Hi,
>
> Can you please tell which is the correct event in 
> BootstrapperInstallEvent to pause the download and also please explain 
> the process to pause the download ?
>
> Thanks in advance
>
> Regards,
> Balajj R
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Options-
> for-pausing-the-download-and-installation-in-wix-custom-BootStrapper-t
> p7596512p7596550.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
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



--
mvh
Asbjørn
--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

2014-08-26 Thread Rob Mensching

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:techsupport...@gmail.com] 
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{xxx----}
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: \x\.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:phogl...@rimage.com]
>> Sent: 18 August 2014 20:13
>> To: wix-users@lists.sourceforge.net
>> 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
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>> -
>> -
>>
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>


--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Compiled Burn executable returns immediately on command line in passive mode

2014-08-26 Thread Nicolás Alvarez

2014-08-26 10:52 GMT-03:00  :
> Is there some way that's not documented to make the exe wait until the Burn 
> engine and BA are finished?  I've scoured the Internet and haven't even seen 
> anyone mention that this is an issue for them.  My next move is to dig into 
> the Burn source code.  Based on my observations so far, it appears that the 
> executable starts up the Burn engine and then returns immediately.  The Burn 
> engine then starts up the BA and works with it throughout the rest of the 
> installation process.

Tried "start /wait bundle.exe"?

-- 
Nicolás

--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Compiled Burn executable returns immediately on command line in passive mode

2014-08-26 Thread ahargan

Hello!

My organization has started using Burn with a custom Bootstrapper Application 
to install multiple application "pieces" onto our servers.  We currently use a 
dumbed down daily scheduling process inside of BladeLogic to install MSI's onto 
our servers and would like to start using this same process to run Burn 
executables on the servers.  However, we're running into a roadblock because 
the compiled exe returns immediately even though the Burn engine and BA keep 
running.  Our scheduling process was designed around the idea of waiting for an 
exe to return (and then evaluating return codes) before moving on to the next 
scheduled exe/MSI to run.  This works fine when running msiexec.exe to install 
MSI's, but breaks down when running Burn exe's because they return immediately.

Is there some way that's not documented to make the exe wait until the Burn 
engine and BA are finished?  I've scoured the Internet and haven't even seen 
anyone mention that this is an issue for them.  My next move is to dig into the 
Burn source code.  Based on my observations so far, it appears that the 
executable starts up the Burn engine and then returns immediately.  The Burn 
engine then starts up the BA and works with it throughout the rest of the 
installation process.

Any thoughts or knowledge about this would be helpful.

Thanks!
Anthony H

--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Options for pausing the download and installation in wix custom BootStrapper

2014-08-26 Thread Asbjørn Mikkelsen

What if you do something clever in OnResolveSource?, it looks like the
WixBA does something for retrying downloads there, I don't understand how
it works, but...


On Tue, Aug 26, 2014 at 2:09 PM, Balaji R  wrote:

> Hi,
>
> Can you please tell which is the correct event in BootstrapperInstallEvent
> to pause the download and also please explain the process to pause the
> download ?
>
> Thanks in advance
>
> Regards,
> Balajj R
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Options-for-pausing-the-download-and-installation-in-wix-custom-BootStrapper-tp7596512p7596550.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
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



-- 
mvh
Asbjørn
--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Options for pausing the download and installation in wix custom BootStrapper

2014-08-26 Thread Balaji R

Hi, 

Can you please tell which is the correct event in BootstrapperInstallEvent
to pause the download and also please explain the process to pause the
download ? 

Thanks in advance

Regards, 
Balajj R



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Options-for-pausing-the-download-and-installation-in-wix-custom-BootStrapper-tp7596512p7596550.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
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

2014-08-26 Thread Matt O'Connell

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{xxx----}
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: \x\.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:phogl...@rimage.com]
>> Sent: 18 August 2014 20:13
>> To: wix-users@lists.sourceforge.net
>> 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
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>> --
>>  
>>
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>


--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

2014-08-26 Thread Matt O'Connell

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:phogl...@rimage.com]
> Sent: 18 August 2014 20:13
> To: wix-users@lists.sourceforge.net
> 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
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> --
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Light error LGHT0204 : ICE83: Both MsiPublishAssemblies AND MsiUnpublishAssem blies actions MUST be present in InstallExecuteSequence table.

2014-08-26 Thread Uday

Hi, 

   I am using  element to include existing merge module. But Light
fails with errors. 
   One of the error is: 
  
  Light error LGHT0204 : ICE83: Both MsiPublishAssemblies AND
MsiUnpublishAssem blies actions MUST bepresent in InstallExecuteSequence
table. 

   Is there any issue in merge module file ? 

Thanks, 
Uday



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Light-error-LGHT0204-ICE83-Both-MsiPublishAssemblies-AND-MsiUnpublishAssem-blies-actions-MUST-be-pre-tp7596547.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
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Cannot view RootView.xaml file in visual studio 2010

Re: [WiX-users] Cannot view RootView.xaml file in visual studio 2010

Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Re: [WiX-users] Compiled Burn executable returns immediately on command line in passive mode

Re: [WiX-users] Compiled Burn executable returns immediately on command line in passive mode

Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Re: [WiX-users] Getting wrong UILevel in custom action

Re: [WiX-users] Light error LGHT0204 : ICE83: Both MsiPublishAssemblies AND MsiUnpublishAssem blies actions MUST be present in InstallExecuteSequence table.

Re: [WiX-users] Options for pausing the download and installation in wix custom BootStrapper

Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Re: [WiX-users] Compiled Burn executable returns immediately on command line in passive mode

[WiX-users] Compiled Burn executable returns immediately on command line in passive mode

Re: [WiX-users] Options for pausing the download and installation in wix custom BootStrapper

Re: [WiX-users] Options for pausing the download and installation in wix custom BootStrapper

Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

[WiX-users] Light error LGHT0204 : ICE83: Both MsiPublishAssemblies AND MsiUnpublishAssem blies actions MUST be present in InstallExecuteSequence table.

20 matches

Site Navigation

Mail list logo

Footer information