Hi,

If you meant the TempFileLocation you set for the AJAXUploader, then it is very normal that it would throw permission exception when your application do not have write permission on that folder. If this is the case, it does not make sense that the new version would not work and the old version would work. You should configure your Windows permission to fix that problem. AJAXUploder always requires write permission on the temp folder.

Thanks!

Hi,

Check and fix your Windows file permission on the temp folder. This is the only thing we will tell you on this issue. The uploader needs write permission on TempFileLocation because it needs to write temp files. This is not an issue in the new version, it's an issue on your folder permission. You can repeat your question again and we will still tell you the same thing.

Thanks!

Hi,

We are not sure what else we can tell you on this. As we have said over and over again, we know our AJAXUploader always need write permission on TempFileLocation. That behavior is by design from the very first version. So there is really nothing to fix here. The only thing you should do is to check and fix your folder permission. If you believe you can switch back to an older version to avoid that problem, please feel free to do so. What we are trying to tell you is that is not a solution and fixing your folder permission is only viable solution.

If you do not believe what we tell you, then there is nothing else we will add to this topic.

Thanks

Hi,

We REALLY WILL NOT troubleshoot a permission issue for you. You need to forget about the fact that 8.0.22.2 works. We know AJAXUploader needs write permission and if it happens to work for you without it, then THAT might be a bug, or more likely a coincident, or it just happens that the site using 8.0.22.2 is configured correctly while the new site is not.

We call File.create to create temp files and then write to it. This is the part that is failing for you. There are numerous reasons that can cause it to fail. One scenario is the directory does not have write permission; Another scenario is the directory is on a network share and your application did not log in properly; Another scenario is our DLL is not trusted on your server. All of which are either Windows, or .NET, or IIS configuration issues. We WILL NOT troubleshoot those issues for you because no only those are beyond the scope of our support, but also beyond the scope of our expertise.

Usually as long as the product works fine locally but not remotely, it is a server configuration issues. In that case the most we will do is point you to the right direction as we already have. We will not actually analyze or troubleshoot the issue for you.

This issue is closed now. This is not a bug in the product so there is nothing to fix. We will not make any further reply or comment on this issue. If you believe 8.0.22.2 can fix the problem for you, please roll back to that version.

Thanks!