Home Analyst Portal

Expanding Max Pool Size to raise the number of SQL connections

Dakota_GreenDakota_Green Member Advanced IT Monkey ✭✭✭
edited July 2016 in Analyst Portal
Hello Community!

Microsoft SQL Server has a set threshold of connections that can take from the connection pool. This is not very helpful if you have a huge Help Desk, or if SQL Server/asp.net is not closing any of those connections. It may manifest itself as the following error in the Web Console log:
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.

To work around this, we can add a Max Pool Size to your Web.Config file. We recommend starting at 300, and then working your way up depending on load.

To accomplish, do the following:

1. On the Portal server, navigate to C:\inetpub\CiresonPortal (or wherever you installed the Cireson Portal at)
2. Locate the file "Web.config" and then open in a text editor (Notepad should do the trick)
3. Locate the following line:
<add name="ServiceManagementDatabase" connectionString="Server=(DOMAIN NAME);Database=ServiceManagement;Trusted_Connection=True;" />

At the end of

add the following:
Max Pool Size=300;

The line should now look like this:
 <add name="ServiceManagementDatabase" connectionString="Server=(DOMAIN NAME);Database=ServiceManagement;Trusted_Connection=True;Max Pool Size=300;" />

I am currently drafting a Knowledge Base article that will include details on some of the most common errors that come up in both the Cache Builder and Web Console log files. This will be included in the article.

Hopefully this helps!


Sign In or Register to comment.