U4-2174 - Umbraco 6.1.0 Beta, Error : Resolution is not frozen, it is not yet possible, to get gains from it

Created by Stéphane Bouchard-Pagé 01 May 2013, 18:37:40 Updated by Stephan 06 Mar 2014, 07:19:33

Is duplicated by: U4-2376

Relates to: U4-2376

Hello, I updated my website, from version 6.0.4 to 6.1.0 Beta (nightly built 89). After following the standard procedure for upgrading, I got an error:

" Resolution is not frozen, it is not yet possible, to get gains from it.

Description: An unhandled exception occurred falling on 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.InvalidOperationException: Resolution is not frozen, it is not yet possible, to get gains from it.

Source Error:

An unhandled exception was generated falling on the execution of the current web request. Information regarding the origin and location of the exception can be APPROBATION using the exception stack traces below.

Stack Trace:

[InvalidOperationException: Resolution is not frozen, it is not yet possible, to get gains from it.]    Umbraco.Core.ObjectResolution.Resolution.EnsureIsFrozen () in c: \ ... \ Umbraco.Core \ ObjectResolution \ Resolution.cs: 32    Umbraco.Core.ObjectResolution.SingleObjectResolverBase 2.get_Value () in c: \ ... \ Umbraco.Core \ ObjectResolution \ SingleObjectResolverBase.cs: 99    Umbraco.Core.Persistence.RepositoryResolver.get_Factory () in c: \ ... \ Umbraco.Core \ Persistence \ RepositoryResolver.cs: 34    <. Ctor> () Umbraco.Core.Services.ServiceContext b__0 in c:. \ ... \ Umbraco.Core \ Services \ ServiceContext.cs: 38    System.Lazy1.CreateValue () 455    System.Lazy 1.get_Value () 14440394    . Umbraco.Core.Services <> c__DisplayClassd <BuildServiceCache> b__8 () in c:. \ ... \ Umbraco.Core \ Services \ ServiceContext.cs: 72    System.Lazy1.CreateValue () 14439352    System.Lazy `1.LazyInitValue () 476    Umbraco.Core.Services.ServiceContext.get_FileService () in c: \ ... \ Umbraco.Core \ Services \ ServiceContext.cs: 140    Umbraco.Web.Routing.PublishedContentRequestEngine.FindTemplate () 901    Umbraco.Web.Routing.PublishedContentRequestEngine.FindPublishedContentAndTemplate () 272    Umbraco.Web.Routing.PublishedContentRequestEngine.PrepareRequest () 103    Umbraco.Web.UmbracoModule.ProcessRequest (HttpContextBase httpContext) 738    System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute () +80    System.Web.HttpApplication.ExecuteStep (IExecutionStep step, Boolean & completedSynchronously) +165

Version Information: Microsoft NET Framework Version: 4.0.30319; ASP.NET Version:. 4.0.30319.18033 "

For the purpose of my test, I dowloaded the source code from codeplex (V6.1). Into the file "C:...\umbraco_7bafbb416666\src\Umbraco.Core\ObjectResolution\Resolution.cs", I commented the lines 30 and 31. Then I built the solution and I copied the dll to the umbraco bin folder. After done this steps, I got no error, all was fine.

3 Attachments

Download UmbracoTraceLog.txt

Download Umbraco.Core.dll.zip

Comments

Sarah Green 25 Jun 2013, 18:33:45

This suddenly appeared on my site (v 6.1.1) causing html 500 errors on both front end and back end ... can access XSLT files, macros, data types, templates, stylesheets (ie everything on the file system) but document types display 500 error and content/media have disappeared (tho' umbraco.config etc still exist ok on file system). Suggests it may be a database error but can connect to the database fine manually.

The error log shows these messages:

2013-06-25 19:07:12,484 [56] INFO Umbraco.Core.PluginManager - [Thread 9] Starting resolution types of umbraco.BusinessLogic.Actions.IActionHandler 2013-06-25 19:07:12,484 [70] ERROR Umbraco.Core.UmbracoApplicationBase - [Thread 70] An unhandled exception occurred System.InvalidOperationException: Resolution is not frozen, it is not yet possible to get values from it. at Umbraco.Core.ObjectResolution.Resolution.EnsureIsFrozen() at Umbraco.Core.ObjectResolution.SingleObjectResolverBase2.get_Value() at Umbraco.Core.Services.ServiceContext.<.ctor>b__0() at System.Lazy1.CreateValue() at System.Lazy1.LazyInitValue() at System.Lazy1.get_Value() at Umbraco.Core.Services.ServiceContext.<>c__DisplayClasse.b__9() at System.Lazy1.CreateValue() at System.Lazy1.LazyInitValue() at System.Lazy`1.get_Value() at Umbraco.Core.Services.ServiceContext.get_FileService() at Umbraco.Web.Routing.PublishedContentRequestEngine.FindTemplate() at Umbraco.Web.Routing.PublishedContentRequestEngine.FindPublishedContentAndTemplate() at Umbraco.Web.Routing.PublishedContentRequestEngine.PrepareRequest() at Umbraco.Web.UmbracoModule.ProcessRequest(HttpContextBase httpContext) at Umbraco.Web.UmbracoModule.b__7(Object sender, EventArgs e) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) 2013-06-25 19:07:12,500 [56] INFO Umbraco.Core.PluginManager - [Thread 9] Completed resolution of types of umbraco.BusinessLogic.Actions.IActionHandler, found 1 (took 15ms)

