Hi,
when i try to upload large files on my local computer using windows vista and IIS7, everything works fine. i can even upload a 150mb file no problem.
after installing CKfinder to my web server, when i try to upload a file larger then 2mb (approx, since it changes abit on every upload attempt), it stops every time somewhere around the 2mb-marker.
My server is using windows server 2003 and IIS6
I am able to upload large files using 3rd party components such as Persists Upload.
But i noticed that you are using adodb.stream, and i havent been able to find a solution (also tryed to increase aspMaxRequestEntityAllowed key in my iis metabase with no effect)
can you help?
or maybe you have a patch to install that will use a 3rd party uploder instead of adodb.stream?
thanks
when i try to upload large files on my local computer using windows vista and IIS7, everything works fine. i can even upload a 150mb file no problem.
after installing CKfinder to my web server, when i try to upload a file larger then 2mb (approx, since it changes abit on every upload attempt), it stops every time somewhere around the 2mb-marker.
My server is using windows server 2003 and IIS6
I am able to upload large files using 3rd party components such as Persists Upload.
But i noticed that you are using adodb.stream, and i havent been able to find a solution (also tryed to increase aspMaxRequestEntityAllowed key in my iis metabase with no effect)
can you help?
or maybe you have a patch to install that will use a 3rd party uploder instead of adodb.stream?
thanks
Re: Large files upload problem
You should include this in your documentation...
Re: Large files upload problem
Hi, I'm glad that you have found the problem and posted it so anyone else can find the solution.
Did you try to use the setup wizard: viewtopic.php?f=10&t=13604 ?
At the very least it should have helped to read the exact error message generated by the server.
I guess that any other component like AspUpload will face the same problem, so I guess that there's no need to provide support for it. Right?
I'll try to add some notes about it, but for me the ideal solution is to bring back a proper error message stating that there's a timeout problem. I know that I did some adjustments about it, but it might not be enough.