U4-3949 - 7.0.1 upgrade, backend not working: Failed to retreive update status

Created by Fabian 30 Dec 2013, 15:49:58 Updated by Fabian 31 Dec 2013, 11:34:42

Hi, after upgrading from umbraco 7.0.0 to 7.0.1 with Nuget, I can login to the backend, although the application tree won't be loaded. I receive the error message: "Failed to retreive update status"

The trace exception is:

2013-12-30 16:39:30,842 [55] ERROR Umbraco.Core.UmbracoApplicationBase - [Thread 47] An unhandled exception occurred System.Runtime.Serialization.SerializationException: Type is not resolved for member 'Umbraco.Core.Security.UmbracoBackOfficeIdentity,Umbraco.Core, Version=1.0.5095.27251, Culture=neutral, PublicKeyToken=null'. bei System.Web.Http.WebHost.HttpControllerHandler.EndProcessRequest(IAsyncResult result) bei System.Web.Http.WebHost.HttpControllerHandler.System.Web.IHttpAsyncHandler.EndProcessRequest(IAsyncResult result) bei System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() bei System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Frontend works like a charm.

Does anybody has an idea, how to fix this issue?

1 Attachments

Comments

Sebastiaan Janssen 30 Dec 2013, 15:59:28

We have not built any supported upgradable NuGet packages so far so you're likely to run into some issues that are not covered in NuGet. To complete the upgrade you might want to follow the upgrade instructions and clear your browser cache and cookies thoroughly (we're working on making that obsolete). Mind you, expecially Chrome caches very aggressively, so we recommend using installing a "clear cache" extension for that.

Upgrades: http://our.umbraco.org/documentation/Installation/Upgrading/general


Sebastiaan Janssen 30 Dec 2013, 16:31:52

Note: I see that our documentation says you can just do Update-Package, will clarify that soon.


Fabian 30 Dec 2013, 18:20:46

Thanks for your answer. I tried the "clear cache" extension in chrome, as well as using IE and firefox. I now tried a clean installation with version 7.0.1 using the already existing database. The problem still remains. Therefore it must have something to do with the database schema/information and not with the fact, that i used NuGet to upgrade the installation.

This exception is thrown, while loading the backend page:

GET http://localhost:55529/umbraco/Api/UpdateCheck/GetCheck 500 (Internal Server Error) (trace posted above)

I've just seen, I also receive this error while loading the backend login page. (seem like http://issues.umbraco.org/issue/U4-3907 )

GET http://localhost:55529/umbraco/UmbracoApi/Authentication/IsAuthenticated 400 (Bad Request)

I deleted any cookie as well as I've used other clients and browsers. still not working.

Any ideas?


Fabian 30 Dec 2013, 18:52:03

