+1-888-365-2779
Try Now
More in this section

Forums / Bugs & Issues / Error Caching

Error Caching

12 posts, 0 answered
  1. Sean
    Sean avatar
    271 posts
    Registered:
    31 May 2006
    17 Sep 2007
    Link to this post
    Hi Guys,

    I have a problem with the way that Sitefinity caches an error when the site encounters certain errors for example, I have a website that is hosted with a provider whose database is unfortunately not the most stable one in the world, I am trying to move them.  Anyway the problem I am getting because of this, is every once in a while when the Application loads up for the first time and there is a SqlTimeOutException for example, the error message is cached and any subsequent requests are then also sent the error until the application is reset, which in this case is only when I modify the web.config file meaning the website could be down for an hour or 2 before I am told about this.

    So is there a way of disabling this caching, and why does it do this anyway, surely all requests after this should try to load the application again if it hasn't loaded successfully?

    Thanks
    Sean
  2. Vlad
    Vlad avatar
    498 posts
    Registered:
    15 Jul 2016
    17 Sep 2007
    Link to this post
    Hi Sean,

    You are right.
    Unfortunately, currently there is no way to disable exception caching.
    We already made the appropriate improvements on our ManagerBase class, so this problem won't persist in the upcoming Sitefinity 3.1 release.

    You Telerik points have been updated for pointing this issue out.

    Sincerely yours,
    Vlad
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
  3. Timothy Lee Russell
    Timothy Lee Russell avatar
    2 posts
    Registered:
    14 Feb 2003
    30 Sep 2007
    Link to this post
    I am having problems with this as well...

    I am using 3.0 SP2

    Thanks,
    Timothy
  4. Vlad
    Vlad avatar
    498 posts
    Registered:
    15 Jul 2016
    01 Oct 2007
    Link to this post
    Hello Timothy,

    It is fixed in Sitefinity 3.1.

    Greetings,
    Vlad
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
  5. Sean
    Sean avatar
    271 posts
    Registered:
    31 May 2006
    16 Dec 2007
    Link to this post
    Hi Guys,

    This problem doesn't seem to be entirely fixed in 3.1.  The exception still caches if the SQL database connection fails when the application first loads.

    Thanks
    Sean
  6. Vlad
    Vlad avatar
    498 posts
    Registered:
    15 Jul 2016
    17 Dec 2007
    Link to this post
    Hi Sean,

    Unfortunately, we cannot reproduce the problem with Sitefinity 3.1.
    We just did a quick test and it works as expected. We did the following:
    - before starting the site, stopped SQL Server;
    - tried to load the site and exception was thrown;
    - started SQL Server;
    - loaded the site without exception.

    Could you please give us detailed instructions how to reproduce your case?

    Thank you for the assistance.

    Regards,
    Vlad
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
  7. Sean
    Sean avatar
    271 posts
    Registered:
    31 May 2006
    17 Dec 2007
    Link to this post
    Hi,

    I followed those exact steps that you used and I still get the exception when Ioad the site.  I am only using 3.1 SP1 and not 3.1 SP2, is it possible that this is something that only got fixed in SP2?  Are you are sure the application have never been loaded before you stopped the SQL Server Service?

    Thanks
    Sean
  8. Vlad
    Vlad avatar
    498 posts
    Registered:
    15 Jul 2016
    17 Dec 2007
    Link to this post
    Hi Sean Molam,

    It's very strange, I just tried again, but with v3.1 SP1 and everything works fine. Actually, this was fixed on September 17th. Could you please send us the StackTrace of the exception?

    Sincerely yours,
    Vlad
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
  9. Sean
    Sean avatar
    271 posts
    Registered:
    31 May 2006
    17 Dec 2007
    Link to this post
    Hi Vlad,

    I think I have figured out what I did differently:

    - before starting the site, stopped SQL Server;
    - tried to load the site and exception was thrown;
    - refreshed the error page a few times
    - started SQL Server;
    - refreshing the page then shows only the error page from that point on until the application is reloaded:

    Here is the stack trace anyway:

    Server Error in '/www.zimweb.com.au' Application.

    An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

    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: An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

    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): An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)]
    System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +435
    System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82
    System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
    System.Data.SqlClient.SqlConnection.Open() +111
    Nolics.ORMapper.DataProviders.SqlServer2005Provider.newConnection(String connectionString) +37
    Nolics.ORMapper.DataProviders.SQLDataProvider.GetConnection() +52
    Nolics.ORMapper.DataProviders.SqlServer2005Provider.GetSQLBuilder() +25
    Nolics.ORMapper.DataProviders.SQLDataProvider.ExecuteKeyQuery(DataSet queries, Boolean fPrimaryKey) +45
    Nolics.ORMapper.DataProviders.SQLDataProvider.QueryByPrimaryKey(DataSet keys) +7
    Nolics.ORMapper.Base.PrimeryKeyQuery.LoadPKQuery() +38
    Nolics.ORMapper.Base.OdbClass.LoadByPrimaryKey(IOdbClass primaryKey, OdbDataProvider provider, ObDataCache cache) +79
    Telerik.Cms.Data.DefaultProvider.GetCmsPage(Guid id) +103
    Telerik.Cms.CmsManager.GetCmsPage(Guid id) +26
    Telerik.Cms.Web.InternalPage.OnPreInit(EventArgs e) +122
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +663


    Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433

  10. Sean
    Sean avatar
    271 posts
    Registered:
    31 May 2006
    17 Dec 2007
    Link to this post
    Sorry that isn't the correct Trace this is it:

    An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

    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: An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

    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): An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)]
    Nolics.ORMapper.DataProviders.SQLDataProvider.Open() +121
    Telerik.DataAccess.NolicsHelper.SetConnection(String connectionName, String providerName) +604
    Telerik.DataAccess.AspnetProviders.TelerikRoleProvider.Initialize(String name, NameValueCollection config) +376
    System.Web.Configuration.ProvidersHelper.InstantiateProvider(ProviderSettings providerSettings, Type providerType) +411

    [TypeInitializationException: The type initializer for 'Telerik.Localization.LocalizationManager' threw an exception.]
    Telerik.Localization.LocalizationManager.get_PersistenceMode() +0
    Telerik.Cms.Web.CmsHttpModule.SetCurrentCulture(HttpContext context, String& path, String query, Boolean& redirected) +34
    Telerik.Cms.Web.CmsHttpModule.BeginRequest(Object sender, EventArgs e) +1224
    System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
    System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64


    Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433

  11. Vlad
    Vlad avatar
    498 posts
    Registered:
    15 Jul 2016
    17 Dec 2007
    Link to this post
    Hello Sean,

    Thank you for the additional information. We finally reproduced the problem and have an idea what is causing it - probably it is because the provider initializes itself in a static class... Anyway, we will try to address this issue for the next release.

    You Telerik points have been updated.

    Sincerely yours,
    Vlad
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
  12. Sean
    Sean avatar
    271 posts
    Registered:
    31 May 2006
    17 Dec 2007
    Link to this post
    Excellent, thanks.
Register for webinar
12 posts, 0 answered