Followed by many repetitions of:

2013-06-25 19:07:12,734 [29] ERROR Umbraco.Core.UmbracoApplicationBase - [Thread 29] An unhandled exception occurred System.InvalidOperationException: Resolution is not frozen, it is not yet possible to get values from it. at Umbraco.Core.ObjectResolution.Resolution.EnsureIsFrozen() at Umbraco.Core.ObjectResolution.SingleObjectResolverBase2.get_Value() at Umbraco.Core.Services.ServiceContext.<.ctor>b__0() at System.Lazy1.CreateValue() at System.Lazy1.LazyInitValue() at System.Lazy1.get_Value() at Umbraco.Core.Services.ServiceContext.<>c__DisplayClasse.b__9() at System.Lazy1.CreateValue() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Lazy1.get_Value() at Umbraco.Core.Services.ServiceContext.get_FileService() at Umbraco.Web.Routing.PublishedContentRequestEngine.FindTemplate() at Umbraco.Web.Routing.PublishedContentRequestEngine.FindPublishedContentAndTemplate() at Umbraco.Web.Routing.PublishedContentRequestEngine.PrepareRequest() at Umbraco.Web.UmbracoModule.ProcessRequest(HttpContextBase httpContext) at Umbraco.Web.UmbracoModule.b__7(Object sender, EventArgs e) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)


Sarah Green 25 Jun 2013, 20:28:48

This seems to be related to Issue U4-2376 - at least after experiencing this error I managed to get the site working on a local version connected the the Db and I then experienced the errors as described in Issue U4-2376


Stephan 25 Jun 2013, 21:54:40

From the exception trace it looks like Umbraco is not booting correctly at all... if resolution is not frozen at the time the published content request engine runs, something's wrong. Do you have the proper UmbracoModule registered in web.config? Do you have a custom global.asax or the default one? Anything special?


Sarah Green 26 Jun 2013, 05:25:19

No special global.asax or anything (tho' have uComponents, 301URLTracker and AutoSort packages installed). I did try replacing global.asax just in case but no joy. Not sure what the "proper" UmbracoModule is - I haven't changed whatever was installed by default for that property. When the error occurred I was editing a new Template.


Stephan 26 Jun 2013, 06:53:09

You say "when the error occured"... does that mean it occured once but not all the time?


Sarah Green 26 Jun 2013, 09:13:31

Yup only the once (thankfully!)


Stephan 26 Jun 2013, 09:22:18

Well... thanfully for you ;-) That rules out a bad config since a bad config would produce the same error systematically. So in means that in some circumstances, Umbraco was trying to serve requests while not being initialized -- and that should never ever happen. In theory.

