Upload fails and the following error is received when using FileUpSE in .NET:

HTTP Module Exception Occurred while processing the HTTP input stream from the client.
File Transfer has been aborted. FileUpEeRequest::SaveRequest failed to set new request state.
Error: FileUpEeRequest::SaveRequest failed to handle preloaded entity body.
Error: Attempted to read or write protected memory.
This is often an indication that other memory is corrupt.

This is an installation/configuration issue as explained below.

This error has been seen when the FileUpTempDir registry key required by the HttpModule is missing or incorrect.

The FileUpTempDir registry key is used to tell FileUp's HttpModule where to cache the uploaded files. This cache path cannot be set in your FileUp code because the HttpModule intercepts the request at a lower level, before your page-level code is executed.

The key is located in the registry at:
HKEY LOCAL MACHINE\SOFTWARE\Software Artisans\SA-FileUp\Parameters.

By default, the FileUp installer will set the FileUpTempDir key to the system temp directory. You may change the path to any directory you like. Check the registry and make sure that the key exists and is set to a valid path that has Read/Write/Modify permissions for the user under which you application is running.

If you did a manual installation and did not add registry parameters for FileUp, see this KB article for instructions on adding all the FileUp registry keys:
Manual installation: How to add registry parameters to FileUp .
Before running the .reg file attached to the KB article, make sure to change the paths to valid writable directories on your server.

Note that in FileUpSE, all the registry keys are optional except for FileUpTempDir (FileUpEE on the other hand has a few additional mandatory keys). Here is an example of what your FileUpSE registry parameters might look like with all the optional and mandatory keys.