1. Hello Guest!

    Thank you for visiting the ClubRunner Community website, you can login using your ClubRunner account information by clicking the login link on the top of every page.
    Dismiss Notice

[Resolved] ALL SITES ARE DOWN

Discussion in 'General' started by Cheryl Warren on Aug 31, 2019.

  1. Cheryl Warren

    By:Cheryl WarrenAug 31, 2019
    New Community Member

    Joined:
    Sep 11, 2017
    Messages:
    3
    Likes Received:
    1
    Gender:
    Female
    Occupation:
    Marketing Consultant
    Location:
    Marketing Consultant
    Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401)
    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.IO.FileLoadException: Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401)

    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:

    [FileLoadException: Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401)]
    System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck) +0
    System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) +139
    System.Activator.CreateInstance(Type type, Boolean nonPublic) +105
    System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark) +1431
    System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) +184
    System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture) +27
    System.Web.HttpRuntime.CreateNonPublicInstance(Type type, Object[] args) +80
    System.Web.HttpApplication.BuildIntegratedModuleCollection(List`1 moduleList) +234
    System.Web.HttpApplication.GetModuleCollection(IntPtr appContext) +1153
    System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +139
    System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +168
    System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +277
    System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +369

    [HttpException (0x80004005): Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401)]
    System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +532
    System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +111
    System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +714


    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.3429.0
     
    Zach likes this.
  2. Zach

    By:ZachAug 31, 2019
    Moderator
    ClubRunner Team

    Joined:
    Jun 5, 2017
    Messages:
    311
    Likes Received:
    54
    Gender:
    Male
    Occupation:
    Product Specialist
    Location:
    ClubRunner
    Hi Cheryl,

    Thank you for the heads up. Our team has been working on investigating the issue and we're working to resolve it as quickly as possible.
     
  3. Divya

    By:DivyaAug 31, 2019
    Moderator
    ClubRunner Team

    Joined:
    Jun 10, 2017
    Messages:
    1
    Likes Received:
    0
    Hi Cheryl,

    Our team identified the root cause of the issue and have successfully resolved it. Your website is now back up. Thank you again for your patience.
     
Top