Here is an example of the error that might appear in the application event log:

Event Type: Error
Event Source: Session Indexer
Event Category: Indexer
Event ID: 9864
Date: 10/9/2009
Time: 2:41:05 PM
User: N/A
Computer: TLDB01
Description:
Failed to retrieve record from Canister. Error 160(0) in NextLssnRec():
retrieving first batch of unindexed LSSN records.. (Type: FAIRCOM; Code: 160).

If the Event Source is the Session Indexer as indicated above, the sessions are skipped for the indexing run and are picked up on the next one.

The sessions that are waiting for indexing are still indexed; there is no risk of data loss. However, the eventlog continues to receive these errors messages until the current day's data is fully indexed. If these errors continue to show up in the eventlog after a couple of days, contact Support.

• No errors are reported in the TLTMaint logs.
• Automated indexing processes are not able to run at all.

The following error may appear in the Application event log:

(11:29 Session Indexer) - Failed to retrieve record from Canister.
Error 160(0) in NextLssnRec(): retrieving first batch of unindexed
LSSN records.. (Type: FAIRCOM; Code: 160).

To fix the indexes:

1. Through TMS, shut down Canister services.
2. On the Canister data volume, create the following directory at the root of the volume:

   
   lssn\Canister.dbs
   

3. From the Canister datastore, move the LSSN_<Date>. files to the above directory, where <Date> is the date of the server crash.
   Note: You must move the files out of the Canister datastore.
4. Restart Canister Services.
5. Check that the indexer error message is not longer present.

Perform the following steps to recover the session data file moved into the lssn\Canister.dbs directory:

1. Delete the *.idx files from the \lssn\Canister.dbs directory.
2. Run the following command in a command shell:

   
   tltmaint -v -noserver -archiver -localdir \lssn
    

   Note: Depending on the file size of the session data, it may take some time to complete the above command.
3. When the command prompt returns, the last line indicates the status. A "no errors" message indicates that all is well.
4. Copy files with LSSN_ prefix from the \lssn\Canister.dbs directory back into the canister data directory.
5. Restart Canister Services through TMS.
   The session data is now available.
6. To test, search for sessions from the date of the server crash.

The following error may appear repeatedly in the Application event log:

Failed to retrieve record from Canister. Error 69(0) in ProcessSesn():
Could not update session CANISTER.dbs\LSSN_20120815_MyServer.dat 469778184.
isam_err = 69. (Type: FAIRCOM; Code: 69).

This error may appear even after recycling services and rebooting the Portal, and the Canisters are appearing to operate normally.

To repair this problem, complete the following steps to rebuild the indexes.

1. Log in to the server hosting the Canister as an administrator.
2. Navigate to the directory where the above file is located. Typically, this directory is the following:

   
   <install_directory>\Canister\Canister.dbs
   

3. Move all files (there should be 3) matching the following name pattern out of the Canister.dbs directory:

   
   LSSN_20120815_MyServer*.idx
   

4. Restart Canister Services through TMS.
5. When the Canister restarts, it attempts to rebuild the indexes by reindexing all sessions that are stored on the Canister. Depending on the volume of data, this process can take several hours.