If you are getting a 12001 error message:

Usually this comes up if you are using Reference Manager 9.5 or earlier and you are trying to open a Reference Manager 10 or 11 database. This is because the database structure has changed between versions. Click here for more information and for a resolution.

If you are getting the 12023 error message:

1. Open the database.
   
   
2. Highlight the first reference on the list.
   
   
3. Wait for it to display it's information in the window.
   
   
4. Use the DOWN ARROW key on your keyboard to move to the next reference.
   
   
5. Wait only long enough for the information to appear on the screen. This should literally only take a fraction of a second.
   
   
6. Continue this process. You should encounter some references where you get the 12023 message, and the information does not appear. On these references, use the Spacebar to mark them.

Once you reach the end of the database, and have marked all of the 12023 references:

1. Create a New Database from the File menu.
   
   
2. Open the References Menu, and choose "Copy Between Databases".
   
   
3. Set the database with problems as the source.
   
   
4. Set the new database as the target.
   
   
5. Set the References to "Unmarked References".

This will leave the bad references behind. If the database is not too large, then this should go fairly quickly.

If you are getting the 12037 or 12049 error message:

First, make certain that if you are converting the database to a later version, that you are opening the database in Read/Write Exclusive mode. When you go to "File > Open Database", make sure the "Access Rights" at the bottom of this dialog is set to "Read/Write Exclusive".

This problem is related to your index file which has somehow become corrupted. Please make sure you have a good backup copy of the database (copy both files .rmd and rmx to another location on the hard drive), then rebuild the database.

If you are upgrading the database from v.8.5 to v.9 or later you may get an error 12049. If you encounter the 12049 error while trying to upgrade your database, you should delete the v.8 database's .rmx (index) file and then rebuild the database in the later version which will construct a new index file. Attempting to upgrade the database without deleting the index file will be unsuccessful.

If you are getting a 12043 error message:

Usually this indicates that you are on a Novell network, and that you need to update to the latest client patch from Novell. To test this, try moving the database from the network drive to your local hard drive and see if you can open a local copy. If so, make sure you have all the latest Novell network client patches installed on the workstation.

Other errors in the 12000 series usually indicate a corrupted database that needs to be rebuilt. For instructions on how to properly rebuild your database:

Please click here to see our FAQ on how to properly rebuild your database.