Import Failure and Manual Restore

    

Gravity takes the following steps when you 'Import' a GDX file:

1.   Decompresses the gdx file to a temporary directory.

2.   Performs checks on the extracted files to make sure they are valid, and specifically checks the registry file is valid and is only accessing Gravity registry keys. (i.e. it has not been hacked to do something nasty)

3.   Exports the current database and all settings. (this is so that if the import does not work it can be rolled back)

4.   Closes the database engine, other open files and forces settings to be saved.

5.   Imports the Registry file.

6.   Copies the database files to the correct location.

7.   Copies 'mywords.lst' to the correct location.

8.   Cleans up the temp directory and finishes.
If there is an error in steps 5, 6 or 7 it aborts the Import, reports the error and then performs an 'Import' on the temporary export that was created in step 3.
If *this* fails, it throws out an error message, this being:
"Could not restore old settings. Gravity cannot proceed without a valid database. Please refer to the user manual for further help on how to repair Gravity."
It will also contain the location of the temporary export created above in step 3. NOTE: Write this down, you will need it.
At this point you have 4 options you can take to fix things up. Please try steps 1 to 4 in order.

1.   Delete the current database and the Gravity 2.9 registry tree. Run Gravity. The new installation screen will appear. Press Import and try to import the temp export it created. The filename of that file is in the above error box.

2.   Delete the current database and the Gravity 2.9 registry tree, manually extract the contents of the temp export (rename the GDX file to a ZIP file), copy it in manually and run the registration import file manually. This should be a guaranteed way of getting it back up and working with no loss of data/settings.

3.   Delete the current database and the Gravity 2.9 registry tree, import a backup. Anything done/downloaded since the backup was made is lost, but its an option if there was a problem in the temp export.

4.   Delete the current database and the Gravity 2.9 registry tree, start from scratch - worse case scenario.
Note this error should be extremely rare, if ever.