I am getting an error uploading a file. The file is about 70MB. The progress always shows 100% then fails.
The vault server is on my intranet.
[11/14/2011 9:46:53 AM] Add $/XML Inspection Data/pavement PROCESSED.zip
[11/14/2011 9:47:10 AM] Upload for item $/XML Inspection Data/pavement PROCESSED.zip failed, retrying...
[11/14/2011 9:47:47 AM] Upload for item $/XML Inspection Data/pavement PROCESSED.zip failed, retrying...
[11/14/2011 9:48:26 AM] Upload for item $/XML Inspection Data/pavement PROCESSED.zip failed, retrying...
[11/14/2011 9:48:26 AM] Upload for item $/XML Inspection Data/pavement PROCESSED.zip failed too many times, aborting transaction.
Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client.
The specific error was "The server had an error processing the file upload but did not return an error header. The remote server returned an error: (404) Not Found."
An exception was encountered during the transaction. Exception: The server had an error processing the file upload but did not return an error header. The remote server returned an error: (404) Not Found. at VaultClientOperationsLib.ClientInstance.UploadItem(ChangeSetItem item, String txID, Byte[]& streamBuffer, Int32& bytesWrittenThisFile, Boolean bIsImport)
at VaultClientOperationsLib.UploadThread.ProcessCommand(UploadThreadCommand command, UploadThreadCommandResult& outputResult)
[11/14/2011 9:48:26 AM] Ending the transaction
Error uploading file
Moderator: SourceGear
Re: Error uploading file
The first thing I would suggest is to try chunked encoding for uploads. This can reduce memory consumption.
This setting is in the Vault GUI Client under tools->Options->Network Settings.
If you already have that checked, you could try unchecking it.
This setting is in the Vault GUI Client under tools->Options->Network Settings.
If you already have that checked, you could try unchecking it.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Re: Error uploading file
That resolved the issue. Thanks for the quick response.