"Access violation" Error while accessing Everest screens

Overview

An Everest user may encounter the following error messages while login in or accessing Everest screens on a new machine:

Error Number: -42
Error Message: Access violation at address 807CFFF4. Read of address 807CFFF4

Additionally, the user may receive the error message:

Error while moving to the next step
Error Number: 2122
Error Message: A component named frmPickTicketBrowser already exists

Solution

This error usually occurs when a user attempts to use previously saved User interface settings on a new computing environment that is not capable of displaying or loading them, or when the user interface settings have become corrupted. The procedure to save and export a UI configuration is described in Customizing Everest Windows Settings

Follow these steps to fix the Access violation errors:

Step 1: Reset the interface

Execute the following steps using an account with Supervisor permissions to reset the user interface settings for the affected user:

  1. Log in to Everest, with SuperUser credentials.
  2. Go to File > Set Up > Interface Settings.
  3. Select the user who is receiving the error.
  4. Select Options > Restore factory settings > All settings.
  5. Validate the fix by having the user attempt to execute the previously failing steps.
    If successful, the error message will not come up; otherwise, proceed to Step 2.

Step 2: Re-install Everest client

If the above steps did not resolve the issue, re-install the Everest client by following these steps:

  1. Ensure you have the installation files on your local file system
  2. Uninstall the Everest client
  3. Delete all the Everest directories from C:\Program files(X86)
  4. Delete all the files from C:\Program Data\Everest and EverestInstall
  5. Install the Everest client using the files from your local file system.
  6. After installing, reset the user interface again by following the procedure in Step 1 above.

Testing

Users should be able to successfully log on to Everest and navigate through various screens without encountering the access violation error.

Back to top

Comments

0 comments

Please sign in to leave a comment.