Something's putting Umbraco in an unstable state and that may be either the cause, or a consequence of, U4-2376. I'm trying to think about something...

At the moment, do you still experience one of these issues (or both) or is it stable again?


Sarah Green 26 Jun 2013, 09:33:52

It's stable atm but I'd love to hear any ideas in case it happens again


Stéphane Bouchard-Pagé 02 Jul 2013, 18:08:07

Update, for your information:

I found the reason why I got this error :)

public class TheClassName : IApplicationEventHandler { // The bad line of code. private readonly IContentService contentService = ApplicationContext.Current.Services.ContentService;

public void OnApplicationStarted(UmbracoApplicationBase umbracoApplication, ApplicationContext applicationContext)
{
    //...
}

}

It was working with Umbraco 6.0.X, but not with Umbraco 6.1.X


Søren Tidmand 03 Jul 2013, 18:46:11

I'm getting the same error after having upgraded a perfectly running version 4.11.8 to 6.1.2. The error occurs on both front and back end. Especially after making changes to templates and stylesheets - at least that's what I've noticed. And by the way ... the back end is running very slow ... very very slow ...


Moshe Kariti 05 Jul 2013, 08:42:16

Hi there - Having same issue when upgraded from 6.1.1 to 6.1.2....Any Idea?


Laurence Gillian 08 Jul 2013, 16:47:31

Am also seeing this error,

Umb 6.1.2, uComponents, uSync


Justin Moore 09 Jul 2013, 09:40:22

I just got it too, after trying to save a DAMP image. umb6.1.2, uComponents, DAMP 2.5, Eksponent CropUp, uSync


Ben Norman 23 Jul 2013, 03:50:30

I got this error on a w2k3 machine which had .net 4 installed. My site was compiled with .net 4.5 and I didn't have permissions set adequately. I got it working by targeting .net 4 in vs which changed a few of the bin files and updated the web.config. Then I updated the permissions on the www root folder to allow changing files and its working now.


Sarah Green 20 Aug 2013, 11:34:16

Still experiencing this now and again on at least 2 sites running 6.0.5 and 6.1.1 .... its making it rather impossible to use Umbraco since it seems whenever I make a change there is a risk of this kicking in and bringing the site down! Any news on a fix please?

