Thread: Error message (in admin page and customer change address)

Hi forum members!

We are having a problem with our ASPDNSF site. We are getting an error message (Timeout Expired) -- attached below.

We started having this issue a few months ago, but only sometimes, upon reloading the page, it will work normally.

Then about 2 months ago, the error occurred much more often. And we had to reload the page multiple times before the page would work.

Now, no matter how many times we reload, it doesn't work. It is affecting our sales greatly.

Currently, customers can still view the catalog site, and can add to cart and checkout, but some of them are starting to see the error during browsing (which is alarming).

We were wondering what could cause this issue? We haven't been doing the monthly maintenance since the beginning, will that be a problem? (we are worried that large customers will get their carts emptied).

Are there any other reasons this might happen?

Many thanks in advance.

Our site ver:
AspDotNetStorefront ML 8.0.0.0/8.0.0.0



########
Server Error in '/' Application.

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

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.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

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:


[SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.]
System.Data.SqlClient.SqlConnection.OnError(SqlExc eption exception, Boolean breakConnection) +1950890
System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException exception, Boolean breakConnection) +4846875
System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject stateObj) +194
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +2392
System.Data.SqlClient.SqlDataReader.ConsumeMetaDat a() +33
System.Data.SqlClient.SqlDataReader.get_MetaData() +83
System.Data.SqlClient.SqlCommand.FinishExecuteRead er(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +297
System.Data.SqlClient.SqlCommand.RunExecuteReaderT ds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) +954
System.Data.SqlClient.SqlCommand.RunExecuteReader( CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) +162
System.Data.SqlClient.SqlCommand.RunExecuteReader( CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) +32
System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior behavior, String method) +141
System.Data.SqlClient.SqlCommand.ExecuteReader() +89
AspDotNetStorefrontCommon.DB.GetRS(String Sql, SqlConnection dbconn) in C:\ASPDNSF\Builds\ML8000\ASPDNSFCommon\Topic.cs:99
AspDotNetStorefront.selectaddress.InitializePageCo ntent() +1028
AspDotNetStorefront.selectaddress.Page_Load(Object sender, EventArgs e) +1023
System.Web.Util.CalliHelper.EventArgFunctionCaller (IntPtr fp, Object o, Object t, EventArgs e) +14
System.Web.Util.CalliEventHandlerDelegateProxy.Cal lback(Object sender, EventArgs e) +35
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +50
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627

Version Information: Microsoft .NET Framework Version:2.0.50727.3615; ASP.NET Version:2.0.50727.3614

I'll say first of all, you should definitely be doing monthly maintenance .. doesnt have to really be monthly but it should be done on a regular basis.

As for the timeout itself, I would suspect the load on the server. Is this a shared server? Perhaps if it is your host has been adding more and more sites which would explain the more increased frequency of issues.

Thank you ssgumby

Re:
We will start doing the monthly maintenance. We never did it because we were worried that large customers who have been adding to cart over a few months might lose their cart and we will lose a very big sale.

Is doing the maintenance safe? Have you encountered any issues during or right after maintenance? (Any suggestions on the best way to do the monthly maintenance will be greatly appreciated)

Re: Server load
We are actually having less traffic then we had before (when the error didn't occur) and our server is a dedicated server, so it's not being shared with other sites.

Maybe what is happening is because we haven't done the maintenance for so long, the database is very bloated and thus it is timing out.

How do I find out if our database is too big?
(Now come to think of it, it was around the time when some customers were complaining that their carts were disappearing, that we turned off (in app_config)
carts and wishlist expiring. And it seems that this issues start happening soon after.. Could that be it?)


Thanks in advance

With regards to monthly maintenance. The only issue i've encountered is the maintenance timing out. Ive had to run it repeatedly to get it to complete. Unfortunately depending on the options you select you could screw up current customers shopping (clearing their cart, etc)) ... because of this you should run it very late ... I typically run mine around 4 am eastern ... this makes it late for everyone in the US and traffic is minimal.

Thanks ssgumby

Great advice! I will try it early in the morning too.

I wonder if any other forum members are encountering the same issues that I'm having.

If someone from ASPDNSF could provide a little more technical analysis of my error messages, it would be great.

In the meantime, I will take ssgumby's advice

Thanks again!