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

Forums / Bugs & Issues / Getting an error - An unhandled exception was generated during the execution of the current web request

Getting an error - An unhandled exception was generated during the execution of the current web request

2 posts, 0 answered
  1. martin
    martin avatar
    43 posts
    Registered:
    10 Feb 2009
    26 Mar 2013
    Link to this post
    Hi, I know this should really be in the 3.x Bugs & Issues area... but for whatever reason I'm unable to start a new thread there - hence putting it here instead.

    We have a small *test* Sitefinity site which is still running 3.7

    The site is there to test a 3rd party bespoke Membership Provider, which should allow front-end site visitors to login to a remote 3rd party database and thus be assigned a Sitefinity role, to allow them access to restricted pages.

    The test site was working the last time I looked (quite some time ago) but since the server it resides on had a crash, I'm just getting an error report and I don't know why.

    +++++++++++++++++++++++++++++++
    Server Error in '/tsgtest' Application.Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.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: Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.

    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): Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.]
    Nolics.ORMapper.DataProviders.SQLDataProvider.Open() +123
    Telerik.DataAccess.NolicsHelper.SetConnection(String connectionName, String providerName) +2607
    Telerik.Cms.Data.DefaultProvider.Initialize(String name, NameValueCollection config) +452
    Telerik.ManagerBase`1.InstantiateProvider(ProviderSettings providerSettings, Type providerType) +1187
    Telerik.ManagerBase`1.InstantiateProvider(ProviderSettings providerSettings) +147
    Telerik.ManagerBase`1.SetProvider(String providerName) +395
    Telerik.ManagerBase`1..ctor(String providerName) +207
    Telerik.ManagerBase`1..ctor() +35
    Telerik.Cms.CmsManager..ctor() +29
    Telerik.Cms.CmsWorkflowService..ctor() +65
    Telerik.Cms.CmsWorkflowService..cctor() +39

    [TypeInitializationException: The type initializer for 'Telerik.Cms.CmsWorkflowService' threw an exception.]
    Telerik.Cms.CmsWorkflowService.Initialize() +0
    Telerik.Cms.CmsManager.OnInitialized() +27
    Telerik.ManagerBase`1.Initialize() +687
    Telerik.ManagerBase`1..ctor(String providerName) +50
    Telerik.ManagerBase`1..ctor() +35
    Telerik.Cms.CmsManager..ctor() +29
    Telerik.Cms.Web.UrlHelper.Initialize() +40
    Telerik.Cms.Web.CmsHttpModule.Init(HttpApplication context) +146
    System.Web.HttpApplication.InitModulesCommon() +65
    System.Web.HttpApplication.InitModules() +43
    System.Web.HttpApplication.InitInternal(HttpContext context, HttpApplicationState state, MethodInfo[] handlers) +729
    System.Web.HttpApplicationFactory.GetNormalApplicationInstance(HttpContext context) +298
    System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +107
    System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +289

    Version Information: Microsoft .NET Framework Version:2.0.50727.3643; ASP.NET Version:2.0.50727.3634
    ++++++++++++++++++++++++++++++++++

    Anyone know if there's an obvious solution to what the error message is suggesting?

    Cheers,
    m.

    edit - thinking about it, I should mention that the crash the server had corrupted the server's Admin password and this wasn't amendable. Thus a secondary Admin account was created - with different username & password. It might be saying that the SQL database is trying to gain authority from the defunct Admin password. But that's me guessing and I wouldn't know where to change this.
  2. Stanislav Velikov
    Stanislav Velikov avatar
    1113 posts
    Registered:
    22 Sep 2016
    29 Mar 2013
    Link to this post
    Hi,

    Refer to this post for the solution deleting the directory for SQL Express. This will allow the site to connect to the database again, create a backup just in case.

    Greetings,
    Stanislav Velikov
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
2 posts, 0 answered