Re: [WiX-users] Restart Manager failed to open session

Yes I stumbled across this when I searched for the error code, and I immediately thought that it might not be an actual timeout but some kind of resource starvation. The machine that exposes this issue is pretty beefy and runs on two latest generation Xeon 6-core processors with 32 GB of RAM, so it

Re: [WiX-users] Restart Manager failed to open session

; Sorry to ask more questions but is some of the info you provided from a > verbose log output? Have you done a system comparison between the one > machine that had a successful installation vs. the target machine that has > the issue? > > J > > On Fri, Feb 13, 2015 at 12:53 PM, S

Re: [WiX-users] Restart Manager failed to open session

@Jeremiah: Yes I read pretty much everything on RestartManager that there is to find, but I don't even have any custom restart manager code. I am using my own MBA, but the RestartManager stuff is handled by WiX, I only respond to the file in use notification. However, when the RestartManager fails

[WiX-users] Restart Manager failed to open session

My WiX 3.9 installer uses RestartManager to shut down the app if it's still running before upgrading or uninstalling. That has worked great for me with very few issues. Now I have come across a Windows 7 (Pro, SP1, x64) system on which it consistently fails to shut down the app, every single time.

Re: [WiX-users] Burn MBA MS .NET 4.5.x Prerequisite

Hallo Andreas, it looks like you have the right pieces, but there are some differences from how my bundle typically looks: - I hope it's a typo that your prereq is NetFx452Redist but further down in the PackageGroupRef you're referencing NetFx451Redist? That second one should probably be NetFx452R

Re: [WiX-users] Download newer version of cached MSI if available

update was available. > STDMETHOD_(void, OnDetectUpdateComplete)( > __in HRESULT hrStatus, > __in_z_opt LPCWSTR wzUpdateLocation > ) = 0; > > > _________ > Short replies here. Complete answers ov

Re: [WiX-users] Download newer version of cached MSI if available

Okay, what (built-in) functionality is there for updating the bundle? The only thing I could find was this, but it's more about being able to do an update check from ARP and not while executing the bundle: http://wixtoolset.org/issues/4190/ // Sascha On Wed, Sep 24, 2014 at 8:51 PM, Rob Menschi

[WiX-users] Download newer version of cached MSI if available

Hello there, after some googling around I couldn't find a good match for this question, so let me start a new thread. What I would like to have is a bundle with embedded (= compressed) MSI packages inside, but then have my custom managed bootstrapper (or burn) check if there is a newer version of

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

about the WiX toolset. > Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create > the default key container > > Ok, did some install testing of the upgrade from the earlier version to > 1709 this morning. > > Windows Server 2008 R2 No repro > Windows Serve

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

