As Bruce notes second, the log file in %TEMP% is the fastest way to figure out what went wrong.
On Wed, Nov 16, 2011 at 5:03 AM, Bruce Cran <br...@cran.org.uk> wrote: > On 16/11/2011 12:06, Harper wrote: > > What's wrong? How can I get information, why it failed? And how can this > be > > fixed? One thing that's different from a successful installation is that > it > > failed on a computer that's a member of a domain. But I am not aware of > > policies that disallow software installation. > > > > How do I get WiX 3.6 installed? > > One way it can fail is if Windows Installer has any reboots pending - > for example if you've installed something previously that wanted to > reboot and you clicked "No". Otherwise, you could check in the logs it > produces by default (i.e. logging is enabled by default) in %TEMP% . > > -- > Bruce Cran > > > ------------------------------------------------------------------------------ > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
