Exception encountered during transaction

bcargill · Post by **bcargill** » Wed Jan 12, 2005 11:53 am

I am using v3.0.1 of the GUI client. I am attempting to create a branch of a directory with a large number of subfolders and files (our entire codebase). The client reports failure (although the branch appears to be created). The server log reports no failures.

The following messages are generated in the client GUI:

[1/12/2005 11:13:38 AM] Preparing data to begin transaction
[1/12/2005 11:13:38 AM] Beginning transaction
[1/12/2005 11:14:23 AM] Branch $/trunk/RD/Codebase
[1/12/2005 11:14:23 AM] Ending the transaction
[1/12/2005 11:16:53 AM] Server unavailable for transaction end
[1/12/2005 11:16:53 AM] 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 underlying connection was closed: Could not establish secure channel for SSL/TLS.Unable to read data from the transport connection.Unable to read data from the transport connection. at VaultClientNetLib.VaultConnection.EndTx(String strTxID, Int64& nNewRevision, VaultResponseItem[]& responses, Int32 nAction, DateTime& txBeginDate)
at VaultClientOperationsLib.ClientInstance.Commit(ChangeSetItemColl givenItems, Boolean keepCheckedOut, Boolean removeLocalCopy, Boolean bIsImport, DateTime dateImport, Int32 nUserIDImport, Int64& nRevID)
[1/12/2005 11:16:53 AM] Transaction failed

The client log is attached.

One interesting note, I can successfully branch a subset of the files. Timeout issue maybe?

Thanks for your help.

Post by **jclausius** » Wed Jan 12, 2005 12:42 pm

Can you locate/ post any relevant information from the server's log. By default this in %windir%\temp\sgvault.

bcargill · Post by **bcargill** » Wed Jan 12, 2005 1:01 pm

I've tried to isolate the appropriate messages from the log based upon the times:

# SourceGear Vault Server
----1/12/2005 9:59:42 AM sgvaultsystem--()--
System Started
Version 3.0.1.2769
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\VaultLogs
Log Level = Debug
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
Active Directory Domain =
SGVault Working Directory = C:\Temp
SGVault Server URL = https://ww2.ironcad.com
Identity = NETWORK SERVICE
...

----1/12/2005 11:13:38 AM bcargill--cargillb.ironcad.com(192.168.1.61)--SSL Enabled BeginTx beginning transaction
----1/12/2005 11:14:23 AM bcargill--cargillb.ironcad.com(192.168.1.61)--SSL Enabled BeginTx returned: Success
----1/12/2005 11:14:23 AM bcargill--cargillb.ironcad.com(192.168.1.61)--SSL Enabled VaultLib.VaultRequestCopyBranch returned: Success
----1/12/2005 11:14:23 AM bcargill--cargillb.ironcad.com(192.168.1.61)--SSL Enabled Ending transaction
----1/12/2005 11:18:03 AM bcargill--cargillb.ironcad.com(192.168.1.61)--SSL Enabled Creating plugin thread...
----1/12/2005 11:18:03 AM bcargill--cargillb.ironcad.com(192.168.1.61)--SSL Enabled VaultLib.VaultResponseItem returned: Success
----1/12/2005 11:18:03 AM bcargill--cargillb.ironcad.com(192.168.1.61)--SSL Enabled EndTxSuccess
----1/12/2005 11:18:03 AM bcargill--cargillb.ironcad.com(192.168.1.61)--SSL Enabled Getting repository Structure.
----1/12/2005 11:18:03 AM bcargill--cargillb.ironcad.com(192.168.1.61)--SSL Enabled GetRepositoryStructure returned: Success

...

Post by **jclausius** » Wed Jan 12, 2005 1:26 pm

OK, so the problem doesn't appear to be even related to the Server.

What is strange is that it appears the End Transaction request made it to the server before the SSL failure.

Normally in cases like this, I would ask other questions about your SSL certificate:
- Have you seen other SSL failures?
- Does the name of the cert match the server's host name?
- Is the cert from a trusted publisher or one of your own?

But if you don't have any other problems, I don't think that is it.

Let's look at other variables -
Any sort of proxy / firewall between your client and the server?

If you have access to Vault through an unsecure port ( non-SSL ), is it safe to assume this works?

bcargill · Post by **bcargill** » Wed Jan 12, 2005 1:34 pm

We have not seen other SSL failures, the name of the cert matches the server's host name, and the cert is one of our own.

There is no proxy involved, but there is a firewall. Although the access is unrestricted.

I think we only allow secure access to the Vault.

Post by **jclausius** » Wed Jan 12, 2005 2:00 pm

It may be possible the branch succeeded, and the network disconnect placed your client side cache in a weird state.

If you shut down all instances of Vault, delete the client side cachemember_repository & cachemember_laststructuregettime files, and restart the Vault client, is the branch there?

Note - to remove a cached tree, cachemember_repository and cachemember_laststructuregettime must be removed from %APPDATA%\SourceGear\Vault_1\Client\{repository-guid}\{vaultuser}, where {repository-guid} is the GUID for your database and {vaultuser} is your vault login account. More detailed information can be found at Vault Client-Side Cache Files

Addressing the disconnects - Is Vault server installed on a Windows 2003 server? Is it possible the application pool for the Vault server may require tweaking? See - Server sessions keeps timing out under Win2k3 and IIS 6 for IIS 6 settings.

bcargill · Post by **bcargill** » Wed Jan 12, 2005 2:44 pm

I deleted the caches and the branch is still there- it appears to be valid, but I'm a little shaky about using it without an explaination of the failure...

It is 2003 server- the timeout settings are as specified in your referenced document.

Post by **jclausius** » Wed Jan 12, 2005 3:04 pm

If the branch is there, it should be just fine. Since all transactions are atomic ( all or nothing ), having the branch in the tree means it is ready for use.

As for the explanation of why the branch exists - if a connection is lost, the Vault server will happily continue to process any running request. IIS will not abort any currently running that simply lost a network connection.

Since it appears as if something outside of IIS dropped the network connection, that would explain why the branch succeeded. However, without detailed knowledge of your exact network setup and perhaps the captured data from a network sniffer during a drop, I can't really explain why the connection was dropped in the first place.

bcargill · Post by **bcargill** » Wed Jan 12, 2005 3:07 pm

Understood- thanks for the help. I suppose I'll just ignore it- ignorance is bliss.

Odd that it happens so repeatably- always at about 3 minutes (I've repeated at least 10 times during trouble shooting).

Post by **jclausius** » Wed Jan 12, 2005 3:31 pm

If you're interested in trouble shooting a bit more, you could try to branch on the Vault server itself. This would eliminate the possibility the problem is server related.