Solution:

This article demonstrates the various methods by which to determine the name of a corrupted database file.

Typically, when a database file is corrupted an error such as the following may be received.

Error 15: Not a Database File

This message does not provide the name of the file that is corrupted. The name of the file may be determined by the steps below:

1. Open System Manager (SM).
2. Under the Transaction menu, point to System Recovery and click Reindex Application Files.
3. Select “Yes” for Remove Deleted.
4. Type the ID of the affected company into the Company Number field.
5. Type the ID of the affected module into the Application ID field.
6. Click Proceed.
7. Click  All when asked to reindex all or only selected files.
8. Click  Yes when asked to confirm reindex.

If the reindexing process is halted by an error, an error message may appear with or without the file name. However, the status bar at the bottom of the window will display the name of the file that disrupted the reindexing process; this is likely the corrupted file. On some computers, this process may execute too quickly to view all the details. In this case, a report may be generated to determine how and why the reindex failed:

1. Note the date of the last reindex performed.
2. Open SM.
3. Under the Print menu, point to System Logs and click Indexing Log.
4. Select the appropriate company and table ID.
5. Select “Failed” for Status.
6. Enter the date range for which the log is to be generated, it should include the date of the last reindex.
7. Unless there were multiple reindexes conducted on the selected date, the time may be left blank.
8. Click Generate.
9. Click Preview.
10. Click Print.

This will produce a report showing which tables failed to reindex.

Important
T here are some system and application tables that have no indexes. Therefore if a No Index Defined message is displayed, it is not a cause for concern and can be ignored.

© Copyright Sage Software