We are on merchello 1.8.0 and umbraco 7.2.4, and are having periodic issues where the Umbraco dashboard suddenly returns a white/blank page, no matter what page we request. Once this issue occurs, we continue to receive a blank page for any dashboard request (user-facing site doesn't have any issues) until we touch the web.config to reset the app. Then the dashboard works fine for a while, and will suddenly stop working. I looked at the Umbraco logs and found the exception stack trace below (one occurrence for each dashboard request):
System.ArgumentException: An item with the same key has already been added. at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource) at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value) at Merchello.Web.Trees.ServerVariablesParsingEvents.ServerVariablesParserParsing(Object sender, Dictionary`2 items) at Umbraco.Web.UI.JavaScript.ServerVariablesParser.Parse(Dictionary`2 items) at Umbraco.Web.Editors.BackOfficeController.ServerVariables() at lambda_method(Closure , ControllerBase , Object[] ) at System.Web.Mvc.ActionMethodDispatcher.Execute(ControllerBase controller, Object[] parameters) at System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters) at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters) at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass42.<BeginInvokeSynchronousActionMethod>b__41() at System.Web.Mvc.Async.AsyncResultWrapper.<>c__DisplayClass8`1.<BeginSynchronous>b__7(IAsyncResult _) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End() at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethod(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass37.<>c__DisplayClass39.<BeginInvokeActionMethodWithFilters>b__33() at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49() at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49() at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49() at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass37.<BeginInvokeActionMethodWithFilters>b__36(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End() at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethodWithFilters(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass25.<>c__DisplayClass2a.<BeginInvokeAction>b__20() at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass25.<BeginInvokeAction>b__22(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End() at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeAction(IAsyncResult asyncResult) at System.Web.Mvc.Controller.<>c__DisplayClass1d.<BeginExecuteCore>b__18(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncResultWrapper.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End() at System.Web.Mvc.Controller.EndExecuteCore(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncResultWrapper.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End() at System.Web.Mvc.Controller.EndExecute(IAsyncResult asyncResult) at System.Web.Mvc.Controller.System.Web.Mvc.Async.IAsyncController.EndExecute(IAsyncResult asyncResult) at System.Web.Mvc.MvcHandler.<>c__DisplayClass8.<BeginProcessRequest>b__3(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncResultWrapper.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End() at System.Web.Mvc.MvcHandler.EndProcessRequest(IAsyncResult asyncResult) at System.Web.Mvc.MvcHandler.System.Web.IHttpAsyncHandler.EndProcessRequest(IAsyncResult result) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
It's entirely possible that one of our upgrades was not completed correctly, but does anyone have any ideas as to what we can check?
I'm having a tough time reproducing this on my end. In fact I've not seen it. What other plugins to you have installed - perhaps we have a conflict with another package?
In 1.9.0, I've moved all of these to a merchelloUrls dictionary instead of adding them directly to the umbracoUrls dictionary.
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.ArgumentException: An item with the same key has already been added.
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.
I was able to get a duplicate key issue based on the language files. I'm writing a bit of test code now to provide assertions that I do not have any duplicates there. This did create a login issue for me on upgrading. I'm not convinced this is the issue you guys are seeing since I don't know why it would affect the ServerVariables parsing but I have not followed that too far into the Umbraco core.
In Umbraco 7.3.0 we will be able to keep our language files separate from Umbraco in the App_Plugins folder so it will make things easier to manage.
If I find a duplicate key, I'll post it here with instructions as to how to fix.
I did find a couple duplicate areas in the language files.
area alias="merchelloShipping"
area alias="merchGatewayProviders"
and quite a few keys missing from languages other than en.xml.
I have posted the updated (cleaned up versions) of the language files to the hot fixes area. To get things squared away, go to /Umbraco/Config/Lang and find the language file (en.xml) or whatever you are using. Remove every section that is prefixed with merchello. These will probably be at the end of the file.
Then copy all of the areas from the cleaned version of the file with the same name.
It would be great if you would try loading the back office before you copied the merchello values back into the language file to see if this error resolves itself. The merchello section will look really ugly until you copy the keys into the respective Umbraco file, but we would know if this solves the other conflict as well.
@Keith Sorry to come in on this issue but I noticed you are running merchello 1.8.0 and you have installed Merchello.Stripe package. We were about to install Merchello.Stripe package but weren't sure whether it was compatible with Merchello 1.8.0 but have you found it works or have you been unable to test it at this point?
Greatly appreciate if you could let me know and apologies again for interupting this ticket but wasn't sure how else to contact you!
@James I was able to install the stripe package without issue, however I know Alex (the owner of the Stripe plugin) was going to be working on getting it updated to ensure compatibility with the newest versions of Merchello. I did have to add in my own fix to the script, so that the API Key would save correctly, and I believe they were set to merge that in (see my commit @ https://github.com/tigreye007/Merchello/commit/9d890de8edb5f32fa17480f86b2b2f1b637b3688)
@Rusty The new language files didn't help. I am still getting the error, and I found a way to reproduce it in my current project.
Environment
Azure website
Web.config Debug = false (may be important, as that's the primary difference between my local dev and the server this is occurring on)
Browser doesn't seem to matter
Log into umbraco dashboard
Clear cache
Shift-Refresh
This set of actions recreates the issue every time for me. Every attempt to load any dashboard page results in this entry in the log (I believe it's the same as I originally posted), and can only be temporarily "fixed" by touching the web.config. If I have time, I will try to reproduce it in my local dev environment.
2015-04-09 19:32:52,506 [13] ERROR Umbraco.Core.UmbracoApplicationBase - [Thread 55] An unhandled exception occurred System.ArgumentException: An item with the same key has already been added. at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource) at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value) at Merchello.Web.Trees.ServerVariablesParsingEvents.ServerVariablesParserParsing(Object sender, Dictionary`2 items) at Umbraco.Web.UI.JavaScript.ServerVariablesParser.Parse(Dictionary`2 items) at Umbraco.Web.Editors.BackOfficeController.ServerVariables() at lambda_method(Closure , ControllerBase , Object[] ) at System.Web.Mvc.ActionMethodDispatcher.Execute(ControllerBase controller, Object[] parameters) at System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters) at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters) at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass42.<BeginInvokeSynchronousActionMethod>b__41() at System.Web.Mvc.Async.AsyncResultWrapper.<>c__DisplayClass8`1.<BeginSynchronous>b__7(IAsyncResult _) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End() at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethod(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass37.<>c__DisplayClass39.<BeginInvokeActionMethodWithFilters>b__33() at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49() at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49() at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49() at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass37.<BeginInvokeActionMethodWithFilters>b__36(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End() at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethodWithFilters(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass25.<>c__DisplayClass2a.<BeginInvokeAction>b__20() at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass25.<BeginInvokeAction>b__22(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End() at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeAction(IAsyncResult asyncResult) at System.Web.Mvc.Controller.<>c__DisplayClass1d.<BeginExecuteCore>b__18(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncResultWrapper.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End() at System.Web.Mvc.Controller.EndExecuteCore(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncResultWrapper.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End() at System.Web.Mvc.Controller.EndExecute(IAsyncResult asyncResult) at System.Web.Mvc.Controller.System.Web.Mvc.Async.IAsyncController.EndExecute(IAsyncResult asyncResult) at System.Web.Mvc.MvcHandler.<>c__DisplayClass8.<BeginProcessRequest>b__3(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncResultWrapper.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End() at System.Web.Mvc.MvcHandler.EndProcessRequest(IAsyncResult asyncResult) at System.Web.Mvc.MvcHandler.System.Web.IHttpAsyncHandler.EndProcessRequest(IAsyncResult result) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Shannon you are right. I managed to replicate this locally by setting the debug="false".
Recycling the app pool, seems to be the only ways to get the backoffice to work again. I might leave it to run in debug mode for now, as this is my own test CMS.
Didn't know it was due to Merchello until I installed only Merchello to a clean install of Umbraco. I was only having the problem when publishing to live server but thanks to Chris I understand this came because in release the debug was removed from web config. So, for the time being my workaround is to add debug to the web.config.
Guys, I'm having this issue too, I always run with debug="false" so I get the issue on localhost / dev / live (transformed to remove debug completely). I performed my upgrade to 7.2.4 / merchello 1.8.1 at the same time so I can't say which of the two is causing the issue but I can say it's only started happening after the upgrade.
Just FYI this seems to be a widespread issue that has started occurring after upgrading to either 7.2.3 or 7.2.4, I can't say which for sure as I jumped straight from 7.2.2 to 7.2.4
Just had this issue... upgraded in varous steps from 6.2.0 to 7.2.4 with contour (not merchello but could be interesting enough to check) upgrade in between.... and a lot of custom contour mods sigh Turned out there were a se.xml and a sv.xml in the umbraco config lang. removed the se and it worked like a charm
I've created an issue on the tracker for this: http://issues.umbraco.org/issue/U4-6559 for 7.2.5 release, in the meantime I know some packages have been updated to fix this issue by checking for the existence of keys in the dictionary first.
"An item with the same key has already been added."
We are on merchello 1.8.0 and umbraco 7.2.4, and are having periodic issues where the Umbraco dashboard suddenly returns a white/blank page, no matter what page we request. Once this issue occurs, we continue to receive a blank page for any dashboard request (user-facing site doesn't have any issues) until we touch the web.config to reset the app. Then the dashboard works fine for a while, and will suddenly stop working. I looked at the Umbraco logs and found the exception stack trace below (one occurrence for each dashboard request):
It's entirely possible that one of our upgrades was not completed correctly, but does anyone have any ideas as to what we can check?
I am experiencing the exact same issue.
Still looking into, anybody else?
Cheers,
Josh
I'm having a tough time reproducing this on my end. In fact I've not seen it. What other plugins to you have installed - perhaps we have a conflict with another package?
In 1.9.0, I've moved all of these to a merchelloUrls dictionary instead of adding them directly to the umbracoUrls dictionary.
Hi Rusty,
Only additional package is the Bazzar MVC store.
If I was to do a pull of 1.9, are there any schema changes? If not Is it simply just a matter of pulling it, building it and replacing the binaries?
Thanks in adavance.
Josh
@Rusty We have no additional packages installed, so unfortunately that's not the issue in my case.
@Rusty I take that back. I also have the Merchello.Stripe package installed.
@Keith @Josh - I'm still trying to reproduce it. I have 7.2.4 installed and with the 1.8.1 binaries and have not seen the issue yet.
I looked at Alex's Stripe provider repo https://github.com/alindgren/MerchelloStripeProvider/tree/master/src/Merchello.Plugin.Payments.Stripe and did not see he had anything registering API controllers - so pretty sure that's not it.
When it happens again can you check the JS console for any errors before you restart the App?
Hi Rusty,
I can't seem to login now. I checked the console and there was 500. Here is the error:
It seems to be something to do with the
Merchello.Web.Trees.ServerVariablesParsingEvents.ServerVariablesParserParsing(Object sender, Dictionary`2 items) +501
Thanks,
JD
Server Error in '/' Application.
An item with the same key has already been added.
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.ArgumentException: An item with the same key has already been added.
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:
Also in the console we are getting:
No url found for api name legacyTreeJs
Josh,
Did you upgrade to 7.2.4 or is it the base install. legacyTree.js is Umbraco.
I'm still have not been able to find this on either a direct install or upgrading a previous version. Does this happen to you on new installs as well?
I was able to get a duplicate key issue based on the language files. I'm writing a bit of test code now to provide assertions that I do not have any duplicates there. This did create a login issue for me on upgrading. I'm not convinced this is the issue you guys are seeing since I don't know why it would affect the ServerVariables parsing but I have not followed that too far into the Umbraco core.
In Umbraco 7.3.0 we will be able to keep our language files separate from Umbraco in the App_Plugins folder so it will make things easier to manage.
If I find a duplicate key, I'll post it here with instructions as to how to fix.
I did find a couple duplicate areas in the language files.
area alias="merchelloShipping"
area alias="merchGatewayProviders"
and quite a few keys missing from languages other than en.xml.
I have posted the updated (cleaned up versions) of the language files to the hot fixes area. To get things squared away, go to /Umbraco/Config/Lang and find the language file (en.xml) or whatever you are using. Remove every section that is prefixed with merchello. These will probably be at the end of the file.
Then copy all of the areas from the cleaned version of the file with the same name.
It would be great if you would try loading the back office before you copied the merchello values back into the language file to see if this error resolves itself. The merchello section will look really ugly until you copy the keys into the respective Umbraco file, but we would know if this solves the other conflict as well.
Much appreciated!
@Keith Sorry to come in on this issue but I noticed you are running merchello 1.8.0 and you have installed Merchello.Stripe package. We were about to install Merchello.Stripe package but weren't sure whether it was compatible with Merchello 1.8.0 but have you found it works or have you been unable to test it at this point?
Greatly appreciate if you could let me know and apologies again for interupting this ticket but wasn't sure how else to contact you!
@James I was able to install the stripe package without issue, however I know Alex (the owner of the Stripe plugin) was going to be working on getting it updated to ensure compatibility with the newest versions of Merchello. I did have to add in my own fix to the script, so that the API Key would save correctly, and I believe they were set to merge that in (see my commit @ https://github.com/tigreye007/Merchello/commit/9d890de8edb5f32fa17480f86b2b2f1b637b3688)
@Rusty The new language files didn't help. I am still getting the error, and I found a way to reproduce it in my current project.
Environment
This set of actions recreates the issue every time for me. Every attempt to load any dashboard page results in this entry in the log (I believe it's the same as I originally posted), and can only be temporarily "fixed" by touching the web.config. If I have time, I will try to reproduce it in my local dev environment.
2015-04-09 19:32:52,506 [13] ERROR Umbraco.Core.UmbracoApplicationBase - [Thread 55] An unhandled exception occurred
System.ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
at Merchello.Web.Trees.ServerVariablesParsingEvents.ServerVariablesParserParsing(Object sender, Dictionary`2 items)
at Umbraco.Web.UI.JavaScript.ServerVariablesParser.Parse(Dictionary`2 items)
at Umbraco.Web.Editors.BackOfficeController.ServerVariables()
at lambda_method(Closure , ControllerBase , Object[] )
at System.Web.Mvc.ActionMethodDispatcher.Execute(ControllerBase controller, Object[] parameters)
at System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters)
at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass42.<BeginInvokeSynchronousActionMethod>b__41()
at System.Web.Mvc.Async.AsyncResultWrapper.<>c__DisplayClass8`1.<BeginSynchronous>b__7(IAsyncResult _)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethod(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass37.<>c__DisplayClass39.<BeginInvokeActionMethodWithFilters>b__33()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass37.<BeginInvokeActionMethodWithFilters>b__36(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethodWithFilters(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass25.<>c__DisplayClass2a.<BeginInvokeAction>b__20()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass25.<BeginInvokeAction>b__22(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeAction(IAsyncResult asyncResult)
at System.Web.Mvc.Controller.<>c__DisplayClass1d.<BeginExecuteCore>b__18(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncResultWrapper.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End()
at System.Web.Mvc.Controller.EndExecuteCore(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncResultWrapper.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End()
at System.Web.Mvc.Controller.EndExecute(IAsyncResult asyncResult)
at System.Web.Mvc.Controller.System.Web.Mvc.Async.IAsyncController.EndExecute(IAsyncResult asyncResult)
at System.Web.Mvc.MvcHandler.<>c__DisplayClass8.<BeginProcessRequest>b__3(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncResultWrapper.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End()
at System.Web.Mvc.MvcHandler.EndProcessRequest(IAsyncResult asyncResult)
at System.Web.Mvc.MvcHandler.System.Web.IHttpAsyncHandler.EndProcessRequest(IAsyncResult result)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
I was having this same issue, it appears something to do with multiple users using the same login when debug is false.
Shannon you are right. I managed to replicate this locally by setting the debug="false".
Recycling the app pool, seems to be the only ways to get the backoffice to work again. I might leave it to run in debug mode for now, as this is my own test CMS.
Shannon,
Would this have anything to do with the [UmbracoApplicationAuthorize("merchello")] attribute?
Hi,
I'm having the exact same issue.
Didn't know it was due to Merchello until I installed only Merchello to a clean install of Umbraco.
I was only having the problem when publishing to live server but thanks to Chris I understand this came because in release the debug was removed from web config.
So, for the time being my workaround is to add debug to the web.config.
Onno
Guys, I'm having this issue too, I always run with debug="false" so I get the issue on localhost / dev / live (transformed to remove debug completely). I performed my upgrade to 7.2.4 / merchello 1.8.1 at the same time so I can't say which of the two is causing the issue but I can say it's only started happening after the upgrade.
Just FYI this seems to be a widespread issue that has started occurring after upgrading to either 7.2.3 or 7.2.4, I can't say which for sure as I jumped straight from 7.2.2 to 7.2.4
https://our.umbraco.org/forum/getting-started/installing-umbraco/63500-Error-in-backoffice-after-upgrade-from-722-to-723(4)?p=0#comment216758
Is there a forthcoming patch for this?
I'm trying to track it down, but it looks like it may be an Umbraco issue.
Just had this issue... upgraded in varous steps from 6.2.0 to 7.2.4 with contour (not merchello but could be interesting enough to check) upgrade in between.... and a lot of custom contour mods sigh
Turned out there were a se.xml and a sv.xml in the umbraco config lang. removed the se and it worked like a charm
Here is the cause:
https://our.umbraco.org/forum/umbraco-7/using-umbraco-7/49453-HTTPS-and-BackOffice-logging-in#comment214323
And here is a fix that package devs should be aware of:
https://our.umbraco.org/forum/umbraco-7/using-umbraco-7/49453-HTTPS-and-BackOffice-logging-in?p=1#comment214334
I've created an issue on the tracker for this: http://issues.umbraco.org/issue/U4-6559 for 7.2.5 release, in the meantime I know some packages have been updated to fix this issue by checking for the existence of keys in the dictionary first.
Thanks Shannon. That did it, appreciate the heads up.
This is fixed in 1.8.2 for Umbraco 7.2.4.
is working on a reply...