Error/Failure

Whenever attempted backups fail or the last retry attempt fails, the following event is recorded in the Event Viewer or the Scheduled Backups Summary.

The following list shows various Error/Failure reasons and troubleshooting tips:

Possible Cause: The DB Programming installation is corrupt.

Corrective Action: Reinstall DB Programming.

Possible Cause: Scheduled Backups were attempted for a DB Programming version that does not support this feature. This can happen if a system is downgraded after Scheduled Backups are scheduled. The only other way this can happen is if a Scheduled Task or registry settings become invalid (possibly via user intervention) or if you attempt to run DB Programming from a command line.

Corrective Action: Check the system version to make sure the proper version is installed. Upgrade if needed. If it appears that the Scheduled Task or registry is corrupt, try changing a parameter and rescheduling the task. If this problem persists, contact Technical Support.

Possible Cause: The software could not register a timer.

Corrective Action: Try rebooting the computer. Make sure the computer is functioning properly for other unrelated types of operations. If this problem persists, contact Technical Support.

Possible Cause: Session information in the registry is corrupted.

Corrective Action: Contact Technical Support.

Possible Cause: Session information in the registry is corrupted.

Corrective Action: Contact Technical Support.

Possible Cause: The executable file is missing or corrupt.

Corrective Action: Reinstall DB Programming.

Possible Cause: The message is self-explanatory.

Corrective Action: Fix the modem entry name.

Possible Cause: The media to which the system database is to be saved does not have enough free space to hold another database file.

Corrective Action: Make space by deleting or off-loading files, or choose another storage media.

If there appears to be plenty of space, try rebooting the computer. If this problem persists, contact Technical Support.

Possible Cause: There are no versions of database programming installed. This can only occur if the registry is corrupt.

Corrective Action: Reinstall DB Programming.

Possible Cause: This database file is missing.

Corrective Action: Reinstall DB Programming.

Possible Cause: The database schema file is missing.

Corrective Action: Reinstall DB Programming.

Possible Cause: The message is self-explanatory.

Corrective Action: Make sure the file is accessible, not read-only, and not in use. If necessary, reinstall DB Programming.

Possible Cause: The message is self-explanatory.

Corrective Action: Make sure the file is accessible, not read-only, and not in use. If necessary, reinstall DB Programming.

Possible Cause: The registry is corrupted.

Corrective Action: Reprogram the IP address or host name for the session in the Edit System Connection dialog box (see Adding/Editing Connections), and then try again.

Possible Cause: The session no longer exists. This can only happen if you manually alter the registry, deleting or renaming a session, or if you edit a Scheduled Backup task in the Windows Task Scheduler.

Corrective Action: Delete the task from the Windows Task Scheduler, or reprogram the session. If this problem persists, contact Technical Support.

Possible Cause: The path is invalid, inaccessible, unavailable, or read-only.

Corrective Action: Make sure the path is correct, that you have access to the path, and that it is not read-only or in use. If this problem persists, contact Technical Support.

Possible Cause: The last step of the database save failed. It could not be inserted into an archive.

Corrective Action: Make sure the path is correct, that you have access to the path, and that it is not read-only or in use. If this problem persists, contact Technical Support.

Possible Cause: The path is invalid, inaccessible, unavailable, or read-only.

Corrective Action: Make sure the path is correct, that you have access to the path, and that it is not read-only or in use. If this problem persists, contact Technical Support.

Possible Cause: The path to a system database save file must be 60 characters or less. To allow for the 17-character file name: YYYYMMDDHHMM.intl, the folder name must be less than 43 characters.

Corrective Action: Change the destination folder for the system database in the Save system database to folder box so that it is less than 43 characters.

Possible Cause: An exception occurred when trying to overwrite or write to the path.

Corrective Action: Make sure you have access to the path, and that it is not read-only or in use. If this problem persists, contact Technical Support.

Possible Cause: There is a serious shortage of memory on the computer.

Corrective Action: Try resetting the computer. If this problem persists, contact Technical Support.

Possible Cause: Installation information in the registry is corrupted.

Corrective Action: Reinstall DB Programming. If the problem persists, contact Technical Support.

Possible Cause: Installation information in the registry is corrupted.

Corrective Action: Reinstall DB Programming. If the problem persists, contact Technical Support.

Possible Cause: Session information in the registry is corrupted.

Corrective Action: Contact Technical Support.

Possible Cause: Session information in the registry is corrupted.

Corrective Action: Contact Technical Support.

Possible Cause: There is a problem with the database itself.

Corrective Action: Try restoring a recent backup to the system. If none is available or this does not solve the problem, contact Technical Support.

Possible Cause: The language database is missing for this DB Programming version.

Corrective Action: Reinstall DB Programming.

Possible Cause: The flavor package database is missing for the DB Programming version.

Corrective Action: Reinstall DB Programming.

Possible Cause: There is a problem with the database.

Corrective Action: Restore the last saved database, or use DB Test to repair this database. If this problem persists, contact Technical Support.

Possible Cause: The message is self-explanatory.

Corrective Action: Manually resolve the problem with the Voice Processor connection, or manually start up DB Programming to indicate that you wish to run DB Programming without a Voice Processor connected.

After performing either of the above, the backup should complete. If the Voice Processor is disconnected, voice data is saved.

Possible Cause: The message is self-explanatory.

Corrective Action: Verify that the IP address or host name programmed for the session in the System Connection dialog box is correct (see Adding/Editing Connections). Make sure it matches the system to which you are trying to connect.

Possible Cause: You have attempted to run DB Programming via command line.

Corrective Action: Do not run DB Programming via command line.

If you have not attempted to run DB Programming via command line and you get this error, contact Technical Support.

Possible Cause: An unhandled exception occurred during the save of the voice data. The <description> of the exception is provided by Microsoft Windows.

Corrective Action: If it is not obvious what to do from the description, contact Technical Support.