StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PONullReferenceException when browsing Sitecore Content Tree
text
Body
copied!<p>We have a Sitecore 6.4 installation (Sitecore.NET 6.4.1 (rev. 110621)), deployed to two servers in a load balanced environment. For one (and only one) of the servers, when you are browsing the content tree in the content editor you receive a stack trace as below. It doesn't always error, but once you do see the error it always happens. </p> <pre><code>[NullReferenceException: Object reference not set to an instance of an object.] Sitecore.Shell.Applications.ContentManager.ContentEditorForm.OnLoad(EventArgs e) +1636 [TargetInvocationException: Exception has been thrown by the target of an invocation.] System.RuntimeMethodHandle._InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, SignatureStruct&amp; sig, MethodAttributes methodAttributes, RuntimeType typeOwner) +0 System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks) +639 System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) +38 System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters) +35 Sitecore.Reflection.ReflectionUtil.CallMethod(Type type, Object obj, String methodName, Boolean includeNonPublic, Boolean includeInherited, Object[] parameters) +37 Sitecore.Reflection.ReflectionUtil.CallMethod(Object obj, String methodName, Boolean includeNonPublic, Boolean includeInherited, Object[] parameters) +66 Sitecore.Web.UI.Sheer.ClientPage.OnLoad(EventArgs e) +420 System.Web.UI.Control.LoadRecursive() +71 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3064 </code></pre>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload