Server unavailable for transaction end

Ken · Post by **Ken** » Thu Feb 12, 2004 2:44 pm

We are having trouble with an off site user trying to add files to the Vault.

Error message in the message pane is:

[2/12/2004 11:18:59 AM] Add $/FOLDER1/FOLDER2/FOLDER3/File1.file
[2/12/2004 11:19:00 AM] Ending the transaction
[2/12/2004 11:19:02 AM] Server unavailable for transaction end
[2/12/2004 11:19:02 AM] Transaction failed
[2/12/2004 11:19:02 AM] Item $/FOLDER1/FOLDER2/FOLDER3/File2.file caused the transaction to fail: Could not apply the delta.
[2/12/2004 11:19:02 AM] Transaction failed

The user does not have any files checked out and has not downloaded any existing directory structure. We are using SSL for the user and if I try to log in with SSL I get the same message for any file I try to add. I can work normally if I do not log in through SSL.

Post by **jeremy_sg** » Thu Feb 12, 2004 3:04 pm

So I'm sure that I understand, your problem, I'm going to restate it. Noone can add any files through an SSL connection. Everyone can add files in normal http mode (except for the offsite guy, since you probably don't have port 80 open to the world.

How big are the files?

Is there anything in the server log that gives a hint?

Ken · Post by **Ken** » Thu Feb 12, 2004 3:16 pm

There is nothing in the server log except VaultServiceBase.VaultResponseAddFile returned: FailDeltaApply and EndTxFailDeltaApply.

I tried to add a 1k gif and this failed with SSL enabled.

Is it possible that the server is trying to initiate a connection when the transaction ends? The server is behind a firewall and incoming traffic is routed to the SSL port.

Post by **jeremy_sg** » Thu Feb 12, 2004 3:54 pm

The server does not try to open another connection out. Does this happen with very small files (about 1 byte). Long ago, I saw a situation where the SSL connection would be reset if the file is over a certain size. If that has reappeared for you, I would really like to know. Another thing to try is setting the registry setting

Software\
SourceGear\
Vault\
Client\
Settings\
DontUseChunkedHTTPTransfers

to "True" on the client machine.

Another possible but unlikely situation is that the server might be running out of disk space in its temp directory. Could you verify that things are ok on the server machine?

Ken · Post by **Ken** » Thu Feb 12, 2004 4:07 pm

I get the same message if I try uploading a 1 byte text file. I tried changing the registry setting to no avail. It works perfectly if I do not use SSL. With SSL I can do everything except Add and Checkin files.

Post by **jeremy_sg** » Thu Feb 12, 2004 4:10 pm

Ken,

We'll need to figure this out directly. Please email me at jeremy@sourcegear.com with your phone number and I'll give you a call.

Post by **jeremy_sg** » Thu Feb 12, 2004 4:36 pm

Ken's situation was resolved as follows:

Ken had a gateway that stood between the external client and the Vault server. This gateway was confused by the SendChunked property which Vault uses on its upload web requests. Setting the DontUseChunkedHTTPTransfers and restarting the client solved his problem.

Ken · Post by **Ken** » Thu Feb 12, 2004 5:58 pm

Thanks for your help. Just out of curiosity are there any penalties for setting DontUseChunkedHTTPTransfers to True?

Post by **jeremy_sg** » Thu Feb 12, 2004 9:47 pm

I'm not actually sure if there are any serious performance implications for disabling SendChunked. Chunked encoding was added in version 1.1 (i think), to prevent OutOfMemory exceptions when uploading large files. Chunked encoding instructs the .Net framework to upload the file a little bit at a time, instead of trying to load the entire file into memory before uploading it. If you're seeing a large performance difference, I would like to know about it.