Is this a .NET or classic ASP application? Is anything getting cached to the correct location? One thing that could cause FileUp cache all your files C:\Windows\Temp rather than the directory specified in the registry would be if it is a .NET application and the HttpModule is not configured correctly. If the HttpModule doesn't intercept the request and cache the file, the FileUp object will cache it, either to the location set by the .Path property or to a default location if the .Path property hasn't been set. Even if the HttpModule is configured correctly, the FileUp object will still temporarily cache very tiny files during the process of the upload. If you want to control this location, set the .Path property before referencing any form elements.
Please tell us more about your application and we will continue helping you troubleshoot the problem.
Are you seeing temp files also get created in the directory specified in the registry? If so, that means the HttpModule is working and these other files are much smaller temp files created by the FileUp object. If you can verify that the HttpModule is working and you are still having this problem, I recommend setting the .Path property to the same location as the one in the registry key.
For example (C#):
FileUp upload = new FileUp(Context);upload.Path = @"D:\DSS-Scans\upload-cache";
... continue with your upload processing code.
This should make sure all temp files created by either the HttpModule or the FileUp object go to the same place. Please let us know if this helps.
Hmm. Now that you have changed the .Path property, even if the HttpModule isn't configured properly, FileUp should be caching everything to "D:\temp\upload-cache." If the HttpModule isn't intercepting the request, ASP.NET would also be caching the entire request somewhere before FileUp is able to access it, but those cache files wouldn't be named sa***.tmp. Are you sure the new code is executing? Is anything at all getting written to the correct directory?
I suggest running procmon during a small upload to look at the registry and filesystem activity of the IIS process while the upload is in process. Is the FileUpTempDir registry key being read? Is D:\temp\upload-cache being written to? Please let us know what you find.
Glad to hear the problem is resolved!
Sorry to hear you are still having problems. If the problem is happening on the server, XFRequest.DebugLevel won't be helpful because that is a setting for XFile. It only logs things that happen on the client.
It will be difficult to troubleshoot this without reproducing it. Do you have a staging server where you can do some load testing?
When you reverted, was it just the dlls or are you using different code and registry settings?
It is difficult to troubleshoot problems that only happen in production. If you can't keep the application running in production so we can help you troubleshoot it there, you will need to try to reproduce the problem in a test environment that is configured exactly the same as the production environment. If the problem only happens with load, you may need to use some kind of load testing tool that can simulate multiple concurrent requests. The only other thing you can do is look more closely at the configuration of the problemmatic production server that is currently not being used, but you won't be able to gather real-time information.
If you decide to purchase an Annual Maintenance contact we could provide more hands-on assistance. Otherwise, please feel free to continue posting questions here.