[SerializationException: Type is not resolved for member 'Umbraco.Core.Security.UmbracoBackOfficeIdentity,Umbraco.Core, Version=1.0.5095.27251, Culture=neutral, PublicKeyToken=null'.] Microsoft.VisualStudio.WebHost.Connection.get_RemoteIP() +0 Microsoft.VisualStudio.WebHost.Request.GetRemoteAddress() +68 System.Web.HttpWorkerRequest.IsLocal() +16 System.Web.HttpRequestWrapper.get_IsLocal() +19 System.Web.WebPages.WebPageBase.ExecutePageHierarchy() +54 System.Web.Mvc.WebViewPage.ExecutePageHierarchy() +119 System.Web.WebPages.WebPageBase.ExecutePageHierarchy(WebPageContext pageContext, TextWriter writer, WebPageRenderingBase startPage) +76 System.Web.Mvc.RazorView.RenderView(ViewContext viewContext, TextWriter writer, Object instance) +743 System.Web.Mvc.BuildManagerCompiledView.Render(ViewContext viewContext, TextWriter writer) +380 Umbraco.Core.Profiling.ProfilingView.Render(ViewContext viewContext, TextWriter writer) +151 System.Web.Mvc.ViewResultBase.ExecuteResult(ControllerContext context) +431 System.Web.Mvc.ControllerActionInvoker.InvokeActionResult(ControllerContext controllerContext, ActionResult actionResult) +39 System.Web.Mvc.<>c__DisplayClass1a.b__17() +74 System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilter(IResultFilter filter, ResultExecutingContext preContext, Func1 continuation) +388 System.Web.Mvc.<>c__DisplayClass1c.<InvokeActionResultWithFilters>b__19() +72 System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilter(IResultFilter filter, ResultExecutingContext preContext, Func1 continuation) +388 System.Web.Mvc.<>c__DisplayClass1c.b__19() +72 System.Web.Mvc.ControllerActionInvoker.InvokeActionResultWithFilters(ControllerContext controllerContext, IList1 filters, ActionResult actionResult) +303 System.Web.Mvc.Async.<>c__DisplayClass2a.<BeginInvokeAction>b__20() +155 System.Web.Mvc.Async.<>c__DisplayClass25.<BeginInvokeAction>b__22(IAsyncResult asyncResult) +184 System.Web.Mvc.Async.WrappedAsyncResult1.End() +136 System.Web.Mvc.Async.AsyncResultWrapper.End(IAsyncResult asyncResult, Object tag) +56 System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeAction(IAsyncResult asyncResult) +40 System.Web.Mvc.<>c__DisplayClass1d.b__18(IAsyncResult asyncResult) +40 System.Web.Mvc.Async.<>c__DisplayClass4.b__3(IAsyncResult ar) +47 System.Web.Mvc.Async.WrappedAsyncResult1.End() +151 System.Web.Mvc.Async.AsyncResultWrapper.End(IAsyncResult asyncResult, Object tag) +59 System.Web.Mvc.Async.AsyncResultWrapper.End(IAsyncResult asyncResult, Object tag) +40 System.Web.Mvc.Controller.EndExecuteCore(IAsyncResult asyncResult) +44 System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +47 System.Web.Mvc.Async.WrappedAsyncResult1.End() +151 System.Web.Mvc.Async.AsyncResultWrapper.End(IAsyncResult asyncResult, Object tag) +59 System.Web.Mvc.Async.AsyncResultWrapper.End(IAsyncResult asyncResult, Object tag) +40 System.Web.Mvc.Controller.EndExecute(IAsyncResult asyncResult) +39 System.Web.Mvc.Controller.System.Web.Mvc.Async.IAsyncController.EndExecute(IAsyncResult asyncResult) +39 System.Web.Mvc.<>c__DisplayClass8.b__3(IAsyncResult asyncResult) +45 System.Web.Mvc.Async.<>c__DisplayClass4.b__3(IAsyncResult ar) +47 System.Web.Mvc.Async.WrappedAsyncResult`1.End() +151 System.Web.Mvc.Async.AsyncResultWrapper.End(IAsyncResult asyncResult, Object tag) +59 System.Web.Mvc.Async.AsyncResultWrapper.End(IAsyncResult asyncResult, Object tag) +40 System.Web.Mvc.MvcHandler.EndProcessRequest(IAsyncResult asyncResult) +40 System.Web.Mvc.MvcHandler.System.Web.IHttpAsyncHandler.EndProcessRequest(IAsyncResult result) +38 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +9514812 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155


Fabian 30 Dec 2013, 20:02:16

Problem solved. Using IIS express instead of Visual studio development server did the trick.


Sebastiaan Janssen 30 Dec 2013, 20:55:12

Ah yes. Never use Cassini, it's old, obsolete and plain evil. ;-)


Fabian 31 Dec 2013, 11:34:42

yes, just noticed :)


Priority: Normal

Type: Bug

State: Fixed

Assignee:

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions:

Due in version:

Sprint:

Story Points:

Cycle: