Just anything related to ASP.Net.Anonymous wrote:Any thing specific I should be looking for?
Enabling chunked encoding is supposed to reduce the memory requirements by the .Net Framework when Vault is transferring files.Anonymous wrote:Neither has worked so far.
Checking the 'chunked encoding' box does not effect whether or not the file uploads successfully (it still fails) but does generate different error messages.
From the vault client installed on the server, attempting to upload with chunked encoding checked gives the system.outOfMemory execption.
With it UNchecked, I get a timeout exception.
The scenario which would provide the best memory usage would be to :
1) Restart the Vault Server (iisreset.exe)
2) Login with a client on a DIFFERENT machine - make sure no one else starts a Vault client
3) Enable chunked encoding on the GUI client
4) Add the file from the client from Step 2.
The only other thing I think might help is adding memory to 4GB and then using the /3GB switch within boot.ini in your Win 2K Server's boot item. This would give IIS more application memory to accept the incoming file.
Otherwise, since the Vault server is at the mercy of IIS' default HTTP handler, I'm afraid it will be difficult adding a file of that size.