Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Unhandled Error: ...max pool size was reachedUnhandled Error: ...max pool size was reached
Previous
 
Next
New Post
12/16/2008 5:40 PM
 

Hi

I am running a DNN instance on Windows Server 2003/IIS 6.0 with 23 portals.  I am regularly (more than every hour) seeing an error message which takes down all my portals as follows:

Unhandled Error
Error Details
File
Error 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.

I have located a corresponding error in the Windows Application Event Log as follows:

Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 12/16/2008 6:59:17 PM
Event time (UTC): 12/16/2008 6:59:17 PM
Event ID: 4b4ac986df8a41b48bdd6a9974a8466c
Event sequence: 36
Event occurrence: 4
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1211025146/Root-1-128739266011545000
Trust level: Full
Application Virtual Path: /
Application Path: C:\dnnroot\
Machine name: CANTARUS-2

Process information:
Process ID: 3592
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:
Exception type: InvalidOperationException
Exception 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.

Request information:
Request URL:
Request path:
User host address:
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE

Thread information:
Thread ID: 1
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: 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.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters)
at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText)
at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues)
at DotNetNuke.Data.SqlDataProvider.GetHostSettings()
at DotNetNuke.Entities.Host.HostSettings.GetHostSettings()
at DotNetNuke.Services.Scheduling.SchedulingProvider.get_SchedulerMode()
at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.Halt(String SourceOfHalt)
at DotNetNuke.Services.Scheduling.DNNScheduling.DNNScheduler.Halt(String SourceOfHalt)
at DotNetNuke.Common.Initialize.StopScheduler()
at DotNetNuke.Common.Global.Application_End(Object sender, EventArgs e)


Custom event details:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I've tried creating a dedicated Application Pool for DNN in IIS but the problem still occurs.

We have recently installed a few modules but we have no idea if one of them is causing the problem and the error trace abvoe doesn't seem to pinpoint it as I'd hoped.  Ideally, we'd roll back to our last backup but we've done a huge amount of work with the new modules (before the error started to occur) so I'm reluctant to lose it all.

Any help much appreciated!

Regards,

roadie.

 
New Post
12/17/2008 3:11 AM
 

WHich kind of SQL Server do you use? MSDE has a limited number of connections, other databases may need to be reconfigured to increase the number of connections available.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
12/18/2008 10:03 AM
 

Sebastian Leupold wrote

WHich kind of SQL Server do you use? MSDE has a limited number of connections, other databases may need to be reconfigured to increase the number of connections available.

Thanks for your reply Sebastian.

I didn't install our DNN instance but I believe it will be MSDE as it was installed as part of the DNN installation process apparently - does that make sense?

Regarding the connection limit on MSDE, I was under the same impression but I found this MSDN article stating that isn't the case and that on 5 concurrent *operations* the Workload Manager introduces a slight performance penalty:
http://blogs.msdn.com/euanga/archive/2006/03/09/545576.aspx

There is an old post on these forums about this issue that Will replied to.  As with other (not DNN-related) resources I've found, he thinks it is a sign of a coding error, which made me think a faulty module might be at fault?
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/114/threadid/190132/scope/posts/Default.aspx

We have disabled the DNN Scheduler and *so far* the problem has not reocurred.   Clearly this is not a real fix.

This may be unrelated, but we are also seeing the following error in the Windows Application Event Log:

Event code: 3005 

Event message: An unhandled exception has occurred. 

Event time: 12/18/2008 2:48:48 PM 

Event time (UTC): 12/18/2008 2:48:48 PM 

Event ID: 3d010d2785f6433d90dba2768dfb8c04 

Event sequence: 442 

Event occurrence: 56 

Event detail code: 0 

 

Application information: 

    Application domain: /LM/W3SVC/1211025146/Root-1-128740717005295000 

    Trust level: Full 

    Application Virtual Path: / 

    Application Path: C:\dnnroot\ 

    Machine name: CANTARUS-2 

 

Process information: 

    Process ID: 3552 

    Process name: w3wp.exe 

    Account name: NT AUTHORITY\NETWORK SERVICE 

 

Exception information: 

    Exception type: HttpException 

    Exception message: Path '/desktopmodules/Map/Sources/Standard.Data.ascx' is forbidden. 

 

Request information: 

    Request URL: http://www.hertsurgentcare.com/desktopmodules/Map/Sources/Standard.Data.ascx 

    Request path: /desktopmodules/Map/Sources/Standard.Data.ascx 

    User host address: 66.249.66.244 

    User:  

    Is authenticated: False 

    Authentication Type:  

    Thread account name: NT AUTHORITY\NETWORK SERVICE 

 

Thread information: 

    Thread ID: 1 

    Thread account name: NT AUTHORITY\NETWORK SERVICE 

    Is impersonating: False 

    Stack trace:    at System.Web.HttpForbiddenHandler.ProcessRequest(HttpContext context)

   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Custom event details: 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any help much appreciated.

Regards,

roadie.

 
New Post
12/20/2008 10:16 AM
 

Just bumping this to see if anyone can help?

 
New Post
12/20/2008 1:58 PM
 

there seem to be an issue with the configuration of the MAP module. either correct the settings or delete the module and clear the recycle bin.

regarding the pool size issue, please validate, which version of SQL server you are using (SQL 2000 / MSDE 2000 /SQL Server 2005 / 2008 Express or above).


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Unhandled Error: ...max pool size was reachedUnhandled Error: ...max pool size was reached


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out