Access Violation Errors - General information and workarounds 

Topic T1167 Applies to All NEO Products



Description

This Knowledge Base article provides some general information on Access Violation errors and provides possible workarounds if they occur.
NOTE: Identified technical causes generating these errors will be taken into account for next releases of our NEO products - this is an ongoing activity to make them less vulnerable for these errors.


General information

Access Violations errors in general are of incidental nature and can be triggered by a wide range of causes most of which are benign issues.
Due to the incidental nature, it is mostly not possible to force this error again even not when repeating same chain of events which triggered the error.
In most cases it is possible to continue to use NEO without further action. Closing and restarting NEO can be done as a precautionary action.


Possible workarounds

If AV errors are more than incidental, restarting the program or, if more persistent, a reboot of the system will mostly be enough to clear the issue.
If afterwards these continue to occur more than incidental a Catalog rebuild - usually reserved for database errors - will most likely clear the problem.


Corrective actions for incidental AV errors

As stated above Access Violation errors can have many causes.
The following knowledge base articles have in certain cases provided a solution and reduced or eliminated occurrences:


Corrective actions for fatal AV errors

Access violations may arise from install and setup of NEO for seemingly no reason. This may occur on Windows XP service pack 2 or greater or Windows Server 2003 service pack 1 or greater. The effects are benign for the PC but NEO simply may not run.
Alternatively, in very rare cases and mostly after a series of repeating AV errors, an Access Violation error can become a fatal error during startup.
Also in this case rebooting the system or forcing a rebuild of the Catalog might resolve the problem. Please refer to T1007/T1008 through the links provided above for instructions to rebuild the Catalog. In these KB articles also the procedure is contained to start NEO in a non-Catalog state in case NEO fails to start while opening the catalog.

When a rebuild of the Catalog as described in T1007/T1008 is not solving the problem or when NEO can simply not be started without generating an AV error, uninstalling and forcing a clean install of NEO Pro or NEO Find will, in most cases, resolve the problem. As the catalog can be maintained during the uninstall no lengthy synchronization is needed after reinstalling the product.

Perform the following to force a clean install of NEO Pro or NEO Find:
 1) Export your current layout settings: within NEO go to View | Layout | Export...
2) Take note of your licensing details under Help | License as you will need to reenter this information later on.
3) Uninstall NEO from Control Panel, Add/Remove programs (keep the catalogs when prompted during the uninstall).
4) Remove the install directory C:\Program Files\NEO Pro or C:\Program Files\NEO Find (if still existing)
5) Remove entries of NEO from the computer registry:

- Open the computer registry (Start - Run - Regedit)
- Browse to HKEY_CURRENT_USER\Software\Caelo Software
- Remove this Caelo Software registry branch - make sure to only delete this branch.

6) Install NEO Pro or NEO Find again; enter your licensing information again when prompted.
7) You can now import your layout settings again.
After install the existing catalog can be opened again (within NEO go to File | Catalog | Open Catalog).



Last updated: 10 December 2008