The following is happening fairly regularly:
----10/3/2007 9:47:39 AM scotts--DARTH()--SSL Disabled Vault Failed to establish a connection to the database.
----10/3/2007 9:47:39 AM scotts--DARTH()--SSL Disabled System.InvalidOperationException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
Running SQL Server 2000, Vault 3.5.0.4741 on Windows Server 2003.
Any ideas on the cause and cure?
Thanks!
Failure to Establish Connection To Database
Moderator: SourceGear
Most likely a setting in the Vault App Pool in IIS. There could be other factors as well. So that I have more environment information, could you open a client, connect to a repository, go to Help - Technical Support, and copy the information from there to me?
Also, if you want to send me an email at support at sourcegear.com (Attn: Beth), I could send you screen shots of the settings I have on server to compare against.
Also, if you want to send me an email at support at sourcegear.com (Attn: Beth), I could send you screen shots of the settings I have on server to compare against.
Beth -
Here's the information:
Client Information
Vault Client Version: 3.5.0.4741
.Net Framework Version: 1.1.4322.2407
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 1022.36 MB
Time Zone: (GMT-08:00) Pacific Time (US & Canada)
Server Information
Vault Server Version: 3.5.0.4741
.Net Framework Version: 2.0.50727.832
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 2.0
OS Version: 5.2.3790
Timezone: (GMT-08:00) Pacific Time (US & Canada)
SQL Version: Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
License Information
2 serial number(s):
1 of 2: 10 users, permanent
2 of 2: 10 users, permanent
Here's the information:
Client Information
Vault Client Version: 3.5.0.4741
.Net Framework Version: 1.1.4322.2407
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 1022.36 MB
Time Zone: (GMT-08:00) Pacific Time (US & Canada)
Server Information
Vault Server Version: 3.5.0.4741
.Net Framework Version: 2.0.50727.832
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 2.0
OS Version: 5.2.3790
Timezone: (GMT-08:00) Pacific Time (US & Canada)
SQL Version: Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
License Information
2 serial number(s):
1 of 2: 10 users, permanent
2 of 2: 10 users, permanent
There's a couple things that could be issues, but we'll start first with the pool connect string. See this forum thread: Failed to establish connection error.
Go to this key and increase the Max pool size number.
<add key="ConnectString" value="Application Name='SourceGear Vault Server'; Connection Reset='true'; Server=(local); Database=sgvault; Max Pool Size=x; Integrated Security='true'" />
Go to this key and increase the Max pool size number.
<add key="ConnectString" value="Application Name='SourceGear Vault Server'; Connection Reset='true'; Server=(local); Database=sgvault; Max Pool Size=x; Integrated Security='true'" />