Question

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

Workflow

Updated September 14, 2016

asked on September 5, 2016

Hello All,

can someone please explain me this error below:

Timestamp: 2016-06-15 11:15:48.166
Local Time: 15-06-16 3:15:48 PM
Category: Database
Machine: VITLWF03
Severity: Error
Application Domain: Laserfiche.Workflow.Service.exe
Process Id: 1276
Process Name: C:\Program Files\Laserfiche\Laserfiche Workflow 9\Laserfiche.Workflow.Service.exe
Win32 Thread Id: 1840 - GC
Thread Name: GC
Message: <Exception handlingInstanceId="fd2d62a3-9a70-47a0-a241-00c39aee2999">
<Description>An exception of type 'System.InvalidOperationException' occurred and was caught.</Description>
<DateTime>2016-06-15 15:15:48Z</DateTime>
<ExceptionType>System.InvalidOperationException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
<Message>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.</Message>
<Source>System.Data</Source>
<HelpLink />
<Property name="System Call">False</Property>
<Property name="TargetSite">Boolean TryGetConnection(System.Data.Common.DbConnection, System.Threading.Tasks.TaskCompletionSource`1[System.Data.ProviderBase.DbConnectionInternal], System.Data.Common.DbConnectionOptions, System.Data.ProviderBase.DbConnectionInternal ByRef)</Property>
<Property name="HResult">-2146233079</Property>
<StackTrace>   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.Open()
   at Laserfiche.Workflow.Database.CommandExecutor.ExecuteCommand(DbCommand command, Delegate method, CallTypes type)</StackTrace>
<additionalInfo>
    <info name="MachineName" value="VITLWF03" />
    <info name="TimeStamp" value="15-06-16 11:15:48 AM" />
    <info name="FullName" value="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
    <info name="AppDomainName" value="Laserfiche.Workflow.Service.exe" />
    <info name="ThreadIdentity" value="" />
    <info name="WindowsIdentity" value="ITLDOM\laserfichesvc" />
</additionalInfo>
</Exception>
----------------------------------------

What could cause this error?

0 0

Replies

replied on September 5, 2016

Hi IqBal.

When I get that error I use the following script:

CREATE NONCLUSTERED INDEX wait_condition_wf_ix ON wait_condition
(
instance_id,
workflow_id
)

in workflow data base and works for me it´s very recommended to back up your workflow data base before you run this script.

Regards

0 0

View 1 previous reply

replied on September 6, 2016

Hello David,

thanks for your help.

however i'm getting the error below when running this script on the database:

Msg 1088, Level 16, State 12, Line 1
Cannot find the object "wait_condition" because it does not exist or you do not have permissions.

Any idea. The script is being run from the db owner profile.

Also, what does this script actually doing?

0 0

replied on September 6, 2016

Hi Iqbal.

Check if your Workflow version is 9.2 because it´s used for that specific version.

If it´s 9.2 review your permissions on the workflow database.

For last review if the data base are you using it´s the workflow database.

The script create index for the workflow database in some cases help to do the call of nodes more efficient.

0 0

replied on September 6, 2016

Hello David,

I'm using version 9.1.1.365

Not my luck.

Any other idea to resolve this issue.

0 0

replied on September 7, 2016

Hi Iqbal.

When exactly occurs this error?.

Maybe we can think in something more specific

0 0

replied on September 14, 2016

This error (and the ones in your other 3 posts with similar SQL errors) usually indicates that the SQL server is overloaded. Whether this is caused by a runaway workflow, underpowered SQL Server machine or other SQL activity unrelated to Workflow cannot be determined from the error message alone. Please contact your reseller to open a case with Tech Support to investigate this issue.

0 0

You are not allowed to follow up in this post.

Question

Question

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

Replies

Sign in to reply to this post.