We started out today by logging the file accesses and came up with
some odd results that we're not sure what to make of... If you interpret
the good log file, you see that three different msiexec processes
access the file one after the other. However, the bad log file shows
that one of the
corrupt. Check
with IE or Visual Studio that it is still a well-formed XML file.
--
Mike Dimmick
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric Fesh
Sent: 06 October 2006 19:55
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Odd failure
Yeah, I miscopied it. Our resident Windows guy knew the trick about converting
to Hex (I'm mostly a Linux/Java guy, so I was totally unaware of that.). The
code in hex is 0x8007006E. He thought it might be two processes trying
to access the file at the same time, but I'll check up on
Well, I'm out of ideas. Here's some of the things I've tried...
1) Made sure that I was running the installer as administrator.
2) Made sure that the file was in DOS/Windows format by converting the file.
Tried several variations of this including passing it through a perl script and
All:
I'm having an odd issue with XmlFile on a machine running Windows2003
Enterprise... The machine has an Intel Woodcrest/Greencreek chipset and is
running a RAID as C:\ (although the machine also has a D:\ which this also
happens on). I mention these because I have no rational explanation
At the risk of spamming you all:
I asked one of our guys here, and his guess is that two processes are trying to
access the file at the same time... I'm trying to figure out how that could be
as the only custom action related to it is SchedXmlFile... I guess that figures
out where to sequence
Eric Fesh wrote:
Failed to open XML file
C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf, system error:
-214704786
Which version of WiX are you using? That string isn't in the current
builds, so I can't see where the error is happening.
--
sig://boB
http://bobs.org
7 matches
Mail list logo
