Repeatable bug: SQLite errors when running a concordance on NABRE

When you run the concordance on NABRE, it gets about three-quarters through then returns an error: "Unable to generate concordance". The Logos log shows SQLite errors:

2016-08-28 16:32:09.9063 32 Error ApplicationUtility SQLite Error 2067: abort at 26 in [create unique index Index_WordNumberTextRanges_WordNumberId_TextRangeId on WordNumberTextRanges (WordNumberId,TextRangeId)]: UNIQUE constraint failed: WordNumberTextRanges.WordNumberId, WordNum
2016-08-28 16:32:09.9083 32 Error ApplicationUtility SQLite Error 11: database corruption at line 57527 of [fe7d3b75fe]
2016-08-28 16:32:09.9088 32 Error ApplicationUtility SQLite Error 11: database corruption at line 57569 of [fe7d3b75fe]
2016-08-28 16:32:09.9329 32 Info ConcordanceDatabaseQuerySource (4m 28.5s) Creating concordance for LLS:NABRE 2016-03-10T02:20:28Z
2016-08-28 16:32:09.9334 32 Error ConcordanceDatabaseQuerySource Error writing to database: System.Data.SQLite.SQLiteException (0x00000013): constraint failed: UNIQUE constraint failed: WordNumberTextRanges.WordNumberId, WordNumberTextRanges.TextRangeId
 at System.Data.SQLite.SQLiteDataReader.ReadAsyncCore(CancellationToken cancellationToken)
 at System.Data.SQLite.SQLiteDataReader.Read()
 at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery()
 at Libronix.Utility.Data.PoolableConnector.CacheAndExecute[T](IConnector connector, String text, Object[] parameterNamesAndValues, Func`2 execute)
 at Libronix.Utility.Data.PoolableConnector.ExecuteNonQuery(String text, Object[] parameterNamesAndValues)
 at LDLS4.Concordance.ConcordanceDatabaseSchema.CreateIndexes(IList`1 indexes, IConnector connector, Action`1 updateProgress, IWorkState workState)
 at LDLS4.Concordance.ConcordanceDatabase.CreateDatabase(IConnector connector, ConcordanceResourceInfo resourceInfo, ConcordanceProgressStage`1 progress, ReadOnlyCollection`1 expectedHeadingKinds, ConcordanceExternalResourceInfoManager externalResourceInfoManager, IWorkState workState)
 at LDLS4.Concordance.ConcordanceDatabaseQuerySource.TryCreateDatabase(CancellationToken cancellationToken)
2016-08-28 16:32:11.5727 50 Error ApplicationUtility SQLite Error 1: no such table: Info
2016-08-28 16:32:11.5737 50 Error ConcordanceDatabaseFileManager Unable to create connection to LLS_NABRE_2016_03_10T02_20_28Z.concordance: System.Data.SQLite.SQLiteException (0x00000001): SQL logic error or missing database: no such table: Info
 at System.Data.SQLite.SqliteStatementPreparer.Get(Int32 index, CancellationToken cancellationToken)
 at System.Data.SQLite.SQLiteDataReader.NextResultAsyncCore(CancellationToken cancellationToken)
 at System.Data.SQLite.SQLiteDataReader.NextResult()
 at System.Data.SQLite.SQLiteCommand.ExecuteDbDataReader(CommandBehavior behavior)
 at Libronix.Utility.Data.PoolableConnector.CacheAndExecute[T](IConnector connector, String text, Object[] parameterNamesAndValues, Func`2 execute)
 at Libronix.Utility.Data.PoolableConnector.ExecuteReader(String text, Object[] parameterNamesAndValues)
 at LDLS4.Concordance.ConcordanceDatabaseSchema.IsCurrentSchemaVersion(IConnector connector, IWorkState workState)
 at LDLS4.Concordance.ConcordanceDatabase.GetDatabaseStatus(IConnector connector, ConcordanceResourceInfo resourceInfo, IWorkState workState)
 at LDLS4.Concordance.ConcordanceDatabaseFileManager.GetFileStatus(String fileName, String resourceId, IWorkState workState)

This is reproducible for different users on different machines.

4336.Logos.log