It looks to me from the log that somehow INSTALLDIR wasnt actually set
there is no path given in the error message, so it will depend on what the
current directory is at the time of execution.
INSTALLDIR isnt a standard property could it be that you need to list it
in SecureCustomProperties?
Also, I still fail to understand why people use their own INSTALLDIR
property rather than using TARGETDIR properly setting it to a location
under ProgramFilesFolder, for example. Ive just observed that if you dont
do anything to the contrary, ROOTDRIVE is initialised to the local disk with
the most free space and TARGETDIR is initialised to ROOTDRIVE. It seems a
much better idea to place your files directly in TARGETDIR and use a type 51
custom action to set TARGETDIR to [ProgramFilesFolder]\MyProductNameHere, if
TARGETDIR is not already set.
--
Mike Dimmick
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Albert van
Peppen
Sent: 04 July 2007 08:49
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Failed to open XML file on Vista
Hi,
Finally found the problem (although it was away since 11 may 2007 because of
changes in my wxi file)..
It turned out that it has nothing to do with Office or anything on Vista.
The message appears when you don't have any XmlFile entries in your wxi
script but has an action scheduled as After="XmlSched".
This implies XmlSched CA is used and so it is placed in the
InstallExecuteSequence but since it has nothing to do, it seems to generates
the error because it's trying to open an empty file (which is indeed an
invalid XML file).
I think it would be an idea to generate a warning / error on this in the
linker (light.exe) or , better yet, the linker should optimize this; Build
the sequence list and before writing to the MSI table, check all CA /
Actions are really used, if not drop them from the list :)
I don't know what WiX 3.0 does with the above problem, i still use WiX 2.0
because it's stable. As soon WiX 3.0 is stable enough i will switch :-)
Regards,
Albert van Peppen
_____
Van: Rob Mensching [mailto:[EMAIL PROTECTED]
Verzonden: zaterdag 12 mei 2007 19:17
Aan: Albert van Peppen; Wix-Devs
Onderwerp: RE: [WiX-users] Failed to open XML file on Vista
No idea. You might use FileMon to watch the access to the file to see what
happens and why the system is messing with your file.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Albert van
Peppen
Sent: Friday, May 11, 2007 4:59 AM
To: Wix-Devs
Subject: Re: [WiX-devs] [WiX-users] Failed to open XML file on Vista
Hi,
I tried again on this notebook; now it works without any problem :(
The only thing done on this notebook since the problem was reproducable is
that now Office 2003 Pro is installed;
Doing so gave the (well known?) error 1913.
After google-ing on this i found a solution at:
http://phaq.phunsites.net/?p=91
I did follow this solution only partionally; I just made the administrators
group owner of the system32 folder. That did the trick for Office 2003 Pro.
Since the MSXML dlls are located in the system32 folder this might be the
'solution' to this?
Although i don't fully understand why this is like this; and thus causeing
the problem with installing Office 2003 Pro.
I'll try to setup a clean Vista out of the box on another machine to
validate this is causing my installer to run well..
Maybe you have more insight in this (known issues with such things ?)
Regards,
Albert van Peppen
_____
Van: Rob Mensching [mailto:[EMAIL PROTECTED]
Verzonden: vrijdag 11 mei 2007 6:40
Aan: Albert van Peppen
Onderwerp: RE: [WiX-users] Failed to open XML file on Vista
Okay, tried this install on Vista. Worked exactly as expected. Im not
sure what problem you are seeing.
The ExecXmlFile CustomAction is running in the elevated CustomAction Server
so it is elevated as well.
From: Albert van Peppen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 09, 2007 6:56 AM
To: Rob Mensching
Subject: RE: [WiX-users] Failed to open XML file on Vista
We don't ACL any files. The XML file is just installed by the MSI installer
in elevated mode.
The user running the installer has least user access (LUA).
It is possible to log in what user state runs the COM InProc server, i doubt
the COM is indeed called in any elevated state..
The mentioned problem also exists on XP with a very restricted user, so it
is not just a Vista problem, but we've found it first in Vista so we thought
it was a problem in/with Vista.
Can you checked the issue yourself?
I am willing to try and change some things in the WiX sources; just to see
i'm right ;) But it seems a bit of task to get the WiX sources compiling..
(At least at this moment)
Regards,
Albert van Peppen
_____
Van: Rob Mensching [mailto:[EMAIL PROTECTED]
Verzonden: woensdag 9 mei 2007 15:36
Aan: Albert van Peppen; Wix-Devs
Onderwerp: RE: [WiX-users] Failed to open XML file on Vista
The ExecXmlFile is already running in an elevated process so the elevation
moniker should be unnecessary. Besides, the fact that youre failing when
running as a local administrator means that UAC is not the issue. It looks
like the problem is somehow related to the file only being accessible by the
domain administrator. Did you ACL the file down such that only the domain
admin can access it?
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Albert van
Peppen
Sent: Wednesday, May 09, 2007 5:58 AM
To: Wix-Devs
Subject: Re: [WiX-devs] [WiX-users] Failed to open XML file on Vista
Hi,
I posted this though to wix-dev since i believe the problem lies in WiX.
When looking at the source coude i found that XmlFile is useing the MSXML
COM object.
This is done by calling ::CoCreateInstance().
When looking into ::CoCreateInstance() and COM and Elevation i found that
you should use a Elevation Moniker.
Check at MSDN: http://msdn2.microsoft.com/en-us/library/ms679687.aspx
I also found that more ::CoCreateInstance() calls might be affected due to
the missing elevation.
Can you guys at the Dev team look at this asap since it it is really a
stopper for me! (I think Bob is the guy for this ;) )
As said, i am using WiX 2.0.5213.0. I think is worth a new release for WiX
2.0 ??
Regards,
Albert van Peppen
_____
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Namens Albert van Peppen
Verzonden: woensdag 2 mei 2007 15:17
Aan: wix-users@lists.sourceforge.net
Onderwerp: [WiX-users] Failed to open XML file on Vista
Hi,
I try to install a XML file through my WiX Installer.
On WinXP i have no problems.
On Windows Vista (Business Edition), client in a Win2003 AD network, i have
some strange problems;
- Installing as a domain administrator gives no problems.
- Installing as a local administrator gives an error; installation fails.
- Installing as a local or domain user with restricted rights gives an
error; installation fails.
- Installing with elevated rights / run as gives an error; installation
fails. (With the exception of Run As domain Administrator)
In all cases where the installation fails the following error appears:
'Failed to open XML file WInsad.xml, system error: -2147024786'
The logfile shows:
MSI (s) (18:E0) [12:50:19:270]: Running as a service.
MSI (s) (18:E0) [12:50:19:317]: Hello, I'm your 32bit Elevated custom action
server.
MSI (s) (18!68) [12:50:19:364]: Creating MSIHANDLE (4645) of type 790531 for
thread 4456
ExecXmlFile: Error 0x8007006e: failed to load XML file: WInsad.xml
MSI (s) (18!68) [12:50:19:489]: Closing MSIHANDLE (4645) of type 790531 for
thread 4456
MSI (s) (18!68) [12:50:19:536]: Creating MSIHANDLE (4646) of type 790531 for
thread 4456
Fout 25531. Failed to open XML file WInsad.xml, system error: -2147024786
MSI (s) (18!68) [12:52:31:146]: Product: Drumis - Programma V2.90.2267.0 --
Fout 25531. Failed to open XML file WInsad.xml, system error: -2147024786
MSI (s) (18!68) [12:52:31:177]: Closing MSIHANDLE (4646) of type 790531 for
thread 4456
MSI (s) (18:10) [12:52:31:208]: Closing MSIHANDLE (4644) of type 790536 for
thread 3812
Actie beëindigd 12:52:31: InstallExecute. Retourwaarde 3.
The following piece of code is what i use in WiX:
<!-- ===== WInsad.xml = License file ===== -->
<DirectoryRef Id="INSTALLDIR">
<Component Id="WInsad.dat" Guid="xxxxxxxx-xxxx-xxx-xxx-xxxxxxxxxxx">
<File Id="File_WInsad.dat" Name="WInsad.dat" DiskId="1"
Source="$(var.MyApplicationSourcePath)\WInsad.dat" Vital="yes" />
</Component>
<Component Id="WInsad.xml" Guid="xxxxxxxx-xxxx-xxx-xxx-xxxxxxxxxxy">
<File Id="File_WInsad.xml" Name="WInsad.xml" DiskId="1"
Source="$(var.DrumisApplicationSourcePath)\WInsad.xml" Vital="yes" />
<XmlFile Sequence="10" Id="Winsad.xml_License"
File="[INSTALLDIR]WInsad.xml" Action="createElement" Name="License"
ElementPath="//WInsad" />
<XmlFile Sequence="11" Id="Winsad.xml_LicenseType"
File="[INSTALLDIR]WInsad.xml" Action='setValue' Name='type'
Value='Demo' ElementPath='//WInsad/License' />
</Component>
</DirectoryRef>
<!-- Features -->
<FeatureRef Id="MainFeature">
<ComponentRef Id="WInsad.dat" />
<ComponentRef Id="WInsad.xml" />
</FeatureRef>
The initial WInsad.xml file is installed on the targetsystem before the
error. It initially looks like:
<?xml version="1.0" encoding="windows-1252"?>
<WInsad>
</WInsad>
The WiX version used in Wix-2.0.5213.0
Am i doing something wrong or is it something with Wix-2 / Vista?
The InstallerVersion in the Package is set to "200", the InstallerPrivileges
is set to "elevated".
Any help is welcome.
Regards,
Albert van Peppen
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
