@thornsen , i had a quick look ,

            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);
        }

I noticed that the unlocked index is not been added back, this line is missing .. _examineManager.AddIndex(index); Now i didnt test it .. it was just a quick observation Maybe also add some logging to see if it is unlocking. The ironic thing the examine index is locked at the moment . ;) hence the error when you try to look at indexes in backoffice . If get more time , i will see if i can load your solution

edit: Exception of type 'Lucene.Net.Index.MergePolicy+MergeException' was thrown. , not sure about this , only suggestion here is to delete the search index in app-data/ , maybe its become corrupt because of lack of the rebuild ..so not sure if that is fall out from the other issues . Also we rebuild the external index in composer . I noticed the error relates to that too external index . so that may stop it getting corrupt . but i need to test that on your solution.

Andy

@Thomsen : after a bit of editing i believe it now works :

Forcing index "InternalIndex" to be unlocked since it was left in a locked state
Forcing index "ExternalIndex" to be unlocked since it was left in a locked state
Forcing index "MembersIndex" to be unlocked since it was left in a locked state

I couldnt connect to db in the zip do you have its connection string ? to test further .. i connect to my testdb and but it looks like it works .

Andy

Hi Andy

Thank you for digging into it (once again). We would be happy to see what you have done so far!

You should be able to import the DB from .bak file into your local SQL server and then use the connection string here, to accecs it:

<connectionStrings>
  <remove name="umbracoDbDSN" />
  <add name="umbracoDbDSN" connectionString="Data 
  Source=localhost;Initial Catalog=ExamineTestErrorsDB;Integrated 
  Security=True" providerName="System.Data.SqlClient" />
 </connectionStrings>

Your first post: I am not re-adding the index because it resulted in an error. I think we in a previous thread concluded that you only nee to add the indexer again, if you are using a custom indexer:

_examineManager.AddIndex(index); 

Hi Thomsen , Ok , i use azure db so that is what thrown me dont use sql compact or express , but got connected to local db , and your backup . so all connected and working quite well ( that i can see in logs ) . I see it is unlocking the indexes and i dont see any serious errors in logs . So had to make some changes : Main ones are in the components folder:

First the component - renamed the class : And removed any code not required .

using Examine;
using Examine.LuceneEngine.Directories;
using Examine.LuceneEngine.Providers;
using Lucene.Net.Index;
using Umbraco.Core.Composing;
using Umbraco.Examine;
using Umbraco.Web.Search;

namespace ExamineErrors.Components
{
    public class ExamineComponent : IComponent
    {
         private readonly IUmbracoIndexesCreator _indexCreator;

         public ExamineComponent(IUmbracoIndexesCreator indexCreator)
         {
              _indexCreator = indexCreator;
         }

        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);
                     }
                 }
            }
        }
    public void Terminate()
    {
    }
}

}

In the Examine Composer So i can add some logging too :

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

namespace Examineerrors.Components
{
[RuntimeLevel(MinLevel = RuntimeLevel.Run)]
public class ExamineComposer : IUserComposer
{
    public void Compose(Composition composition)
    {
        composition.Register(factory => new 
        PublishedSnapshotServiceOptions
        {
            IgnoreLocalDb = true
        });
        composition.Components().Append<ExamineComponent>();
    }
}

}

In webconfig : in app settings :

<add key="Umbraco.Core.LocalTempStorage" value="EnvironmentTemp" />
<add key="Umbraco.Examine.LuceneDirectoryFactory" value="Examine.LuceneEngine.Directories.TempEnvDirectoryFactory, Examine" />
<add key="Umbraco.Core.MainDom.Lock" value="SqlMainDomLock" />

Not sure if you need the sqlMaindomlock ( as i think it more azure db) . also in Prod you might need to change this : Examine.LuceneEngine.Directories.TempEnvDirectoryFactory change to Examine.LuceneEngine.Directories.SyncTempEnvDirectoryFactory

Hope that works for you . Andy

ps : if the unlock was required you will see this in the logs :

Forcing index "ExternalIndex" to be unlocked since it was left in a locked state

Hi Andy

Thank you very much. I have implemented all of your suggestions at the live demo site and on another one of mine causing the same problems. I have uploaded the changes at about 1.00 PM and the Examine Management tab is "still alive" ...

Let's give it a few hours and see how it works out.

Best regards.

Hi again

Just checked the log this morning after the demo site has been running with the corrections over night, and it shows there is a lot of these errors since yesterday:

Also the Examine Management tab has been corrupted with errors:

Thomsen , have you tried to delete the indexes in appdata/ temp/examineindexes/after the other code change, just to see if they were already corrupt to allow it to create new indexes .
Also once the setting / indexers is back after a restart , try the rebuild in the settings

Some more on this here : https://our.umbraco.com/forum/ourumb-dev-forum/bugs/16066-Missing-LuceneNet-assembly I assume your not low on space on DB ( just a thought)

Hi again and thanks for your help, Andy. We have tried deleting all the temp and cache folders and files, stopping and recycling the IIS and rebuilding the indexes over again. It works for a while, and then the error rain and AppDomain terminating starts over again.

For now our only solution is to split our v8 sites up into separate Umbraco installations until this get solved, since it is too critical.

We have raised an issue here, referencing this thread: https://github.com/umbraco/Umbraco-CMS/issues/8740

Thanks

is working on a reply...