SourceOne: Email Management ExAsElasticIdxObj thread fails to start

Summary: ExAsElasticIdxObj thread fails to start, and indexing stops the process with the error message "Got Write Lock - But Another Process Owns it."

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

ExAsElasticIdxObj threads are not running on any of the SourceOne Index servers.

The following warnings are seen in the ExAsIndex logs:

  • WARNING|Got Write Lock - But Another Process Owns it - [\\servername\DropDir\DropDir.lock] - OLD LOCK('Version  : 1.0  Machine  : <Hostname>  MAC Addr :<MAC add value>  Module   : ExAsIndex.exe  PID      : 10592  TID      : 9536  Acquired : 2019-07-29T12:48:28.015  Updated  : 2019-07-30T11:57:40.208  ') - THIS(Version  : 1.0  Machine  : <Hostname>  MAC Addr : :<MAC add value>    Module   : ExAsIndex.exe  PID      : 10592  TID      : 9536  Acquired : 2019-07-29T12:48:28.015  Updated  : 2019-07-30T11:57:40.208  )|ExAsLockFile.cpp(634)
  • WARNING|Skipping  \\servername \DropDir unable to claim dropdir lock.  Error: 0x800300a7|ExAsIdxComp.cpp(2563)

Cause

Index process was unable to claim the Drop Dir Lock. None of the Index servers were using the Lock file.

Resolution

In order to address the issue, perform the steps below:

  1. Stop SourceOne Indexer Services on all the Index servers.
  2. Delete or Move Drop Dir lock file from the index location.
  3. Start the SourceOne Indexer Services.

A new lock file is created and after that, ExAsElasticIdxObj threads start to be generated.

Affected Products

SourceOne Email Management

Products

SourceOne, SourceOne Email Management
Article Properties
Article Number: 000053666
Article Type: Solution
Last Modified: 01 يونيو 2026
Version:  5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.