|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Monday, February 04, 2013 6:31 AM
Points: 9,
Visits: 304
|
|
I am using an SQL Job to call a stored procedure which queries the database to get some email addresses and creates an HTML body. The procedure then calls sp_send_dbmail to send the emails.
I get an error on the job regarding a connection timeout. I'm not sure if the timeout is returning from the exchange server or the SQL server. Any ideas? Exception Type: Microsoft.SqlServer.Management.SqlIMail.Server.Common.BaseException Message: There was an error on the connection. Reason: 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., connection parameters: Server Name: , Database Name: msdb Data: System.Collections.ListDictionaryInternal TargetSite: Void OpenConnection(Microsoft.SqlServer.Management.Common.SqlConnectionInfo) HelpLink: NULL Source: DatabaseMailEngine
StackTrace Information =================== at Microsoft.SqlServer.Management.SqlIMail.Server.DataAccess.ConnectionManager.OpenConnection(SqlConnectionInfo ci) at Microsoft.SqlServer.Management.SqlIMail.Server.DataAccess.DataAccessAdapter.OpenConnection(String dbServerName, String dbName, String userName, String password) at Microsoft.SqlServer.Management.SqlIMail.IMailProcess.QueueItemProcesser.ProcessQueueItems(String dbName, String dbServerName, Int32 lifetimeMinimumSec, LogLevel loggingLevel)
2) Exception Information =================== Exception Type: System.InvalidOperationException 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. Data: System.Collections.ListDictionaryInternal TargetSite: System.Data.ProviderBase.DbConnectionInternal GetConnection(System.Data.Common.DbConnection) HelpLink: NULL Source: System.Data
StackTrace Information =================== 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 Microsoft.SqlServer.Management.SqlIMail.Server.DataAccess.ConnectionManager.OpenConnection(SqlConnectionInfo ci)
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Monday, September 17, 2012 11:29 AM
Points: 1,
Visits: 1
|
|
Did you ever find a solution for this?
We are having a similar problem where we get this error around 9:00p.m. every night for some reason.
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Tuesday, March 26, 2013 8:41 AM
Points: 2,562,
Visits: 3,451
|
|
set the trace for that particular time interval and see what other and related stuff is running ? and other thing try to see the perf mon too (i suspect there could be resource crunch too)
-------Bhuvnesh---------- While 1 = 1 (Learning SQL....) Click to get fast response of your post
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Monday, February 04, 2013 6:31 AM
Points: 9,
Visits: 304
|
|
tjmoore99 (9/17/2012) Did you ever find a solution for this?
We are having a similar problem where we get this error around 9:00p.m. every night for some reason.
Yes it is fixed. I believe we increased the database Mail Executable Minimum Lifetime setting in the Database Mail System Parameters.
|
|
|
|