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 processes (608) tries to access the file again after the presumed ExecXmlFile process (3576) has opened it.
At this point this may be more of a .NET or Windows Installer question, but does anyone have any suggestions on what else I might try? On the machines where the install is successful, the log looks like this: 1 11:56:59 AM msiexec.exe:2956 QUERY INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf PATH NOT FOUND Attributes: Error 2 11:57:01 AM msiexec.exe:972 QUERY INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf PATH NOT FOUND Attributes: Error 3 11:57:01 AM msiexec.exe:972 QUERY INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf PATH NOT FOUND Attributes: Error 4 11:57:05 AM msiexec.exe:972 QUERY INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf PATH NOT FOUND Attributes: Error 5 11:57:05 AM msiexec.exe:972 QUERY INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf PATH NOT FOUND Attributes: Error 6 11:57:05 AM msiexec.exe:972 QUERY INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf PATH NOT FOUND Attributes: Error 7 11:57:05 AM msiexec.exe:972 QUERY INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf PATH NOT FOUND Attributes: Error 8 11:57:05 AM msiexec.exe:972 QUERY INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf NOT FOUND Attributes: Error 9 11:57:05 AM msiexec.exe:972 QUERY INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf NOT FOUND Attributes: Error 10 11:57:05 AM msiexec.exe:972 CREATE C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf SUCCESS Options: OverwriteIf Access: 00120196 11 11:57:05 AM msiexec.exe:972 WRITE C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf SUCCESS Offset: 0 Length: 505 12 11:57:05 AM msiexec.exe:972 SET INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf SUCCESS FileBasicInformation 13 11:57:05 AM msiexec.exe:972 CLOSE C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf SUCCESS 14 11:57:15 AM msiexec.exe:3740 OPEN C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf SUCCESS Options: Open Access: Read 15 11:57:15 AM msiexec.exe:3740 READ C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf SUCCESS Offset: 0 Length: 4095 16 11:57:15 AM msiexec.exe:3740 READ C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf END OF FILE Offset: 505 Length: 8178 17 11:57:15 AM msiexec.exe:3740 CLOSE C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf SUCCESS 18 11:57:15 AM msiexec.exe:3740 OPEN C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf SUCCESS Options: Open Access: 00120196 19 11:57:15 AM msiexec.exe:3740 WRITE C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf SUCCESS Offset: 0 Length: 510 20 11:57:15 AM msiexec.exe:3740 SET INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf SUCCESS Length: 510 21 11:57:15 AM msiexec.exe:3740 SET INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf SUCCESS Length: 510 22 11:57:15 AM msiexec.exe:3740 FLUSH C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf SUCCESS 23 11:57:15 AM msiexec.exe:3740 WRITE C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf SUCCESS Offset: 0 Length: 4096 24 11:57:15 AM msiexec.exe:3740 CLOSE C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf SUCCESS On the machines where the install is not successful, the log looks like this: 10636 12:50:08 PM msiexec.exe:3448 QUERY INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf PATH NOT FOUND Attributes: Error 14491 12:50:08 PM msiexec.exe:608 QUERY INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf PATH NOT FOUND Attributes: Error 14512 12:50:08 PM msiexec.exe:608 QUERY INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf PATH NOT FOUND Attributes: Error 17697 12:50:11 PM msiexec.exe:608 QUERY INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf PATH NOT FOUND Attributes: Error 17698 12:50:11 PM msiexec.exe:608 QUERY INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf PATH NOT FOUND Attributes: Error 17699 12:50:11 PM msiexec.exe:608 QUERY INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf PATH NOT FOUND Attributes: Error 17700 12:50:11 PM msiexec.exe:608 QUERY INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf PATH NOT FOUND Attributes: Error 17710 12:50:11 PM msiexec.exe:608 QUERY INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf NOT FOUND Attributes: Error 17717 12:50:11 PM msiexec.exe:608 QUERY INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf NOT FOUND Attributes: Error 17718 12:50:11 PM msiexec.exe:608 CREATE C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf SUCCESS Options: OverwriteIf Access: 00120196 17719 12:50:11 PM msiexec.exe:608 WRITE C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf SUCCESS Offset: 0 Length: 505 17720 12:50:11 PM msiexec.exe:608 SET INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf SUCCESS FileBasicInformation 17721 12:50:11 PM msiexec.exe:608 CLOSE C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf SUCCESS 35041 12:50:14 PM msiexec.exe:3576 OPEN C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf SUCCESS Options: Open Access: Read 35042 12:50:14 PM msiexec.exe:3576 READ C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf SUCCESS Offset: 0 Length: 4095 45027 12:50:24 PM msiexec.exe:608 QUERY INFORMATION C:\Program Files\Verari Systems\VCC\OSMon\config\vcc.conf PATH NOT FOUND Attributes: Error -- 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: > 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 ------------------------------------------------------------------------- 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
