Hi,

I had the same problem and the solution was to restart de SQL server proccess.

Hi,

I've just got the same error when saving a document, here is the stack trace:

System.Data.SqlClient.SqlException: Lock request time out period exceeded. The statement has been terminated. Stacktrace at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at StackExchange.Profiling.Data.ProfiledDbCommand.ExecuteNonQuery() in C:\projects\dotnet\src\MiniProfiler.Shared\Data\ProfiledDbCommand.cs:line 272 at Umbraco.Core.Persistence.FaultHandling.FaultHandlingDbCommand.

We're running Umbraco 8.6, examine 1.0.3 in Azure.

Hi All,

I've just found this thread: https://our.umbraco.com/forum/umbraco-8/97117-execution-timeout-expired-on-rebuilding-cache

I've increased the Umbraco connection string to 90 sec and I'll keep an eye on things, hopefully it's resolved. I'll let you know if it appears again.

Hi - I solved this today by upgrading to 8.6.4, rebuilding and then update Examine via NuGet afterwards. There is a bugfix in the new version og Examine - don't know why it is not included in the new 8.6.4 version.

And then I have registered this composer also.

using Umbraco.Core.Composing;
using Umbraco.Web.PublishedCache.NuCache;

namespace MySite.Composers
{
    public class IgnoreLocalDbComposer : IUserComposer
    {
    public void Compose(Composition composition)
    {
        composition.Register(factory => new PublishedSnapshotServiceOptions
        {
            IgnoreLocalDb = true
        });
    }
}

}

Those three actions solved it for me - hope it helps.

This is fixed in 8.6.4 I believe - we migrated to 8.6 from 7.15 a while ago and have had this happen quite a lot on a busy site with lots of editors.

https://github.com/umbraco/Umbraco-CMS/pull/8398

Edit - should have read the rest of the thread first!

Do you have SqlMainDomLock set in the web.config?

When we first went to 8.6.0 we had that set on all servers; to get it working we had to have it only on our master server - we got that error about indexing a LOT and had to go back to 7.15 (we'd kept a copy of the old site of course).

On 8.6.2 we have to have that setting on all servers.

We can't install 8.6.4 for a week or so now anyway so hopefully we'll have time to work it all out before then!

No - I haven't tried that one. Should I just add this?

<add key="Umbraco.Core.MainDom.Lock" value="SqlMainDomLock" />

@Guido Adam - Thanks, I am active in the thread you are linking to, trying to solve the problem earlier this year. Andy there is really helpful. Unfortunately the solution at the bottom of the thread unlocking the index directories did not solve the error. I really hope to sort it out before my site here is going live by September the 1st. - I wish I did drop the idea of having two sites in one solution - but it really worked flawless in v.7.x :-O

@Chris Norwood - I tried updating my web.config with:

 <add key="Umbraco.Core.MainDom.Lock" value="SqlMainDomLock" />

but unfortunately it had no effect. This is is the error log since I cleaned it two hours ago:

Hi Thomsen,

Do you still have IgnoreLocalDB on using the composer?

My understanding was that this should only be used on a front-end server (i.e. not the back office server) - if your server is both a front-end and back-end server then you might not want that setting in place? (I would try removing it I think, although I'm not convinced it's an issue - at least it would eliminate one potential source).

@Chris - after removing the IgnoreLocalDB and testing I start getting random "Lock request time out period exceeded." YSOD errors again, so it seems like this composer workaround is necessary when trying to run multiple domains on the same v8 installation.

One last idea - you could try without either SqlMainDomLock or IgnoreLocalDb? (I.e. turn them both off)?

SqlMainDomLock shouldn't be needed outside Azure anyway and IgnoreLocalDb is only really meant for front end servers as I understand it (I've had a few discussions with Umbraco support about it and what configuration is needed, but they've all been in the context of an Azure app service).

thomsen , what have u set the db timeout ? i increased ours to 90 and seem to help , also on our dev box ,

<add
    key="Umbraco.Examine.LuceneDirectoryFactory"
    value="Examine.LuceneEngine.Directories.SyncTempEnvDirectoryFactory, Examine" />

, change this to TempEnvDirectory .. just a suggestion to see if that helps . it seems to work well on dev which is shared across a number of dev's

on the prod , ignore db , unlock db code is also there , didnt add the sqldomlock seem to cause more issues . v8.6.4 currently . Although not tried since upgrade to 8.6.4 . Also if u dont use sqldomlock , have you tried the change in azure config the setting for website recycling is option.

Andy

@Thomsen

public void Initialize()
    {
        DirectoryFactory.DefaultLockFactory = d =>
        {
            var simpleFsLockFactory = new NoPrefixSimpleFsLockFactory(d);
            return simpleFsLockFactory;
        };
        foreach (var index in _indexCreator.Create()) { 
            if (index is LuceneIndex)
            {
                var luceneIndex = index as LuceneIndex;
                var dir = luceneIndex.GetLuceneDirectory();
                if (IndexWriter.IsLocked(dir))
                {
                    IndexWriter.Unlock(dir);
                }
            }
        _examineManager.AddIndex(index);
        }

Thanks Andy

I have been running the quickfixes and suggestions for some days now, but this error flood and application crashes unfortunately seems to continue.

I have created a new thread with a project and a demo site showcase with as much information about the setup and the hosting environment as possible. I have provided a login to the demo site, to show the log and the Examine management tab going down. There is also a download of the project.

https://our.umbraco.com/forum/using-umbraco-and-getting-started//103281-unhandled-exception-in-appdomain-terminating-an-examine-index-and-lucene-errors-showcase

I really hope this can help describe and show the problem and help to a solution.

Thanks!

Getting the same issue on 9.3.1..

Lock request time out period exceeded. The statement has been terminated.

Undtagelsesdetaljer
System.Data.SqlClient.SqlException, System.Data.SqlClient, Version=4.6.1.3, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a: Lock request time out period exceeded. The statement has been terminated.

Restarting the SQL server worked for us

/Rune

is working on a reply...