Options
GUI Exception: Timeout Expired
csm
Posts: 17
Hello All,
Just returned to my computer and the running SQL Backup GUI had the following exception displayed:
Click'd OK... all seems ok. Possible GUI bug?
Colby
Just returned to my computer and the running SQL Backup GUI had the following exception displayed:
SQLBackup v5 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. WorkerExecutionException at RedGate.SQLBackup.Engine.ConfigurableThreadPool._1(Exception ) at RedGate.SQLBackup.Engine.ConfigurableThreadPool._1._2() at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() ---------- 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. at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at _23._1(String , Object ) at RedGate.SQLBackup.Engine.Server._1() at RedGate.SQLBackup.Engine.Server._1() at RedGate.SQLBackup.Engine.ServerInProgressItems._1() at RedGate.SQLBackup.Engine.Server._1() at _6._2(Object )
Click'd OK... all seems ok. Possible GUI bug?
Colby
Comments
Thanks for your post. Connection Pooling is done in .NET to improve the efficiency of connections to a SQL Server.
The error message may simply mean that you have exceeded the maximum allowed number of connections to the server. The maximum number of allowed connections can be configured in your SQL Server (Enterprise Manager/Management Studio) server properties.