[PS: Touching the web.config seems to fix the problem and bring the site back up but re-starting the website from IIS doesn't]


Stephan 20 Aug 2013, 15:52:55

OK, would like to try to spend some time on that one... Stéphane, can you elaborate on why that was causing an error?

To all: so the site is running correctly, then something happens, and you start to get that exception on every request. Correct?

Sarah, you seem to imply that that "something" is related to changing something in Umbraco -- I assume you mean, save a stylesheet, a template, edit a document... can you be more precise? Is this reproductible or it happens "sometime"?

Also, can you make sure log4net is configured in "debug" mode and attach a complete log file to the issue?


Sarah Green 20 Aug 2013, 16:26:55

"so the site is running correctly, then something happens, and you start to get that exception on every request. Correct?" Yes - in my case the "something" is either Saving a change to a Template or an XSLT file. I don't think I've seen it happen with content publishing/saving or a stylesheet and I'm not using the MVC stuff. Sadly I can't reproduce it but it feels like I do a number of changes which may well be bugged and when I'm testing and saving and repeating eventually Umbraco throws its hands in the air and does a wobbly :)

I'll do the log4net debug on one of the systems but not the live one!


Sarah Green 21 Aug 2013, 13:43:03

OK I have a repeatable scenario but its not exactly the same as the original error recorded here ... (I'm not actually getting any error at all now - the debug file just stops when the 503 error kicks in) but I believe it is the same thing (tho' feel free to re-direct me elsewhere if you think not).

The situation is that I have a single page ("services") which I suspect has a buggy bit of XSLT in its macro (same macro is used by other pages but suspect the conditions of this particular page are causing a problem tho' can't see why atm. If I unpublish the page it all works fine. If I publish it then the 503 situation kicks in as soon as the page is viewed on the site (backend viewing causes no problems).

I've attached the trace file - last crash came after line 21245. Hope it helps!


Stephan 21 Aug 2013, 16:14:46

When the page is viewed, does it render correctly or does it cause an error? And the next page you try to view, you get the 500 error (resolution is not frozen...). Right?

What's strange is that there is no resolution-related exception in the log file you uploaded?


Sarah Green 21 Aug 2013, 16:25:19

Page never gets loaded - 503 cuts in before it gets there ... and I suspect that's why the log doesn't get written too. ... I didn't get the 500 error this time - just restarted the App Pool and unpublished the bad page asap.


Stephan 21 Aug 2013, 16:29:45

See my question on U4-2376: when you mention "503" do you actually mean the IIS 503 error (IIS screen) and not an ASP.NET 500 (YSOD) error?


Sarah Green 21 Aug 2013, 16:50:34

See my answer on U4-2376 ;) I mean an "HTTP Error 503 - Service Unavailable" - host support tells me I crashed the App Pool.


Sarah Green 22 Aug 2013, 11:42:19

Had this from host supplier tho' not sure it shows much

Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7a5f8 Faulting module name: nlssorting.dll, version: 4.0.30319.17929, time stamp: 0x4ffa55e0 Exception code: 0xc00000fd Fault offset: 0x00001cda Faulting process id: 0xdd4 Faulting application start time: 0x01ce9e6ee334f605 Faulting application path: C:\Windows\SysWOW64\inetsrv\w3wp.exe Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\nlssorting.dll Report Id: 2381d903-0a62-11e3-ba4c-000c299a3ed2


Sarah Green 22 Aug 2013, 12:01:10

looks like a stack overflow problem to me - debug file shows repeated "Umbraco application starting" entries within 10ths of a second just before the crash so looks to me like its repeatedly trying to re-start itself for some reason.


Sebastiaan Janssen 22 Aug 2013, 12:04:07

Hi Sarah, it would be super useful if you could get a hold of the crash dump as described here, is that possible? http://stackoverflow.com/a/13300623/5018


Sarah Green 22 Aug 2013, 12:58:56

I have it but its rather large (85Mb zipped) and having probs uploading it - any chance of an email address or something to send it to?


Sebastiaan Janssen 22 Aug 2013, 14:04:43

@Sarah that's too large for email, try uploading to dropbox or wetransfer? :)


Sarah Green 22 Aug 2013, 14:58:26

yup can do dropbox but need an email to share to pls


Stephan 22 Aug 2013, 15:16:17

@Sarah: sgay pilotine.com

Your mention of repeated (failed) attempt at starting Umbraco is precious. I think what happens is that something happens when Umbraco starts, that crashes the app domain. So IIS restart it again and again until it decides to go 503.

We prob. need better diagnostics code to figure out what's the original error - and maybe the crash dump could help.


Sarah Green 22 Aug 2013, 15:40:11

Many thanks :) Link is on its way to you :)


Stephan 26 Aug 2013, 12:17:18

Looking at the dump... in the end, IIS dies because of a StackOverflow exception. Unfortunately the dump references Native Image DLLs so Visual Studio can't tell me where in System.Web we are before crashing. I need System.Web.pdb for .NET v4.0.30319 32bits. Only have 64bits right now... if anyone can create it... found instructions here: http://blogs.msdn.com/b/visualstudioalm/archive/2012/12/10/creating-ngen-pdbs-for-profiling-reports.aspx

Edit: I ''have'' tried to generate the PDB on my x64 PC but Visual Studio complains it's not valid ;-(


Stephan 26 Aug 2013, 15:33:33

Notes for self: using windbg + sos to get partial symbols. Request was XsltVisualize.aspx. In a button.OnClick which in turns runs an XslCompiledTransform. From then on it runs IL compiled code, seems to invoke a Xml extension method, which turns into some unsafe reflection... until an uncaught stack overflow exception is thrown -- and these can't be caught, so w3wp dies.

