CMS11: In use notification already exist error

November Happy Hour will be moved to Thursday December 5th.

AI OnAI Off

Home / Forums / Developers (Main Products) Forum / CMS 7.5 - 11 /

CMS11: In use notification already exist error

Magnus Eriksson

Vote:

Hi,

recently we have started to get a lot of "in use notification already exist" in our CMS11 episerver error logs. When this error occurs, our editors are unable to edit/save/publish content in episerver. We have been unable to find a solution since the error seems to be located within episerver (see error log)

We have noted that Optimizely has fixed a similar error in CMS12:

CMS-2366 – Fixed an issue where when you tried to edit the same page from multiple tabs, In use notification already exists error message displayed in one of the editors.

This problem makes it hard to work within episerver and we are wondering if there is a solution/fix/workaround for CMS11 ?

System.Web.HttpException (0x80004005): In use notification already exists.
   at EPiServer.Cms.Shell.UI.Rest.Internal.InUseNotificationStore.Post(InUseNotificationViewModel entity)
   at lambda_method(Closure , ControllerBase , Object[] )
   at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters)
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c.<BeginInvokeSynchronousActionMethod>b__9_0(IAsyncResult asyncResult, ActionInvocation innerInvokeState)
   at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`2.CallEndDelegate(IAsyncResult asyncResult)
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethod(IAsyncResult asyncResult)
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass11_0.<InvokeActionMethodFilterAsynchronouslyRecursive>b__0()
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass11_2.<InvokeActionMethodFilterAsynchronouslyRecursive>b__2()
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass11_2.<InvokeActionMethodFilterAsynchronouslyRecursive>b__2()
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethodWithFilters(IAsyncResult asyncResult)
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass3_6.<BeginInvokeAction>b__4()
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass3_1.<BeginInvokeAction>b__1(IAsyncResult asyncResult)
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeAction(IAsyncResult asyncResult)
   at EPiServer.Shell.Services.Rest.RestControllerBase.EndExecute(IAsyncResult asyncResult)
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

#322869

May 30, 2024 8:32

Eric Herlitz

Vote:

In general with these errors

Clear the cache and restart IIS.
Check the database for duplicate notification entries and clean them up.
Ensure no scheduled jobs are stuck.
Review custom code related to notifications.
Update Episerver packages to the latest versions (for CMS11).

The cache data would also include the one in the Framework folders, e.g. run this in PowerShell

net stop w3svc
Remove-Item -Path "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\*" -Force -Recurse
Remove-Item -Path "C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\*" -Force -Recurse
net start w3svc

If you want to clear the database check for duplicates first, the notification tables can be cleared without risk anyway.

#322935

May 31, 2024 10:41

Magnus Eriksson

Vote:

It looks like a defragmention of the database did the trick. Have been running now for 4 days without these errors.

#323152

Jun 05, 2024 12:08

Please login to post a reply