Upload Error- file upload did not return an error header

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
jlawton
Posts: 1
Joined: Fri Apr 16, 2010 12:42 pm

Upload Error- file upload did not return an error header

Post by jlawton » Mon Sep 27, 2010 9:39 am

We have had difficulty getting some releases into Vault. This is the error returned:

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)

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: Upload Error- file upload did not return an error header

Post by Beth » Mon Sep 27, 2010 11:00 am

Were you uploading using the Vault GUI client, or integrated with VS or some other software?

Were you adding one file or an entire solution?
Beth Kieler
SourceGear Technical Support

JJRADHA
Posts: 2
Joined: Tue Jan 27, 2015 8:17 am

Re: Upload Error- file upload did not return an error header

Post by JJRADHA » Wed Jan 08, 2020 5:13 am

Hi Beth,

I am receiving this same error message:

[08/01/2020 11:05:00] Version Check: This Vault Professional client is version 10.0.2.30936
[08/01/2020 11:05:00] Version Check: Your Vault Professional server is version 10.0.2.30936
[08/01/2020 11:05:00] Version Check: The following information was retrieved from the SourceGear website. No information was sent to SourceGear. You can disable this part of the version check from the Options dialog.
[08/01/2020 11:05:00] Version Check: The most recent Server release is version 10.0.2.30936
[08/01/2020 11:05:23] Preparing data to begin transaction
[08/01/2020 11:05:23] Beginning transaction
[08/01/2020 11:05:23] Add $/DBA/Radharani/MERGE/Apcore.notif.ref_remainderStatus - Merge.sql
[08/01/2020 11:05:23] Upload for item $/DBA/Radharani/MERGE/Apcore.notif.ref_remainderStatus - Merge.sql failed, retrying...
[08/01/2020 11:05:23] Upload for item $/DBA/Radharani/MERGE/Apcore.notif.ref_remainderStatus - Merge.sql failed, retrying...
[08/01/2020 11:05:23] Upload for item $/DBA/Radharani/MERGE/Apcore.notif.ref_remainderStatus - Merge.sql failed, retrying...
[08/01/2020 11:05:23] Upload for item $/DBA/Radharani/MERGE/Apcore.notif.ref_remainderStatus - Merge.sql 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.processUploadRequest(HttpWebRequest request, Int64 bytesWrittenThisFile, Int64 uncompressed_length, String itemPath, Boolean updateProgress)
at VaultClientOperationsLib.ClientInstance.UploadItemCommon(Object t_item, String txID, String fileToken, String diskfile, Boolean bIsImport, Byte[]& streamBuffer, Int64& bytesWrittenThisFile)
at VaultClientOperationsLib.ClientInstance.UploadItem(ChangeSetItem item, String txID, Byte[]& streamBuffer, Int64& bytesWrittenThisFile, Boolean bIsImport)
at VaultClientOperationsLib.UploadThread.ProcessCommand(UploadThreadCommand command, UploadThreadCommandResult& outputResult)
[08/01/2020 11:05:23] Ending the transaction
[08/01/2020 11:05:23] Transaction failed
[08/01/2020 11:05:23] Transaction failed

I have put a trace in sql server but it does not even get to that point.
It suggests fiddling with the tool-options-network but not sure what I should put there.
I have included a picture.

what else can I do?
is it by any chance lack of permissions somewhere?
radhe01.jpg
radhe01.jpg (491 KiB) Viewed 5991 times

Tonya
Posts: 866
Joined: Thu Jan 20, 2005 1:47 pm
Location: SourceGear

Re: Upload Error- file upload did not return an error header

Post by Tonya » Wed Jan 08, 2020 8:47 am

Hello,

Thank you for the details. Can you please email us your Vault Server log? The Vault Server log is in %windir%\temp\sgvault\sgvault.log on the server machine.

Please email the log to support@sourcegear.com and refer to this forum post.

Thanks,

Tonya

JJRADHA
Posts: 2
Joined: Tue Jan 27, 2015 8:17 am

Re: Upload Error- file upload did not return an error header

Post by JJRADHA » Thu Jan 09, 2020 11:57 am

Thanks Tonya for the reply.

I have fixed my issue - it was really related to permissions as I had anticipated.
what was wrong?

I have changed the logging folder on my Vault to the following:
Image

Then when looking at the log file, to see what errors were generated I saw this:

Uncaught Exception: Could not find a part of the path 'D:\VAMANA\SOURCEGEAR\Temp\6abaa204-3b4d-4d59-9ff6-70c7e584a632.vlt'.

I noticed there was no Temp folder created under SOURCEGEAR in my D: drive, so I created the Temp folder and all started to work.
In my case I was getting the error when uploading a file into my Sourcegear.

Obviously I have all permissions setup for all the folders used by sourcegear vault.
I love this program, thank you.

regards
Marcello Miorelli
Attachments
the_loggin.jpg
the_loggin.jpg (151.1 KiB) Viewed 5978 times

Tonya
Posts: 866
Joined: Thu Jan 20, 2005 1:47 pm
Location: SourceGear

Re: Upload Error- file upload did not return an error header

Post by Tonya » Thu Jan 09, 2020 1:42 pm

We are glad to hear your problem is resolved! And thank you for posting the resolution.

Tonya

Post Reply