Hi there,
I bought the component today, and while I was demonstrating it to our company president, it stopped the upload of a big file after uploading around 3.5MB. Am I missing something in any of the configurations?

Thanks,
Arvind Khanan

After reading your response, I tried to configure my server and checked all the settings. Everything seems to be working fine. I have kept the max size = 2100000000 bytes and tried to upload 200 mb file. It stops after 10% to 13% of upload.

However it loads the whole file very well if I try to load from the same web server where site is hosted. But if I use it as an Internet site, it doesn't show any error, but stops after some time.

I even tried to load using your sample web, but there it displays error of file size being too big.

Your immediate response will be highly appreciated, because I want to merge it in our solution at the earliest if it works fine.

Thanks,

No, it does not stop, smaller files get thru, but an sql script file of size 4MB did not get thru and stopped after 93% of upload on an internet environment.

We are working for Health Care Sector, so our files are generally big and need to be highly secure. That was the reason I wanted to use https file upload as opposed to ftp upload.

As I need this feature at the earliest, so when would you be able to let me know?

Thanks for all your help and fast response.

Hi Arvind,

We are now 22% through a 300M+ file and it is still going. Is there anyway that we can try it with your server? You can PM us with the details if that's OK for you.

Thanks

Hi,
I also thought of the same but as per my first writeup, I am not sure of configuration setting in IIS or in Windows Explorer for setting the quota. Can you please help me to setup the quota so that I should test.

Moreover, if this quota can be set for individual users, e.g. Network Services may have the quota different from Administrators.

Thanks for all your help,

Hi Arvind,

I don't think it will stop because the quota is not set. We were researching the problem on our side. We ran into the quota problem when we were doing our test with our servers. Since our server is being managed by our hoster, who employees quota managements but we are not sure which system they use. I believe the easiest way to verify whether it's a quota problem or a server problem is to use a regular file upload element and see if it can upload the whole file to the server. If that can not do it, then we can be sure that it is a server problem.

Thanks

Hi Arvind,

The thing that I think worth trying at this moment is a regular HTTP file upload. We are not convinced that this is our problem yet because you may not be able to sucessively upload the file using a regular HTTP upload method ---- if that is the case, then I think it's pretty clear that the problem is your server and you can't just throw it back to us. As I have explained before, there is nothing we can do if your server hangs there.

If that proves to work, then we will need access to your server in order to see both scenarios and debug them in order to find out the difference. We can stay with you during the weekend if you will be there as well. But it's not likely that the problem can be resolved by Monday if you are gone because you are the only one that is seeing this problem.

Thanks

Hi Arvind,

You can try regular HTTP upload by putting a standard ASP.NET HtmlInputFile on the form and see if you are able to upload the same file onto your server.

As for my replies, I don't think there are any conflicts between them. I am not sure how you got that conclusion. Maybe it needs a bit more clarification:

1. If there is a quota and it is being hit, then most likely you see that problem (it may sit there or fail, depending on exactly how your quota management is implemented);

2. "I don't think it will stop because the quota is not set.". This means I do not believe the fact that "quota is not set at all" can cause the uploader to stop. Again, I am not saying that there can't be other reasons that can cause it to stop;

As for "throwing thing", I was referring you declaring our product needs more work and demanding us "taking it back" without even knowing for sure that it is our problem or not. It's like that your car ran out of gas and you want the dealer to fix it for you. That's why I found it's a bit unacceptable. We understand that you run into a problem, we are also doing our best to help you out, it is both yours and ours best interest to work it out ---- regardless what caused the problem. But trying to be political half way won't be helpful. So I want to say it again, if it is a problem in our components, then we will not only accept, but will do our best to fix it as soon as possible and provide a workaround for you at the earliest time if possible. But it's probably much better not pointing fingers before we get to the bottom of this and really know what it is.

I am sure both of us know and understand many things can cause problems. Just like a car won't run without gas, it's very obvious that in such case you don't blame the car. We did see the same problem when the quota limits is hit, but is that a problem of our component? I don't think so. Your harddrive crashed and that's a software problem? Probably not. However when such issue does occur, we always try to identify what exactly caused the problem and then advice our customer to the best of our knowledge and if possible, provide a solution or workaround for our customers.

Trouble shooting a problem can be frustrating, but it’s not like the moment you blame on others and the problem is solved. That’s the reason that we are trying to work with you and hope that we can find a solution for you. And if you try to be aggressive, probably you just end up with nobody wants to solve the problem for you. As our set policy, we do not issue refund after license key is disclosed as doing so would obviously encourage fraudulent orders.

Thanks for your understanding.