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.
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?
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:
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272
Seems your log table is 'full'.
Clear the table 'umbracoLog'.
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?
Im having the same problem.
But how can the table be full?
What does that even mean?
is working on a reply...