Two things here

  1. Sarah, can we get a look at the XSLT? Are you doing anything special in there?
  2. Why would the crash lead to the "resolution is not frozen" exception? I can understand that it takes the app domain down, but ...


Stephan 26 Aug 2013, 15:55:06

More:

happens in <xsl:template match="ContactPage | GenericPage | HomePage | Locations | Service | SystemPage"> which seems to recurse quite a lot (is that expected). Then at one point it calls the RenderMacroContent method via the XmlExtensionFunction mechanism. The macro content is

{code} On node 1416. And then... I'm not sure what happens nor whether the method is called at all... the process dies soon after. {code} 0:026> !clrstack OS Thread Id: 0x2070 (26) Child SP IP Call Site 1c914b14 70a62b52 [DebuggerU2MCatchHandlerFrame: 1c914b14] 1c9148dc 70a62b52 [HelperMethodFrame_PROTECTOBJ: 1c9148dc] System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean) 1c914bb0 6f50371d System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[]) 1c914bd4 6f538f9d System.Reflection.RuntimeMethodInfo.Invoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo) 1c914c08 673b8e9b System.Xml.Xsl.Runtime.XmlExtensionFunction.Invoke(System.Object, System.Object[]) 1c914c3c 673b8987 System.Xml.Xsl.Runtime.XmlQueryContext.InvokeXsltLateBoundFunction(System.String, System.String, System.Collections.Generic.IList`1[]) 1c914c6c 1dab7540 DynamicClass.(System.Xml.Xsl.Runtime.XmlQueryRuntime, System.Xml.XPath.XPathNavigator) 1c914ea0 1dab7dac DynamicClass.(System.Xml.Xsl.Runtime.XmlQueryRuntime, System.Xml.XPath.XPathNavigator) 1c9150d4 1dab7dac DynamicClass.(System.Xml.Xsl.Runtime.XmlQueryRuntime, System.Xml.XPath.XPathNavigator) {code}


Sarah Green 26 Aug 2013, 19:25:08

