Hi,

There are two folders when it comes to uploader: TempFileLocation and FinalFileLocation. The permission requirment for them are the same:

1. They must already exist. Uploader does not create these folders for you. So if you need to dynamically set these two folders, you should create them first;
2. The folder must be writable by ASP.NET worker process. ASP.NET worker process, especially in production environment, usually runs on an account that has restricted permissions so that if somebody exploited a loophole of your website and uploaded some code to run on your server, they still won't be able to destroy the whole system. This account is usually NT AUTHORITY\Network Service but I believe you can change it. This determines the permission of your whole application, not just the uploader. So an easy test is to call File.Create to create a file in your code, if that works, the uploader should work. If that does not work, neither will the uploader.

Generally you should not change TempFileLocation dynamically. In your case, you can set FinalFileLocation dynamically, or do not set FinalFileLocation but handle the uploader's FileUploaded event and then copy the file dynamically from TempFileLocation to wherever you would like. The reason that you should not change TempFileLocation is because TempFileLocation contains other temp files maintained by the uploader (.status file, example). Uploader automatically cleans those files at a later time. However if you frequently changes TempFileLocation, temp files in "old" TempFileLocation" may never get a chance to be cleaned.

Hope this helps.

Thanks!

Hi,

It doesn't happen right away. That's exactly why you do not want to change TempFileLocation. This post has more information on how it works:

http://www.essentialobjects.com/Forum/Default.aspx?g=posts&t=128

Thanks!