File size limit to add to MSI?
Hi,
I am delivering 4 files to c:\program files\vendor\<files>
I'm using Installshield 2011, Win 7 64 bit.
One of the files is 7 gig, due to the 2 gig limit to a cab file, I have the msi as an uncompressed external files. When I install I have the following error:
Product: VendorFile -- Error 1310.Error writing to file: C:\Program Files (x86)\vendor\<largeFile> System error 131. Verify that you have access to that directory.
If I take the large file out an dinstall the MSI it installs the other (smaller) files.
Is there a limit to file size?
If I can't get the MSI to deliver the file, I'm thinking of using an AD policy to deliver or a Custom Action in the MSI to map to the network share and copy the file.
Thanks...
I am delivering 4 files to c:\program files\vendor\<files>
I'm using Installshield 2011, Win 7 64 bit.
One of the files is 7 gig, due to the 2 gig limit to a cab file, I have the msi as an uncompressed external files. When I install I have the following error:
Product: VendorFile -- Error 1310.Error writing to file: C:\Program Files (x86)\vendor\<largeFile> System error 131. Verify that you have access to that directory.
If I take the large file out an dinstall the MSI it installs the other (smaller) files.
Is there a limit to file size?
If I can't get the MSI to deliver the file, I'm thinking of using an AD policy to deliver or a Custom Action in the MSI to map to the network share and copy the file.
Thanks...
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
andys0123
12 years ago
Does the file zip to < 2Gb? If so add the zip & include Custom Action to unzip with Winzip or 7zip command line tools. Remember to add entry to RemoveFile table for the uninstall.
Posted by:
blacklisted_packager
12 years ago
The file size in filetable is Double Int so the maximum size supported should be 2GB
Posted by:
anonymous_9363
12 years ago
7Gb in a single file? That sounds like an application design issue to me!
If the file is already on a network share, why is there a need to copy it locally? If it's a database, my guess is that it's a Microsoft Access-based one, in which case you are R E A L L Y playing with fire with a file of that size. Migrating it to SQL Server should be right up there on your priority list.
If the file is already on a network share, why is there a need to copy it locally? If it's a database, my guess is that it's a Microsoft Access-based one, in which case you are R E A L L Y playing with fire with a file of that size. Migrating it to SQL Server should be right up there on your priority list.
Posted by:
Meic
12 years ago
Thanks for your replies - yup, definate an application design issue! A pre-req piece of software the client uses would only work with a databse when it was on a local drive.
The client are now looking for alternatives...
The client are now looking for alternatives...
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.