Ahh...whoops...I think I invoked a build at the same time as that particular error. But that still doesn't address the problem I consistently see when I increase the overall MSI size (with multiple cabs of < 2GB size) seems to be > 2GB...
filenames and paths removed to protect the innocent. =) Microsoft (R) Windows Installer Xml Linker version 2.0.4820.0 Copyright (C) Microsoft Corporation 2003. All rights reserved. Updating file information. Generating database. Merging modules. Processing media information. Cabbing file xxx from 'xxx'. Cabbing file xxx from 'xxx'. Cabbing file xxx from 'xxx'. Cabbing file xxx from 'xxx'. Cabbing file xxx from 'xxx'. Cabbing file xxx from 'xxx'. Cabbing file xxx from 'xxx'. Cabbing file xxx from 'xxx'. Importing streams. Importing cabinet stream 'xxx.cab' from '<pathremoved>\Temp\gblw976s\xxx.cab'. Importing cabinet stream 'xxx.cab' from '<pathremoved>\Temp\gblw976s\xxx.cab'. Importing cabinet stream 'xxx.cab' from '<pathremoved>\Temp\gblw976s\xxx.cab'. light.exe : warning LGHT1011 : Access denied; cannot delete '<pathremoved>\Temp\gblw976s'. Warning, failed to delete temporary directory: <pathremoved>\Temp\gblw976s light.exe : error LGHT0001 : Failed to Commit database Exception Type: System.Runtime.InteropServices.ExternalException Stack Trace: at Microsoft.Tools.WindowsInstallerXml.Binder.ImportStreams(String databasePath, Output output) at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output) at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args) On Tue, 30 Jan 2007 13:13:04 -0800, "Rob Mensching" <[EMAIL PROTECTED]> said: > 0x80070020 is SHARING_VIOLATION. Do you have a virus scanner watching > the built files? That's the way this happens most often. Virus scanners > are notorious for locking up compressed files. I always exempt the build > drives from our virus scanners. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Alex Lian > Sent: Tuesday, January 30, 2007 12:02 PM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Any documentation on WiX/Windows Installer > limits? > > > I'm not exceeding any of those statements. > All files are *individually* < 2GB, and I'm setting up multiple cabs > such that none exceed 2GB. I'll double check my wxs file, but I'm pretty > sure I tried to verify that. > I got this error when I did exceed that: > > light.exe : fatal error LGHT0017 : Failed to create cab '<path > removed>\Temp\kq9kbz9g\client_base.cab' while cabbing file '<filename > removed>' with error 0x80070020. > > So, it seems more like I have problems when light tries to re-open the > msi file after adding the cabs in... > > -Alex > > > On Tue, 30 Jan 2007 09:39:32 -0800, "Rob Mensching" > <[EMAIL PROTECTED]> said: > > The FileSize column in the File table has a datatype of "DoubleInteger". > > From the documentation: > > > > "The DoubleInteger data type is a four-byte integer value. Unless > > otherwise restricted, the range of legal values is from -2,147,483,647 to > > +2,147,483,647." > > > > Also, it is a known issue that cabinet files cannot handle more than ~2 > > GB of data in a single cabinet. > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Alex Lian > > Sent: Tuesday, January 30, 2007 9:03 AM > > To: wix-users@lists.sourceforge.net > > Subject: Re: [WiX-users] Any documentation on WiX/Windows Installer > > limits? > > > > > > Ahh...that makes sense (with also additionally experimenting by me > > confirming some of that). > > So, I'm still experimenting - splitting up the files across cabs/media - > > but light.exe > > seems to choke on the large MSI it outputs in the temp directory. > > > > I see this error: > > light.exe : error LGHT0001 : Failed to open database: C:\<path > > removed>\Temp\jjua6pkf\<filename removed>.msi > > > > Exception Type: System.Runtime.InteropServices.ExternalException > > > > Stack Trace: > > at Microsoft.Tools.WindowsInstallerXml.Msi.Database.Open(String path, > > OpenDat > > abase type) > > at Microsoft.Tools.WindowsInstallerXml.Binder.GenerateDatabase(Output > > output) > > > > at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output) > > at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args) > > > > If I pare off some of the larger files (> 1GB each) it seems to be able > > to create a ~2GB installer, > > but it chokes when I add the next file. Any thoughts before I start code > > diving in light.exe? > > Is light.exe hindered at some file size? > > > > -Alex > > > > > > On Sun, 28 Jan 2007 20:07:45 -0800, "Rob Mensching" > > <[EMAIL PROTECTED]> said: > > > Cabinet files (the compression technology used by the Windows Installer) > > > can currently only handle up to 2GB. Unfortunately, with Merge Modules > > > you only get one cabinet. However, for MSI files you can split your > > > product into multiple cabinets (separate Media elements) to get around > > > the problem. > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On Behalf Of Alex Lian > > > Sent: Sunday, January 28, 2007 7:30 PM > > > To: wix-users@lists.sourceforge.net > > > Subject: [WiX-users] Any documentation on WiX/Windows Installer limits? > > > > > > I've been googling for the spec somewhere (as well as about the tools) > > > > > > What's the file size limitations of wix? I seem to be able to create the > > > .msm with 4 files > > > totalling 3.4GB though it seems unnaturally compressed down to 805MB. > > > > > > However, in trying to create a final .msi using this .msm, yields an > > > E_ABORT error trying > > > to access the msm file. Orca can seem to open it fine, but I'm having > > > trouble trying to > > > re-extract the files at the moment. > > > > > > So... > > > > > > any pointers to docs/info on limits? > > > > > > I'm sure I'm still doing something amiss, and I'll keep struggling on > > > it. > > > > > > -Alex > > > > > > ------------------------------------------------------------------------- > > > 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 ------------------------------------------------------------------------- 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
