setup project can not build
Hi, I am using vs 2003 to build a setup project but got this error message
"Could not find file ..., Not enough storage is available to complete this operation."
I checked the path of the file, it is correct. After I remove this file from the setup project, I can build it successfully and the result msi file is about 250MB, the file I removed is about 260MB, is there any limitation about the size of the file in setup project or the total size of msi file? If so, how can I build the setup project?
I appreciate your help.
Hi Snow Bear -
Where are you trying to build the file? It sounds like there isn't enough disk space to build it - you might check the amount of free space on the drive where it is being built, or try changing the path to another drive with more than 510MB free space.
Hope this helps,
the V-Bee
Hi, V-Bee:
Thanks for your reply. For some reason I did not receive alert from the forum about your response. I checked the forum today and find your reply.
I am building the project on the hard drive, inside the main project folder there is a setup project folder. The msi file is created inside the release folder of the setup folder. The hard drive should have enough space, it is a new machine with 2G RAM and 300G HDD, I checked the free space in C:, it has 226G free space.
Another thing I forgot to mention is that the setup package include lots of files(data, map etc), is that a problem?
Thanks,
snow bear
Well, that rules out the obvious. What kind of file is it that was preventing the Setup from building? Is it possible that the file in question was somehow corrupted, or was in use by some other process? It could be that the error you are receiving is being thrown because there isn't another error for your specific situation.
- the V-Bee
the file is an MS Access database file (.mdb). It should be in good condition, because when I run the project in development environment, everything works, that .mdb file is needed when run the project.
 snow bear wrote: |
| the file is an MS Access database file (.mdb). It should be in good condition, because when I run the project in development environment, everything works, that .mdb file is needed when run the project. |
|
Hi there
I have the same problem. My MS Access file is also about 290Mb. It worked when the file was smaller, but I copied the original DB in the setup folder and now it doesn't seem to "find" the file - you know what I mean.
Thanx
Wynand
I am having the same prolem with 1.8g access.mde file!
When I tried to create an empty setup project and just add those Access databases one by one and rebuilt the project, it works, I can not figure out what's going wrong.
I also tried to download a try version of wise installation, it can package all the files together but it has some problem to detect the dependent dll.
Unfortunately, there are some problems building setup projects with very large files, especially those greater than 700MB.
The limitation is actually in the libraries that do the compression of the files.
As a result, one of the best work arounds for building with large files is to set the Setup project's properties to build as Loose Uncompressed files. You'll have to copy the whole directory to deploy it, instead of just a .MSI file, but it will likely work better for large files.
Thanks for your help. I followed your advice to set the Package files to "As loose uncompressed files" in the property of the setup project, but when I build the solution, I still get this error message: "Could not find the '...' 'Not enough storage is available to complete this operation.'"
Any more suggestion?
Thanks a lot.
I think I have some unfortunate information.
I did some more digging into this issue, and found the related bug I logged on this a few years ago. We did some deep investigation recently and found that the ability to package files is actually limited by RAM, since files are being loaded into memory.
Package as Loose actually should work by not loading the data in RAM, but there is a bug in that we still load the file into RAM. In fact, we are loading all files into memory at the same time. So, it depends on how big your total project is.
So, the real workaround is to do this on a machine with more free RAM available. Perhaps you might be able to increase your swap file (Virtual Memory/Cache) size.
We have been able to succesfully package files as large as 678Mb.
I hope this at least clarfies things a bit.
It makes sense now. After removing the mdb file, the setup package is about 404MB now, and the mdb file is about 252 MB, I guess I have reached the limit of the setup project in visual studio. By the way, my ram is 2GB.
So basically there is no way for me to build the setup project using vs 2003, is that right? How about other third party installation software like InstallShield or Wise?
Thank you so much.
I think that some of the 3rd party tools do a better job of building large setup solutions. They both have free trials you can test to see if one is suitable.
Ok, it makes sense what you're saying, except that it doesn't work that way. I am trying to build a setup project that contains two 200+ mb files, I have 2 gigs of RAM, my virtual memory is set to 4096 mb, and I have over 55 gigs open on my hard drive. How on earth would Visual Studio be unable to load all of the files in my setup project, and be unable to do whatever it wants to them?
I have at least 4 times as much memory Visual Studio could conceivably require. This doesn't make any sense, and it still doesn't work when I remove one of the large files. I'm sure that you're explanation covers part of the bug, but we need more to work off. If that was the exact problem, then the results would be consistent. Believe it or not, some of us depend on these tools to function properly. I think its safe to say that solutions with files greater than a gig are fairly common. Do you know if microsoft is currently working on this problem? My biggest question is, how do
they build their projects?
I'm getting this error now on simple projects (basic Windows app w/ 1 form). I started getting it all of a sudden (Unable to start debugging. Not enough storage is available to complete this operation.) I've checked many things on the system now, including virtual pagefile allocation, various services, etc. everthing else, except [ironically] Symantec LiveUpdate, seem ok (Symantec also compains it couldn't get enough memory).
Any ideas on this twist?
