Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Dexter 17 posts 67 karma points
    Sep 21, 2012 @ 15:55
    Dexter
    0

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

    Umbraco 4.9.0 / Windows Server 2008 R2 / IIS7.5 / Asp.Net 4.0

    After upgrading from v4.8.1 to v4.9.0 when I log into the cms, I am presented with the following error in the right pane.  Has anybody encountered this error?  If so, what was your resolution?

     

    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: 

    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: 

    [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) +404
       System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() +412
       System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1363
       System.Data.SqlClient.SqlDataReader.ConsumeMetaData() +59
       System.Data.SqlClient.SqlDataReader.get_MetaData() +118
       System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +6387937
       System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) +6389506
       System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) +538
       System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) +28
       System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) +256
       System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) +228
       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) +148
    
    [SqlHelperException: Umbraco Exception (DataLayer): SQL helper exception in ExecuteReader]
       umbraco.DataLayer.SqlHelper`1.ExecuteReader(String commandText, IParameter[] parameters) +261
       umbraco.BusinessLogic.Log.GetLogReader(User user, LogTypes Type, DateTime SinceDate) +362
       dashboardUtilities.LatestEdits.Page_Load(Object sender, EventArgs e) +353
       System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +25
       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) +3064
    


    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272

     

  • Stefan Kip 1614 posts 4131 karma points c-trib
    Sep 21, 2012 @ 16:33
    Stefan Kip
    1

    Seems your log table is 'full'.

    Clear the table 'umbracoLog'.

  • Pete 152 posts 176 karma points
    Feb 28, 2013 @ 12:36
    Pete
    0

    I'm going to open this up again - we're experiencing the same thing with great frequency at the moment: 4+ times a day. 

    We have been using the truncate umbracoLog solution to get it going again. What is interesting is that the umbracoLog table is empty and logging is switched off. Truncating the umbracoLog table takes a very long time. 4 minutes and 20 seconds on the most recent run. 

    This command does actually give us access to the CMS again. 

    Any thoughts on what could be causing a timeout on this table and why truncating the empty table, with logging switched off anyway, allows access again?

  • Anders Brohäll 295 posts 561 karma points c-trib
    Mar 12, 2013 @ 11:27
    Anders Brohäll
    0

    Im having the same problem. 

    But how can the table be full?
    What does that even mean? 

Please Sign in or register to post replies

Write your reply to:

Draft