Error Starting Chrome message when starting eLodge

If there is a conflict between your version of Google Chrome and your version of ChromeDriver on your machine, you may receive one of the below error messages when starting eLodge.  This guide explains how to resolve the issue.

1. Re-start your machine from the Windows icon

Your ChromeDriver file may be locked by windows and unable to update.  Re-starting Windows will clear the lock and allow ChromeDriver to update the next time Migration Manager starts.

  1. Click the Windows Icon.
  2. Click the Power button.
  3. Click Restart.

(Do not click 'Shut Down' as this does not actually do a full restart of your machine).

2. Ensure your Google Chrome is installed and up to date

Make sure Google Chrome is installed on your machine.  As well as this, your version of Google Chrome may have not yet auto-updated, or it may have an update pending.  Make sure your Google Chrome version is up to date

Open Google Chrome, then:

  1. Click the Settings icon on the top-left of screen.
  2. Click Help.
  3. Click About Google Chrome.

Ensure your Google Chrome says 'Google is up to date'. (If it is not up to date, Google Chrome should automatically update at this point or prompt you to re-launch the application).

For full details on how to update Google Chrome, see: Google's Support Page.

3. Manually removing the ChromeDriver.exe file.

If you continue to receive the 'Session not Created' error below, follow these steps to manually remove the outdated file.

3.1. Restart your Machine again

From your Start button, select Power, then Restart.

3.2. Delete ChromeDriver.exe

1. After restarting your machine and before you start Migration Manager, go to your C:\Program Files (x86)\Migration Manager\ folder (maybe called 'Leap Migration Manager')

2. Locate the ChromeDriver.exe Program and delete this file.

Note: Depending on your system's settings, you may not see the ".exe" at the end of the file name.  You will see either ChromeDriver.exe or just ChromeDriver.  Delete whichever one you see.

3. Start Migration Manager and run eLodge. A new ChromeDriver should download upon starting Migration Manager.  Wait a few moments after logging in, then try running eLodge again.

eLodge should now run without error.