SqlException Timeout expired

Hans Olav Nymand · Post by **Hans Olav Nymand** » Fri Aug 03, 2012 1:52 am

Hi,

We get this error in the log:
----29-07-2012 00:06:51 Read_Only--robot14.pdc.xx(10.117.68.20)--SSL Disabled System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

Can you assist me by explaining which timeout has expired, and where this timeout is set. Is it a value set in the vault server web.config, in the IIS or on the SQL Server.

We'd like to increase this value to see if it helps.

Best regards,
Hans Olav Nymand
Prolog Development Center A/S

lbauer · Post by **lbauer** » Fri Aug 03, 2012 7:51 am

This timeout generally means that the Vault connection to SQL Server timed out. This can be due to many things, such as: a transaction took much too long, network connectivity problems caused a timeout, etc.

What types of problems are users experiencing when using Vault?

Before we modify any settings, we'd like to see a copy of the Vault Server log to see what else is going on with the the Vault Server.

It's called sgvault.log and is in %windir%\temp\sgvault on the server machine. Send the log zipped up to support at sourcegear.com, Attn: Linda. Please include a link to this forum post.

Hans Olav Nymand · Post by **Hans Olav Nymand** » Fri Aug 03, 2012 4:59 pm

OK, I've attached a reduced version of the sgvault.log. Please note that this bulltin board does not allow files with extension .log and no larger than 2MB - a little silly when having to upload a log.

The users experience problems like this:
[30-07-2012 12:04:29,55] "C:\Program Files (x86)\SourceGear\Vault Client\vault.exe" -user "read_only" -password "" -host "vault.pdc.xx" -repository "Visual Prolog" getlabel "$/_Vip6/Prodir" "20120629_1546" -makereadonly -setfiletime checkin -destpath "c:\Vault\Staff Software\src\prog\..\Visual Prolog\_Vip6\Prodir"
<vault>


























































<error>
<exception>VaultClientOperationsLib.GetLatestVersionFailedException: Exception of type 'VaultClientOperationsLib.GetLatestVersionFailedException' was thrown.
at VaultClientIntegrationLib.GetOperations.performLabelGet(String objectPath, String label, String labelSubItem, String labelWorkingFolder, String destPath, GetOptions go)
at VaultClientIntegrationLib.GetOperations.ProcessCommandGetLabelToLocationOutsideWorkingFolder(String objectPath, String label, String labelSubItem, GetOptions getOptions, String destPath)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)</exception>
</error>
<result>
<success>False</success>
</result>
</vault>

Best regards,
Hans Olav Nymand

lbauer · Post by **lbauer** » Mon Aug 06, 2012 1:26 pm

There's a pattern of errors in your server log that we've seen before. A failed download destablizes the Vault Server cache and a number of other errors follow, include SQL timeouts.

When you restart the Vault Server, do things operate better for a while? Restarting the Vault Server refreshes the server cache.

We have a fix for this cache instability, if this is the problem you are experiencing.

Hans Olav Nymand · Post by **Hans Olav Nymand** » Mon Aug 06, 2012 1:58 pm

Yes, restarting the server resolves the problem for 2-3 days, then it's back.

Regards,
Hans Olav

lbauer · Post by **lbauer** » Mon Aug 06, 2012 3:04 pm

Ok, then we'll try the special build which fixes this "cascading error" problem.

Email support at sourcegear.com, Attn: Linda. Please include a link to this forum post.

SourceGear Support

SqlException Timeout expired

SqlException Timeout expired

Re: SqlException Timeout expired

Re: SqlException Timeout expired

Re: SqlException Timeout expired

Re: SqlException Timeout expired

Re: SqlException Timeout expired