Sometimes we enconter this error on our server hosting some Umbraco sites:
Server Error in '/'
Application.
The wait operation timed out
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.ComponentModel.Win32Exception: The wait
operation timed out
Source Error:
An unhandled exception was
generated during the execution of the current web request. Information
regarding the origin and location of the exception can be identified using
the exception stack trace below.
Stack Trace:
[Win32Exception (0x80004005): The
wait operation timed out]
[SqlException (0x80131904):
Timeout expired.The timeout period
elapsed prior to completion of the operation or the server is not
responding.]
@Luca, did you ever get to the root cause of this? We are running 4.7.1.1. But we are only seeing the time out when trying to login or access the Content node within the Content section (where you can change password, etc). I'm wondering if Umbraco is starting to crack due to the size of the content tree, as this is a multi language, multi site setup, so there are a very high number of pages, images, etc, and the database is > 2GB too.
We're also having this issue on an Umbraco 4.11.8 site. At first glance this seems to be related to the amount of content (this is a large site content-eise and we have a whole bunch of other sites that are on 4.11 and 6.1 which don't exhibit this issue). The strange thing however is that it happens only on production - as soon as we take the production database down, the issue is not reproducible on other (i.e. staging, test, etc) environments (which starts to move us away from this actually being a content issue).
The current workaround is simply to remove the LastEdits control from the dashboard (not really a solution for me however because the client wants this functionality).
Hi @Joseph. It turned out that our issue was caused by the umbracoLog database table, which was over 2GB in size. We removed all non audit trail related entries (there were many error entries), and then cleared out any records that were over a year old. Once this was done the site loaded very fast. So it would seem there are issues with CMS components that access a large umbracoLog table. Hope this solves your issues.
Server Error "The wait operation timed out "
Sometimes we enconter this error on our server hosting some Umbraco sites:
Server Error in '/' Application.
The wait operation timed out
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.ComponentModel.Win32Exception: The wait operation timed out
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[Win32Exception (0x80004005): The wait operation timed out]
[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(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) +392
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) +815
System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) +4515
System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() +61
System.Data.SqlClient.SqlDataReader.get_MetaData() +138
System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +6738869
System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds) +6741487
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite) +586
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) +107
System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) +288
System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) +237
Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) +262
umbraco.DataLayer.SqlHelpers.SqlServer.SqlServerHelper.ExecuteReader(String commandText, SqlParameter[] parameters) +26
umbraco.DataLayer.SqlHelper`1.ExecuteReader(String commandText, IParameter[] parameters) +143
[SqlHelperException: Umbraco Exception (DataLayer): SQL helper exception in ExecuteReader]
umbraco.DataLayer.SqlHelper`1.ExecuteReader(String commandText, IParameter[] parameters) +256
umbraco.BusinessLogic.Log.GetLogReader(User user, LogTypes Type, DateTime SinceDate) +362
dashboardUtilities.LatestEdits.Page_Load(Object sender, EventArgs e) +353
System.Web.UI.Control.LoadRecursive() +71
System.Web.UI.Control.LoadRecursive() +190
System.Web.UI.Control.LoadRecursive() +190
System.Web.UI.Control.LoadRecursive() +190
System.Web.UI.Control.LoadRecursive() +190
System.Web.UI.Control.LoadRecursive() +190
System.Web.UI.Control.LoadRecursive() +190
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3178
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.18446
The server is a Windows Server 2008R2 with IIS 7.5/.NET Framework 4.5 and SQL EXPRESS 2008.
Someone have encountered the same problem ?
Thanks for any suggestion...
Hi Luca and welcome to our :)
Do you control these servers yourself or is it a shared hosting solution?
If it's shared hosting I guess you should contact the hosting company to have them investigate what is going on.
What version of Umbraco are you using? And are there any custom API integration done?
/Jan
Hi Jan,
We directly have control of the server, the Umbraco version are 4.9.1 (the most), 4.11.4 and some new 7 with no custom API integration.
The error occurs occasionally, and only on some site that use SQL EXPRESS; some site with 4.9.1 and SQLCE are not affected by the problem.
Thanks !
@Luca, did you ever get to the root cause of this? We are running 4.7.1.1. But we are only seeing the time out when trying to login or access the Content node within the Content section (where you can change password, etc). I'm wondering if Umbraco is starting to crack due to the size of the content tree, as this is a multi language, multi site setup, so there are a very high number of pages, images, etc, and the database is > 2GB too.
We're also having this issue on an Umbraco 4.11.8 site. At first glance this seems to be related to the amount of content (this is a large site content-eise and we have a whole bunch of other sites that are on 4.11 and 6.1 which don't exhibit this issue). The strange thing however is that it happens only on production - as soon as we take the production database down, the issue is not reproducible on other (i.e. staging, test, etc) environments (which starts to move us away from this actually being a content issue).
The current workaround is simply to remove the LastEdits control from the dashboard (not really a solution for me however because the client wants this functionality).
Hi @Joseph. It turned out that our issue was caused by the umbracoLog database table, which was over 2GB in size. We removed all non audit trail related entries (there were many error entries), and then cleared out any records that were over a year old. Once this was done the site loaded very fast. So it would seem there are issues with CMS components that access a large umbracoLog table. Hope this solves your issues.
The "Log" section on this link helped work out which log entries to keep for audit trail purposes, but I think it's quite old:
http://our.umbraco.org/wiki/recommendations/recommended-reading-for-it-administrators/best-practices-for-live-deployment
is working on a reply...