I've suddenly started to get this with a new 4.10 install. Did you get anywhere with it?

EDIT:

I've done a little digging and for me it was due to my Global.asax.cs not inheriting from the UmbracoApplication class (they must have tweaked it recently).

If you have your own Global.asax.cs file. Ensure that it looks like this: 

public class Global : global::Umbraco.Web.UmbracoApplication 
{
}

Ohh sry mate for not providing the solution to my own problem, glad u found out that fast. Took me a day or so  :) 

For me worked this procedure:

1. delete global.asax from server

2. refresh site

3. copy again global.asax on server

4 refresh site

Gionata Aladino Canova

I've the very same problem ATM - none of the above solutions works for me... - any idears...? >:-(

In my case, the AppStart class is causing it.

I couldn't find anyway to replace my global.asax :(

Anyone found a solution for this. 
Recently updated a site to v6.1.3 and this Resolution is not frozen error shows up once in a while. Sometimes it goes away after a refresh, seems to always work if I replace the Global.aspx and restart the site but it is not really a solution :/

Thanks

Started getting this too having upgraded from 6.0.5 to 6.1.3

I created this error by adding a const (therefore effectively static) member variable pointing at the ContentTypeService to my ApplictionStarted event handler.

Daft? Maybe, but might be of use to somebody.

Rich

So this is what the error looks like, it just appeared on a new install of v.6.1.2, so it's not related to upgrading...

This might have something to do with Lucene indices rebuilding.  I upgraded a QA environment to 6.1.4 then propogated it to PRD and received the same message.  After picking my jaw up off the floor, I nuked the indices in the TEMP folder and waited about an hour (You can't log in to Umbraco until they are rebuilt anyway).  Everything seem to come back up just fine afterwards.

I get this when installing some nuget packages with Umbrao v6.1. Some packages change assembly bindings in web.config System.Net.Http back to 2.0.0.0.

Manually changing back to 4.0.0.0 fixes error:

      <dependentAssembly>

        <assemblyIdentity name="System.Net.Http" publicKeyToken="b03f5f7f11d50a3a" />

        <bindingRedirect oldVersion="0.0.0.0-2.0.0.0" newVersion="4.0.0.0" />

      </dependentAssembly>

I fixed this by refreshing the iss application pool for the domain

is working on a reply...