| |
Main
Date: 09 Jan 2007 12:19:12
From: radix33@gmail.com
Subject: The Golf Channel new website redesign woes....
|
I just love server error messages: Server Error in '/' Application. 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. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: 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. Source Error: The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL: 1. Add a "Debug=true" directive at the top of the file that generated the error. Example: <%@ Page Language="C#" Debug="true" % > or: 2) Add the following section to the configuration file of your application: <configuration > <system.web > <compilation debug="true"/ > </system.web > </configuration > Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode. Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario. Stack Trace: [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.] System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction) +396 System.Data.SqlClient.SqlConnection.Open() +386 TGC.Track.TrackPageView(Boolean Redirect) +404 TGC.Track.TrackPageView() +7 ASP.Global_asax.Application_EndRequest(Object sender, EventArgs e) +193 System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() +60 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +87 Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET Version:1.1.4322.2032
|
|
| |
Date: 09 Jan 2007 23:24:45
From: Dave Lee
Subject: Re: The Golf Channel new website redesign woes....
|
<radix33@gmail.com > wrote in message news:1168373951.485410.219720@i39g2000hsf.googlegroups.com... > I just love server error messages: > > > Server Error in '/' Application. > 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. > Description: An unhandled exception occurred during the execution of > the current web request. Please review the stack trace for more > information about the error and where it originated in the code. > > Exception Details: 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. > > Source Error: > > The source code that generated this unhandled exception can only be > shown when compiled in debug mode. To enable this, please follow one of > the below steps, then request the URL: > > 1. Add a "Debug=true" directive at the top of the file that generated > the error. Example: > > <%@ Page Language="C#" Debug="true" %> > > or: > > 2) Add the following section to the configuration file of your > application: > > <configuration> > <system.web> > <compilation debug="true"/> > </system.web> > </configuration> > > Note that this second technique will cause all files within a given > application to be compiled in debug mode. The first technique will > cause only that particular file to be compiled in debug mode. > > Important: Running applications in debug mode does incur a > memory/performance overhead. You should make sure that an application > has debugging disabled before deploying into production scenario. > > Stack Trace: > > [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.] > > System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnec tionString > options, Boolean& isInTransaction) +396 > System.Data.SqlClient.SqlConnection.Open() +386 > TGC.Track.TrackPageView(Boolean Redirect) +404 > TGC.Track.TrackPageView() +7 > ASP.Global_asax.Application_EndRequest(Object sender, EventArgs e) > +193 > > System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep. Execute() > +60 > System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& > completedSynchronously) +87 > > > Version Information: Microsoft .NET Framework Version:1.1.4322.2032; > ASP.NET Version:1.1.4322.2032 > Is this from a swinger or a hitter or ... Oops - my error. At first I thought you were quoting TGM :-) dave
|
| |
Date: 09 Jan 2007 14:21:44
From: wtrplnet
Subject: Re: The Golf Channel new website redesign woes....
|
<radix33@gmail.com > wrote in message news:1168373951.485410.219720@i39g2000hsf.googlegroups.com... >I just love server error messages: > > > Server Error in '/' Application. > 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. > Description: An unhandled exception occurred during the execution of > the current web request. Please review the stack trace for more > information about the error and where it originated in the code. > > Exception Details: System.InvalidOperationException: Timeout expired. > The timeout period elapsed prior to obtaining a connection from the > Server error messages are intended to give the administrator/web developer a clue what's going wrong (they usually don't!) They are of little or no use to the end user. Alan ----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet News==---- http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups ----= East and West-Coast Server Farms - Total Privacy via Encryption =----
|
|