Examine index problems & members can not login "Lock request time out period exceeded." error
Just updated to latest 8.6 trying to fix this - but still having problem.
I think members index is damaged, and members can not log-in (did everything > (deleted member indexes on disk, cache clear, database cache clear itd...)
In admin/Settings section > Examine Index options are not avaialble - just list of options - you can not click Manage Exmamine Indexes to get details.
Sometimes error box pop-ups "Failed to retrieve indexer details"
Related to this is bigest problem - members can not log in on our site because of "Lock request time out period exceeded." and I am sure this is related to index problem.
Any idea how to fix this?
Umbraco error log has more info
{"@t":"2020-05-01T01:05:52.9557993Z","@mt":"Cannot get GetIndexDocumentCount, the writer is already closed","@l":"Warning","SourceContext":"Umbraco.Examine.UmbracoContentIndex","ProcessId":13400,"ProcessName":"w3wp","ThreadId":226,"AppDomainId":13,"AppDomainAppId":"LMW3SVC2ROOT","MachineName":"EC2AMAZ-T42FVJ3","Log4NetLevel":"WARN ","HttpRequestNumber":11,"HttpRequestId":"ebec8e9f-9f4d-49ba-a48b-6808b7938220"}
{"@t":"2020-05-01T01:05:52.9557993Z","@mt":"Cannot get GetIndexFieldCount, the writer is already closed","@l":"Warning","SourceContext":"Umbraco.Examine.UmbracoContentIndex","ProcessId":13400,"ProcessName":"w3wp","ThreadId":226,"AppDomainId":13,"AppDomainAppId":"LMW3SVC2ROOT","MachineName":"EC2AMAZ-T42FVJ3","Log4NetLevel":"WARN ","HttpRequestNumber":11,"HttpRequestId":"ebec8e9f-9f4d-49ba-a48b-6808b7938220"}
Error info about "Lock Request timeout error"
System.Data.SqlClient.SqlException (0x80131904): Lock request time out period exceeded.
The statement has been terminated.
at HZZ_mjere_2020.Controllers.MemberController.SubmitLogin(LoginModel model, String returnUrl) in C:\Repositories\kadei-mjere-2020\HZZ-mjere-2020\Controllers\MemberController.cs:line 157
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.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 System.Web.Mvc.Controller.<>c.<BeginExecuteCore>b__152_1(IAsyncResult asyncResult, ExecuteCoreState innerState)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncVoid`1.CallEndDelegate(IAsyncResult asyncResult)
at System.Web.Mvc.Controller.EndExecuteCore(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncVoid`1.CallEndDelegate(IAsyncResult asyncResult)
at System.Web.Mvc.Controller.EndExecute(IAsyncResult asyncResult)
at System.Web.Mvc.MvcHandler.<>c.<BeginProcessRequest>b__20_1(IAsyncResult asyncResult, ProcessRequestState innerState)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncVoid`1.CallEndDelegate(IAsyncResult asyncResult)
at System.Web.Mvc.MvcHandler.EndProcessRequest(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)
ClientConnectionId:9d10437b-a01e-464d-bf73-4a4b40ac1b46
Error Number:1222,State:51,Class:16
Examine index problems & members can not login "Lock request time out period exceeded." error
Just updated to latest 8.6 trying to fix this - but still having problem.
I think members index is damaged, and members can not log-in (did everything > (deleted member indexes on disk, cache clear, database cache clear itd...)
In admin/Settings section > Examine Index options are not avaialble - just list of options - you can not click Manage Exmamine Indexes to get details.
Sometimes error box pop-ups "Failed to retrieve indexer details"
Related to this is bigest problem - members can not log in on our site because of "Lock request time out period exceeded." and I am sure this is related to index problem.
Any idea how to fix this?
Umbraco error log has more info
Error info about "Lock Request timeout error"
Hi, did you find a solution for this? seeing similar issues on a 8.6 site.
Yes, we have IIS configured to use more than 1 prcess workers. Downgraded to 1 worker and with latest umbraco 8.6.x no problem anymore.
Did you solve the issue? Seeing the same issue on a 8.6 site.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.