XSLT files are in the Dropbox folder ... I would expect the call to <xsl:template match="ContactPage | GenericPage | HomePage | Locations | Service | SystemPage"> to be repeated 2-3 times (obviously depends on content - node 1416 would be the first occurrence which should be called from <xsl:template match="Services">) but not more than that ... (and it shouldn't be a recursive loop - just a loop from Services to Service) ... Having said that I did suspect that there was some buggy code in here ... just didn't expect it to throw 503 errors!


Sarah Green 27 Aug 2013, 08:13:13

I'm now convinced that this is an infinite recursion problem and so probably isn't an Umbraco issue (tho' I guess it would be nice if it timed out rather than crashed the app. pool). The only thing I'm still somewhat confused about tho' is that although the example and crash data we've examined here occurs when the page is rendered, the earlier examples occurred in other situations where this was not the case (e.g. on re-starting Umbraco and when saving files). I'm guessing Umbraco is periodically doing some sort of validity checking on these occasions and running the XSLT files as part of this process.


Stephan 27 Aug 2013, 11:15:05

About recursive calls in the template: actually, I can't see what IL code is executed, so maybe it's not recursive calls at all but the different steps within the template.

About your XSLT: using library:RenderMacroContent is, I think, not efficient at all -- I understand what you're trying to do, but I think it can be done with included XSLTs much more efficiently.

About the error occurence: it can occur whenever the XSLT runs. That is, when the page is rendered, of course, but also when the XSLT is saved -- because then it is sort-of rendered, to check that it is correct & valid.

Refactoring the XSLT with includes instead of nested macro calls should (should...) fix your issue.

That being said I still don't understand

  • what causes the stack overflow...
  • why would that leave Umbraco in an unstable "resolution is not frozen" state

Very little time today, more later this week.


Sarah Green 27 Aug 2013, 16:12:43

Good point re the includes but not really part of the problem (at least I should hope not!)


Daniel Portella 26 Nov 2013, 14:14:33

I am getting this same issue on 6.1.3 what was the resolution?

As an example of my stacktrace:

In this example the request made was : /umbraco/webservices/legacyAjaxCalls.asmx/GetSecondsBeforeUserLogout

But the error seems to happen on randomly on any request be it content or backoffice urls.

Exception information: Exception type: InvalidOperationException Exception message: Resolution is not frozen, it is not yet possible to get values from it. at Umbraco.Core.ObjectResolution.SingleObjectResolverBase`2.get_Value() at Umbraco.Web.UmbracoContext.EnsureContext(HttpContextBase httpContext, ApplicationContext applicationContext, Boolean replaceContext) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)


Daniel Portella 26 Nov 2013, 14:44:48

I can confirm as Sarah touching the web config fix the issue for a period of time.


Shannon Deminick 26 Nov 2013, 23:13:53

@Stephen, you know the fix we found in v7 for this error - do you think it's the same issue randomly with 6.x ?


Sarah Green 26 Nov 2013, 23:53:53

If I remember rightly the "fix" for me was to rename the "faulty" templates or macros then reboot. Then go back in and recreate the templates and cut & paste the code back into them.


Shannon Deminick 27 Nov 2013, 01:50:42

we found this issue cropping up in v7 due to a race condition, need to check if that same condition exists in 6.x, will wait for Stephen to reply.


Stephan 27 Nov 2013, 08:10:01

@Shannon: don't know ;-( Will look into it deeper later, no time this week.


Daniel Portella 28 Nov 2013, 12:14:51

@shannon can you provide any details or ticket url for this race condition?


Daniel Portella 28 Nov 2013, 12:18:06

Just providing more information, since there is a lot of thread locking and "thread safe" code around the resolvers part of the product we notice this issue getting worse and worse when we have more users making changes to content on the backoffice (concurrently).

We experience other errors random stuff and the resolution is frozen error which kills the app pool kicking all the users out of the backoffice (lock screen appears).


Stephan 28 Nov 2013, 13:30:42

@Daniel: the point of the "thread safe" code is precisely to detect such crazy situation where Umbraco is running yet not initialized. Prior to v6, when it happened, it led to crazy debugging situations, so now at least we know something's wrong.

I have fixed stuff with commit cdd1a0a4cb77969abab94140282c236811922c52 on oct 2nd, and I think Shannon was happy with it. It is in 7, and in 6.2 so not in 6.1 yet. Maybe we should backport it to 6.1.x?


Stephan 28 Nov 2013, 13:31:02

Oh and.... has this exact bug been actually reproduced on 7?


Daniel Portella 28 Nov 2013, 15:29:26

@Stephan I didnt mean to offend with the quotes is emphasizing the thread safety around it which is very good. Indeed I had a look around it will be good to see your commit and see what changes you have made. It may be good to back port to 6.1 so users getting that version dont get this issue. About 7 version I am not sure just going from what shannon and some others have said.


Stephan 28 Nov 2013, 15:36:16

No worry, wasn't offended, sorry if I sounded like I was ;-)

So if anybody reading this thread and having the issue with 7 can report? Otherwise I'll backport it to 6.1 tomorrow so it's in the nightlies.


Sebastiaan Janssen 28 Nov 2013, 18:38:50

We're not planning any new 6.1.x releases currently, the next one will be 6.2.0. I would encourage you to try out the fix in the following way: I've cherrypicked only this commit (cdd1a0a4cb77969abab94140282c236811922c52) into the release version of 6.1.6 and built it. The attached Umbraco.Core.dll is therefore exactly the same as the one in 6.1.6, except with this fix applied. Would love to hear if this solves the issue definitively.


Shannon Deminick 28 Nov 2013, 21:35:43

The v7 issue was pre v7 launch. It was the same message: "Resolution is not frozen, it is not yet possible to get values from it." however it would occur with various stack traces. The fix Stephen made prior to releasing v7 has worked and I've never seen it since. I think the reason i saw it in v7 and not in v6 is because of the inherent async nature of webapi calls and when loading the backoffice a few of these calls are all made at once which probably lead to the race condition easier.


Daniel Portella 29 Nov 2013, 11:12:46

@Sebastiaan hehe I am using 6.1.3 but I will do the same you did and rebuild 6.1.3.

I will let you know if what ever happens it may be some time need to get those concurrent users changing stuff again!


Daniel Portella 29 Nov 2013, 11:32:57

@Sebastiaan I did the same now for 6.1.3 we will test this now and report.


Jon Dunfee 13 Jan 2014, 07:54:57

I'm almost sure to get this error anytime I mess with Lucene configuration. I removed and added three custom Lucene indices and it's spitting this error. I've encountered it before and pretty much just sit tight for a few minutes for Lucene to get some nodes processed and then it'll allow operations to continue.


Stefan Kip 02 Feb 2014, 15:22:48

I've seen this issue happening in one of our v6.1.6 websites:

[InvalidOperationException: Resolution is not frozen, it is not yet possible to get values from it.] Umbraco.Core.ObjectResolution.SingleObjectResolverBase`2.get_Value():13 Umbraco.Web.UmbracoContext.EnsureContext(HttpContextBase httpContext, ApplicationContext applicationContext, Boolean replaceContext):54 System.Web.HttpApplication+SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute():93 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously):21


Stefan Kip 04 Feb 2014, 10:04:47

And another one in some other v6.1.6 website:

[InvalidOperationException: Resolution is not frozen, it is not yet possible to get values from it.] Umbraco.Core.ObjectResolution.SingleObjectResolverBase2.get_Value() in d:\temp\UmbracoV7Branch\src\Umbraco.Core\ObjectResolution\SingleObjectResolverBase.cs:109 Umbraco.Web.Routing.DomainHelper.DomainForNode(Int32 nodeId, Uri current):37 Umbraco.Web.Routing.DefaultUrlProvider.GetUrl(UmbracoContext umbracoContext, Int32 id, Uri current, UrlProviderMode mode):165 Umbraco.Web.Routing.UrlProvider+<>c__DisplayClass3.<GetUrl>b__0(IUrlProvider provider):0 System.Linq.Enumerable+WhereSelectArrayIterator2.MoveNext():78 System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable1 source, Func2 predicate):57 Umbraco.Web.Routing.UrlProvider.GetUrl(Int32 id, Uri current, UrlProviderMode mode):92 InfoCaster.Umbraco.Helpers.UrlHelper.GetUrl(Node node, Boolean forceFullUrl, Boolean forceRelativeUrl, Boolean ignoreUmbracoUrlAlias) in c:\XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:28 InfoCaster.XXXXXXXXXXXXXXXXXX.Masterpages.Boulevard.OnLoad(EventArgs e) in c:\XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX System.Web.UI.Control.LoadRecursive():46 System.Web.UI.Control.LoadRecursive():104 System.Web.UI.Control.LoadRecursive():104 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint):1219


Shannon Deminick 09 Feb 2014, 22:39:38

It is probably the same issue we were seeing with v7 prelaunch, we need to ensure that the fixes are backported to 6.2.


Shannon Deminick 17 Feb 2014, 04:51:04

From what I can see this will already be fixed in 6.2, Stephen made the change for 7.x in the 6.2 branch and then it was merged upwards, see rev: cdd1a0a4cb77969abab94140282c236811922c52

@Stephen can you confirm?


Stephan 17 Feb 2014, 07:34:38

Looking at it today and reporting.


Shannon Deminick 06 Mar 2014, 01:31:24

Stephen, can you mark this as fixed if it is complete?


Priority: Normal

Type: Bug

State: Fixed

Assignee:

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 6.1.0, 7.0.0, 6.1.3

Due in version: 7.1.0, 6.2.0

Sprint:

Story Points:

Cycle: