If there is no abnormality, you can try the following solution: Maybe you can find the reason for your lock timeout. ![]() So you can use sp_who2 to check for all session that are currently established in the database and check for any with blocking, high CPU usage, high I/O usage, or any with multiple entries for the same SPID. In some cases, a query will fail with the lock request time out period error after waiting for more than 10ms. Msg 1222, Lock request time out period exceeded Please see this MS link, which describes the possible scenarios for this error. End of stack trace from previous location where exception was thrown -Īt .Throw()Īt .HandleNonSuccessAndDebuggerNotification(Task task)Īt .ApiControllerActionInvoker.d_1.MoveNext()Īt .ActionFilterAttribute.d_6.MoveNext()Īt .ActionFilterAttribute.d_5.MoveNext()Īt .Msg 50000, Level 16, State 1, Server BIDSSql, Procedure CommandExecute, Line 167 ![]() 11:49:02,112 ERROR - Unhandled controller exception occurred for request ''Īt .SqlServerSyntaxProvider.WriteLock(IDatabase db, TimeSpan timeout, Int32 lockIds) in D:\a\1\s\src\Umbraco.Core\Persistence\SqlSyntax\SqlServerSyntaxProvider.cs:line 272Īt .ContentService.Save(IContent content, Int32 userId, Boolean raiseEvents) in D:\a\1\s\src\Umbraco.Core\Services\Implement\ContentService.cs:line 782Īt .SaveAndNotify(ContentItemSave contentItem, Func`2 saveMethod, Int32 variantCount, Dictionary`2 notifications, SimpleNotificationModel globalNotifications, String invariantSavedLocalizationKey, String variantSavedLocalizationKey, String cultureForInvariantErrors, Boolean
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |