[WiX-users] Setting MsiLogFileLocation property

Hello, I need to enable verbose logging and configure MSI log file location. I am currently doing this by adding the following properties inside of my .wxs file: 1 x:/WIX/wix-msi.log ... Is this the right place for these properties? If so, then I am assuming that the reason why they are

Re: [WiX-users] SetInstallLevel Control Event in Maintenance

Of course right after I posted this I came across an old thread between Stefan Krueger and Bob Arnson saying that MSI doesn't appear to support this even though the SDK doesn't actually spell it out. I assume I'll have to manipulate the features directly using AddLocal and REMOVE as a feature

[WiX-users] SetInstallLevel Control Event in Maintenance

I have an installer that has a "setup type" story that drives the INSTALLLEVEL property through the use of SetInstallLevel control events. During the initial installation everything works as expected. Now I've been asked to show this dialog again during the maintenance UI. I can see in the

Re: [WiX-users] Running a single MSI on the same machine more than once concurrently

We have a webservice package and a database package. We run the webservice package one 1 or more servers while we only run the database package on a single server. We started with a single package that installed both. That caused problems because we could not choose separately when to deploy th

Re: [WiX-users] Running a single MSI on the same machine more than once concurrently

Hi >From experience of shipping to customers an installer that can do both >scenarios, the two part install might be intuitive, but it's a right pain in >practice. I now avoid doing the two part installs if at all possible. Also the single install location is generally much easier if the data

Re: [WiX-users] Running a single MSI on the same machine more than once concurrently

Understood. Which actually illustrates why it can make sense to split the database setup from the main install because one day you might want to relocate the database and reconfigure the application server and it might be difficult if only the installer knows how to service the database. Stil

Re: [WiX-users] Running a single MSI on the same machine more than once concurrently

The requirement is for the MSI to be run on a deployment server no matter what environment is targeted. So the user does not need to logon to a test server or a UAT server first and then run the MSI: they can always logon to the deployment server and pass in the target environment server. -

Re: [WiX-users] Running a single MSI on the same machine more than once concurrently

Application on the server farm and database on a (separate) database server is the norm for my applications. Reality is that the database servers aren't even generally in the same physical location as the server farm, and the installing account on the server farm only has just enough rights to

Re: [WiX-users] Running a single MSI on the same machine more than once concurrently

I've often wondered this myself and designed my installer per customer requirements. I agree, it seems wierd to have MSI state data on one machine registering resource data on another machine. Still, it does work in situations where the person doing the installer has DBA rights on the instance

Re: [WiX-users] Running a single MSI on the same machine more than once concurrently

Can I ask why you aren't installing this on the database server itself? I still see the need for instance transforms as you could have multiple database instances locally, but it seems counter intuitive to me to have an installer registered on one machine with the actual payload on a different mach

Re: [WiX-users] ICE64 Validation - Bug?

Looks like you're doing a perMachine install but using perUser directories. Usually, such an install is done perUser. ICE is a validation process. It's warning you that you have an installer that violates the perMachine/perUser expectations. It's not related to run time errors. -- John Merr

[WiX-users] ICE64 Validation - Bug?

If I don't check "Supress ICE Validation" - I get an ICE64 as shown below. I can't seem to get rid of it no matter what I try. I don't get the ICE64 error when I run the installer. Error 310 ICE64: The directory AppData_Microsoft is in the user profile but is not listed in the RemoveFil

Re: [WiX-users] Running a single MSI on the same machine more than once concurrently

Cheers, Rob. Looks just what I am after so I'll give it a go. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 14 March 2012 15:08 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Running a single MSI on the same machine more tha

Re: [WiX-users] Running a single MSI on the same machine more than once concurrently

The Windows Installer supports this using "instance transforms". You can read about them in the MSI SDK and see the InstanceTransform element in WiX. On Wed, Mar 14, 2012 at 5:25 AM, Paul Taylor wrote: > Hi all, > > Newbie question: > > I am working on a WiX project to deploy SQL Server databases

[WiX-users] WiX 3.6.2712.0 - WriteIIS7ConfigChanges: Error 0x80071a90 on Windows Server 2008 R2.

Hi, On a Windows Server 2008 R2 we once in a while get the following error: MSI (s) (F8:28) [11:11:47:419]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI833C.tmp, Entrypoint: WriteIIS7ConfigChanges WriteIIS7ConfigChanges: Entering WriteIIS7ConfigChanges in C:\Windows\Inst

[WiX-users] Running a single MSI on the same machine more than once concurrently

Hi all, Newbie question: I am working on a WiX project to deploy SQL Server databases to different environments and one of the requirements is the above. So the build process generates one MSI which is then executed on a deployment server passing the target server in as a variable. Two questio