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 cutting/pasting the file contents into a Notepad session. 3) Attempted to make sure that the file was in UTF-8 format since that's what the header on the XML declares it as. 4) Removed the UTF-8 format declaration in case the file wasn't in UTF-8. 5) Tried several tools to validate the XML in vcc.conf. The results were iffy, but I'm positive that's because the validators themselves were no good. I downloaded a professional-quality XML editor on a trial basis and it told me the file was fine. 6) Tried updating the Microsoft XML parser. 7) Tried removing the custom action that starts the OSMon service at the end of the install in case that was locking the file before the XML editing custom action could edit it. 8) Tried removing the file from the installation to see if the installer could open the file if it was already on disk (in theory, this should have eliminated the Windows Installer service as a process that might have a lock on the file). 9) Hardcoded the path to the file in case the variable specification I used was causing issues. 10) Tried removing the comments in the file. 11) Tried removing the comments and entries in the file.\ 12) Tried removing everything but the XML header from the file. 13) Tried using an empty file. *shrug* Guess I'll need to find an alternate solution of some sort. -- Eric Fesh Customer Support Engineer/Software Test Engineer Verari Systems Software, Inc. 110 12th Street North, Suite D103 Birmingham, AL 35203 Phone +1-205-397-3141 ext. 3149 Fax +1-205-397-3142 [EMAIL PROTECTED] http://www.verarisoft.com/ The information contained in this communication may be confidential and is intended only for the use of the recipient(s) named above. If the reader of this communication is not the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you are not a named recipient or received this communication by mistake, please notify the sender and delete the communication and all copies of it. Eric Fesh wrote: > 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 0xFFFFFFFF8007006E. He thought it might be two processes > trying > to access the file at the same time, but I'll check up on the validity of the > .conf file. What I don't understand is if it's a parse error, why does it > only > happen on specific machines...? > > Weirding me out, I tells ya. > > -- > > Eric Fesh > Customer Support Engineer/Software Test Engineer > Verari Systems Software, Inc. > 110 12th Street North, Suite D103 > Birmingham, AL 35203 > Phone +1-205-397-3141 ext. 3149 > Fax +1-205-397-3142 > [EMAIL PROTECTED] > http://www.verarisoft.com/ > > The information contained in this communication may be confidential and is > intended only for the use of the recipient(s) named above. If the reader of > this communication is not the intended recipient(s), you are hereby notified > that any dissemination, distribution, or copying of this communication, or > any of its contents, is strictly prohibited. If you are not a named > recipient or received this communication by mistake, please notify the sender > and delete the communication and all copies of it. > > > Mike Dimmick wrote: >> You're missing a digit from that error number. It should have ten digits to >> map to an error HRESULT. I normally convert large negative numbers back to >> hex, then if the upper WORD is 0x8007, I know it's a Win32 error code mapped >> into an HRESULT (FACILITY_WIN32 is 7). The error return of >> XmlLoadDocumentFromFile if IXMLDOMDocument::load returns S_FALSE is set to >> (HRESULT mapped) ERROR_OPEN_FAILED, which is 0x8007006E (-2,147,024,786). >> Assuming that is the error code returned, there could be a parsing error. >> >> XmlLoadDocumentFromFile has the beginnings of code to report a parsing error >> but it's commented out. The XmlReportParseError function referenced in the >> commented-out code isn't implemented. You could implement such a function, >> uncomment the call and recompile wixca.dll to find out better information >> about why it's failing. >> >> My guess would be that the existing .conf file is somehow corrupt. Check >> with IE or Visual Studio that it is still a well-formed XML file. >> > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
