Vault server could not be contacted to perform the operation

[scaiferw]

One of my developers is trying to upload a directory structure.

Total Files Listed:
490 File(s) 698,067,726 bytes
521 Dir(s) 147,256,967,168 bytes free

It fails quite quickly;

Code: Select all

[31/07/2013 1:56:36 PM] Preparing data to begin transaction
[31/07/2013 1:58:36 PM] Beginning transaction
[31/07/2013 1:58:37 PM] An error occurred while trying to begin a transaction.
[31/07/2013 1:58:37 PM] Transaction failed
[31/07/2013 1:58:37 PM] An exception was encountered during the transaction.  Exception: The Vault server could not be contacted to perform the operation.  Your network connection to the server may have been interrupted.  Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client.The request failed with HTTP status 413: Request Entity Too Large.   at VaultClientNetLib.VaultConnection.BeginTx(Int32 nRepID, VaultRequestItem[]& requests, String& strTxID, String comment)
   at VaultClientOperationsLib.ClientInstance.Commit(ChangeSetItemColl givenItems, String strChangeSetComment, Boolean keepCheckedOut, Boolean removeLocalCopy, CommitType committype, VaultDateTime dateImport, Int32 nUserIDImport, Int64& nRevID, Int32[]& retBegEndTx)

I know my network path is open because I've been doing other work from the same location, and when I try a small set of the files that are failing it goes through without problem;

Code: Select all

[31/07/2013 1:59:56 PM] Preparing data to begin transaction
[31/07/2013 1:59:56 PM] Beginning transaction
[31/07/2013 1:59:56 PM]     Create folder $/z_test5/subtest_c/AdobeDreamweaverCS6_v12r1
[31/07/2013 1:59:56 PM]     Add $/z_test5/subtest_c/AdobeDreamweaverCS6_v12r1/AdobeDreamweaverCS6_v12r1.aamee
[31/07/2013 1:59:56 PM]     Add $/z_test5/subtest_c/AdobeDreamweaverCS6_v12r1/AdobeDreamWeaverCS6_v12r1.cmd
[31/07/2013 1:59:56 PM]     Add $/z_test5/subtest_c/AdobeDreamweaverCS6_v12r1/AdobeDreamWeaverCS6_v12r1_Remove.cmd
[31/07/2013 1:59:56 PM] Ending the transaction
[31/07/2013 1:59:56 PM] Transaction completed successfully

The sgvault.log shows nothing for this time period.

Can you point me to a solution for this?

(This attempt is being made locally, the client is installed on the Vault application server, the file set is on a network share.)

[lbauer]

Is this the same user referenced in this forum post?

http://support.sourcegear.com/viewtopic.php?f=5&t=21807

If not, have that user enable Chunked Encoding and also increase the UploadTimeoutSeconds registry value if they're on a different machine.

[scaiferw]

It is the same user, and I'm also having the same result when I test it.

[scaiferw]

Incidentally, because the error cited HTTP 413 Request Entity Too Large, I identified the largest file - 152,643KB - and uploaded it alone with no problem. I successfully uploaded files between 1.5GB and 2GB yesterday from the same network share.

[lbauer]

This HTTP 413 error is coming from IIS, which thinks the upload size is too large.

Are you using SSL?

[scaiferw]

Yes, I unbound HTTP/80 and bound HTTPS/443 when this server was built last year. All connections are SSL.

The 413 error puzzled me as I've successfully uploaded files far larger than the largest file in this file set, and I can upload the largest in this set by itself with no problems.

[lbauer]

I did some Internet research.

One blog wrote:

If you have a website with SSL and “Accept Client Certificates” enabled HTTP requests are limited to the UploadReadAheadSize of the site. To resolve this, you have to increase the UploadReadAheadSize. (Default size 48kb)

http://tharakaweb.com/2012/12/11/413-re ... too-large/

Here are additional links that might help:


http://forums.iis.net/t/1161838.aspx
http://forums.iis.net/t/1169257.aspx
http://forums.iis.net/t/1193836.aspx/1
http://www.attunity.com/faq/rmft-faq-er ... -too-large
http://forums.iis.net/t/1192002.aspx/1? ... +too+large
http://blogs.iis.net/rakkimk/archive/20 ... dsize.aspx
http://tmoaikel.wordpress.com/2011/10/1 ... s-6-and-7/

[scaiferw]

But that doesn't account for the fact that I'm easily uploading individual files of close to 2GB, and the largest file in the set I'm having trouble with is 150MB.

I'm reluctant to monkey with the UploadReadAheadSize setting when the upload size doesn't seem to be the problem.

Can you suggest another avenue of approach?

If the UploadReadAheadSize is still indicated I can do it, but there seems to be no GUI to manage and I can't see the current setting to restore it if this doesn't work.

I'm don't want to be making a blind change on a production server if I can help it.

Thanks,

Rob

[lbauer]

How large is the entire upload?

If you copy the files to the server machine, rather than uploading from the network share, does the upload succeed?

We'd like to see a copy of your latest the Vault Server log (it should cover the time of the upload attempt, but we want to see if there are errors prior to that).

Also send a copy of the client log.

[scaiferw]

As noted, the entire upload is 490 Files, 698,067,726 bytes.

Yes, the upload does succeed if the files are copied to the server, then uploaded to the repository from the client installed on the server.

I set the client log to to log all classes, ran the upload locally (source files uploaded from server) and got a log, but the log is not updating on subsequent upload attempts so is not showing any details for the subsequent failed uploads from a network share. Not sure now to resolve this. Renaming the log file in an attempt to force creation of a new one did not work.

Incidentally, I believe one upload attempt this morning from the network share did succeed, though I cannot confirm because the log and the message pane does not indicate the source of the upload. Two subsequent attempts this morning failed.

Where should I send the logs?

[lbauer]

How are you enabling client logging?

You can send the logs to support at sourcegear.com, ATTN: Linda.

Please include a link to this forum post.