Thanks Phil, I'll take a look when I get a chance. I have a feeling it's still in the hash table.
Thanks again. On 30 May 2013 19:28, Phil Wilson <phil.wil...@mvps.org> wrote: > Have a look at the "vital" setting for the file. You may find it's not > vital > in the "Info" message case. > > MSI File table: > > > http://msdn.microsoft.com/en-us/library/windows/desktop/aa368596(v=vs.85).as > px > > If the file is external and you are replscing it at the last moment make > sure you don't make a file hash mistake. You don't want the hash in the MSI > file to not match the actual file, so turn it off for that file unless you > are fixing the MsiFileHash table when you replace the file. > > Phil > > -----Original Message----- > From: John Ludlow [mailto:john.ludlow...@gmail.com] > Sent: Thursday, May 30, 2013 6:08 AM > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Error 1308 (Source File not found) emitted as Info on > upgrade > > Hi, > > I have one MSI, with a bunch of compressed files in an embedded cab, and > one > readme next to the install as an uncompressed file. This file is still in > the installer, it's just got the nonCompressed bit set. This is so we can > update the readme right up until release with late-breaking information. > > This all works fine for fresh installs and upgrades, as long as that file > is > present. I that file is not present, we get this: > > Error 1308. Source file not found: > C:\Users\Neil.Owen\Desktop\10.0.4.1157\ReadMeFirst_EN.htm. Verify that the > file exists and that you can access it. > That makes perfect sense. > > The issue is that this is not happening on upgrade. What's happening on > upgrade if the readme file is missing is that the same error is being > published as an Info message, and the install carries on merrily: > > Info 1308. Source file not found: > C:\Users\Neil.Owen\Desktop\10.0.4.1157\ReadMeFirst_EN.htm. Verify that the > file exists and that you can access it. > There's a few ways we can work around this (either not having the file > uncompressed like this or by having an action which checks for the presence > of the file). However, what I'd like to understand is why MSI is turning > this Error message into an Info message on upgrade. > > Any ideas? > > Thanks > > ---------------------------------------------------------------------------- > -- > Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get > 100% visibility into your production application - at no cost. > Code-level diagnostics for performance bottlenecks with <2% overhead > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap1 > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > ------------------------------------------------------------------------------ > Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET > Get 100% visibility into your production application - at no cost. > Code-level diagnostics for performance bottlenecks with <2% overhead > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap1 > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
