Just curious ...
I thought the external container feature resulted in separate folders of images
What exactly happens when you download the closed file ? to you get a 60 Mb file, or does it try to re-insert the images ?
> I have tested downloading both mine and your file. I have also both tested with having the data transferred externally and only being stored internally. In all cases, when the file is ballooned to 16GB, the 404 error you mentioned does occur. This is likely a limitation of the server software itself.
Is the issue having FMS re-combining the container data and the database so that it can be downloaded from the server?
The temporary solution is to run a backup and pull the backup files for both the database and the container data?
Have you tried this and been able to access the local container data from the local copy of the database?
With the database on the server and the container data set as external, are you able to do all of the normal functions with the existing container data and add new records?
What exactly happens when you download the closed file ?
What happens under the hood is that FMS zips the FM file itself and the whole folder structure where it keeps the RC data and downloads that as one file.
The problem has been that the RC folder structure is somewhat different for the hosted file than for it's local version so after you downlaod the file (assuming that it works given its overall size) you would still have to manually move one or two folders before the local version sees its RC data
There is no problem with using the file from the client side.
It's when downloading the file from the server to the d/top that the proces just stops indicating a 404 error.
So the file does not download.
The work around is to use a backup.
The issue is that the file does not download to the client desktop as expected.
All other aspects of server/client usage work as does document management.
It's just downloading the file that doesnt't work.
Just a thought, but could it be a network issue? Wondering if you received a hiccup on the network, and it causes FMS to hiccup in a much more dramatic way. More of a server puke I guess.
Are you doing the download via wifi?