> -- > 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: Sascha Sertel [

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

og look like for these three files? > > -- > John Merryweather Cooper > Senior Software Engineer | Enterprise Service Applications | Continuing > Development > Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 | > jocoo...@jackhenry.com > > > -Origina

Re: [WiX-users] Uninstalling bundle with broken BA

varez wrote: > I can properly uninstall the MSIs via msiexec /x {GUID}. The problem is > removing the stuff left behind by Burn, such as the cached bundle and > packages. I doubt msizap knows anything about bootstrappers... > > El lunes, 8 de septiembre de 2014, Sascha Sertel >

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

ct > installers. Much easier if I can replicate. > > I'm basically trying to figure out what is different in our installers and > deployment scenarios such that we don't see this issue. > > -- > John Merryweather Cooper > Senior Software Engineer | Enterprise S

Re: [WiX-users] Uninstalling bundle with broken BA

Let me introduce you to your new best friend: MsiZap ( http://msdn.microsoft.com/en-us/library/aa370523(v=vs.85).aspx) While I was doing custom BA development MsiZap helped me out of a few botched installations where I was stuck in t

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

The issue is very easily reproducible for me when doing an upgrade from one bundle to another one. I emailed Keith links to two installers that have 100% repro for me when upgrading from the one to the other while having KB2918614 installed. Repros on any machine. I'm happy to share some logs but

Re: [WiX-users] Issue with RemoveFolder and Error 2911 Config.msi

or the help! // Sascha On Fri, Sep 5, 2014 at 2:02 PM, Sascha Sertel wrote: > I thought when it uninstalls the old version it does so by running the > cached MSI for THAT version, which also doesn't have CONFIGFOLDER in it? > > I've made other changes to the installer before

Re: [WiX-users] Issue with RemoveFolder and Error 2911 Config.msi

t; On Fri, Sep 5, 2014 at 11:41 AM, John Cooper > wrote: > > > The database being referred to is probably the MSI itself. Problems > > with RemoveFolder usually occur when the property is not defined soon > enough. > > It must be defined before the RemoveFolders standard acti

Re: [WiX-users] Issue with RemoveFolder and Error 2911 Config.msi

ur authoring look like? Are you using a property? > > -- > John Merryweather Cooper > Senior Software Engineer | Enterprise Service Applications | Continuing > Development > Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 | > jocoo...@jackhenry.com > >

Re: [WiX-users] Issue with RemoveFolder and Error 2911 Config.msi

You must remove the > individual msi's not the folder. This usually indicates that the > uninstall/upgrade process cannot find the name of the msi to uninstall > or upgrade. > > And Save the following link to your Programmer's Toolbox: > http://msdn.microsoft.com/en-us/library

[WiX-users] Issue with RemoveFolder and Error 2911 Config.msi

I ran into a weird issue that I can't seem to figure out, hopefully someone has an idea. My issue happens only when doing a minor upgrade from an older version to a newer version of my product. The failure lines from the log look like this: MSI (s) (1C:3C) [23:17:21:084]: Note: 1: 2228 2: 3: Err

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

trusting the computer or the user > to allow delegation might be a fix. > --- > Phil Wilson > > > On Thu, Aug 28, 2014 at 10:14 PM, Neil Sleightholm > wrote: > > It also happens with a clean install in my scenario. > > > > -Original Messag

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

, Aug 28, 2014 at 2:09 PM, Neil Sleightholm 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--

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 privileg

Re: [WiX-users] Issues with Wix Installer per-user minor upgrade

@Rob: Yes the bundle as well as the packages inside the bundle all work fine without the August 12 update, but started failing after applying the update. @Phill: Yes that is exactly the issue I'm seeing as well. Is there any solution to this other than uninstalling the August 12 update? // Sasch

Re: [WiX-users] Issues with Wix Installer per-user minor upgrade

hem but I can't really find any product that would be suitable to file MSI defects against. // Sascha On Fri, Aug 22, 2014 at 12:23 PM, Sascha Sertel wrote: > I am having the EXACT same issue as described by Vikas, but I have reason > to believe that this breakage is caused by a rece

Re: [WiX-users] Issues with Wix Installer per-user minor upgrade

I am having the EXACT same issue as described by Vikas, but I have reason to believe that this breakage is caused by a recent Windows Update released by Microsoft, because I tested packages that used to upgrade fine from one version to the next (they are released in production and have been used by

Re: [WiX-users] RemoveFolderEx really slow on large folders

Fri, May 9, 2014 at 10:31 AM, Jeremy Farrell wrote: > How does rollback work with your CA? > > > From: Sascha Sertel [mailto:sascha.ser...@gmail.com] > > > > Yes, what it is getting hung up on is enumerating a hundred > > thousand files one by one and adding them up

Re: [WiX-users] RemoveFolderEx really slow on large folders

Yes, what it is getting hung up on is enumerating a hundred thousand files one by one and adding them up to a giant string that is passed on to the MSI engine. I looked at the RemoveFolderEx C++ implementation and it confirmed all my suspicions, so I went ahead and took it out and created my own m

Re: [WiX-users] WiX 3.8 Installer and NetFx 4.5.2 on Win7 x64

How are you installing .NET 4.5.2? The WiX 3.8 NetFxExtension does not contain a wxs for NetFx452, so I'm assuming you manually specify an ExePackage element for 4.5.2? Since .NET 4.5.2 was just released a couple of days ago I'm sure there aren't a lot of people who have tried to deploy it with Wi

[WiX-users] RemoveFolderEx really slow on large folders

Hi there, I'm using the util:RemoveFolderEx custom action to remove a folder during uninstall that contains temporary files that are no longer needed (think of it as a browser cache for example). Due to the nature of the application the number of files in the folder can be in the thousands. I not

Re: [WiX-users] Difference between [#FileId] and [!FileId] reference?

Ok, so it's an MSI thing, thanks Phil! Still interesting that I don't get any ICE warnings when using [!filekey] for the shortcut target property, since according to MSDN it should be treated like [#filekey]. Also happy to learn about [$filekey] to get the directory of the file path only. That'll

[WiX-users] Difference between [#FileId] and [!FileId] reference?

Hey guys, in my WiX generated MSI installer I am creating a bunch of shortcuts, in which I was using the proven Target="[#FileId]" notation where FileId is of course the Id given to a file installed by a different component. Everything works fine, and I'm seeing the (expected) ICE warning: warn

Re: [WiX-users] Visual Studio 2013

t 10:23 AM, Corby Nichols wrote: > Where would I find the "Templates Option"? > > I have Installed, Online, & Recent: > > Under Online, I have a 'Templates' option, but it does not have Windows > Installer XML; > > > > > > -Origi

Re: [WiX-users] Visual Studio 2013

No when you install WiX 3.8 it also installs the project templates. You should be able to find them in the New Project dialog under Templates -> Windows Installer XML. Make sure you restart Visual Studio after installing WiX so it picks up the new templates. // Sascha On Fri, Apr 4, 2014 at 8:3

[WiX-users] ExecuteFilesInUseEventArgs Question

Hey everybody, I'm working on a custom managed bootstrapper application for my bundle and I'm adding support for the ExecuteFilesInUse event. While doing some testing I noticed that the Files property does not actually return a list of files that are locked, but rather alternates between process

Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper

To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and > Bootstrapper > > So per users can installer to C:\Program Files\ ? > > -Original Message- > From: Sascha Sertel [mailto:sascha.ser...@gmail.com] > Sent:

Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper

No I did not set ALLUSERS directly. On Fri, Jan 24, 2014 at 2:32 PM, Rob Mensching wrote: > Did you have ALLUSERS set the whole time as well? > > -Original Message- > From: Sascha Sertel [mailto:sascha.ser...@gmail.com] > Sent: Friday, January 24, 2014 2:21 PM > To:

Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper

ou on a fork of this thread that found > the most important thing: You need to make sure your per-user package is > truly per-user. The easiest way to do that is to use: > Package/@InstallScope='perUser'. > > -Original Message- > From: Sascha Sertel [mailto:sasch

Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper

ll > it automatically translates to LocalAppDataFolder instead." > > I think Vista maybe but I think windows 7 doesn't do that. Don't > quote me. I just vaguely remember reading something about that. Maybe > someone else can chime in. > >

Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper

Let me clarify a bit to tell you what I'm trying to do, what I've tried, and what I thought isn't currently working: Goal: Build a WiX installer for my software which installs .NET Framework 4.5.1 if needed, C++ Runtime if needed, and my software. My software needs to be installed per-user, i.e. i