• Error: "Invalid database name. Unable to find database in registry" 
• Error: “Unable to open the destination database” 
• The Database of the selected company must first be converted to one of the appropriate versions listed below before it can be upgrade to this version

Note: Accessing a database on a network drive by a Single User or Lite editions is NOT supported and will corrupt the database.

There are several causes of database errors, including:

• Another user is in the database
• The database moved to a new location or server
• The database .LOG is corrupted
• User no longer has right to that area of the network
• The database has an incorrect Engine Name
• Two databases in the same folder have the same file name with different extensions (i.e., fas.db and FAS.bdb)
• Attempting to open a database that is more than one Schema version back
• The database is corrupted

Note: Single user versions allow only one user to access the database at a time. To have multiple users access simultaneously, upgrade to the Network version. Ensure no other users are in the database.

In Sage Fixed Assets - Depreciation:

1. Go to File, Database List Manager.
2. Highlight the database, click Remove.
3. Click Find, Browse to where the database is located, click OK.
4. Click Search, highlight the database.
5. Click Add, then click Close and Close.
6. Attempt to open the database.
   Notes:
   • If database does not appear in the Database List Manage after adding, the local BESTSYS.DB is corrupted. You will need to swap it with the bestsys.SAV. See Unable to connect to the system database - Single User
   • If you cannot locate the database, consult local IT staff to determine the file location.

If there are errors adding the database:

• Ensure there are no databases with the same filename but different extensions in the same folder (Example: best.db and *.bdb are in the same folder)
• Rename the database .Log file
• If the database will not launch the In-Place Conversion: File, Database List Manager, Highlight the database(s) noted above, and click Remove
• Move the database to the local hard drive
• In the case of database corruption, restore from backup