However, this is a documented known error. The troubleshooting steps can be found in the “Javelin Troubleshooting” section of the Javelin documentation, which can be found at
https://docops.ca.com/ca-test-data-manager/4-7/en/javelin/javelin-troubleshooting.
To resolve the socket timeout issue, when attempting to open the Firefox driver, you need to:
- Open a Web browser and navigate to http://selenium-release.storage.googleapis.com/index.html
- Locate the latest version folder which contains the selenium-dotnet-<version>.zip file. At the time this document was create the latest release was found in the 3.5 folder: selenium-dotnet-3.5.2.zip
<Please see attached file for image>

- Download the selenium-dotnet-<version>.zip file and extract the WebDriver.dll and WebDriver.Support.dll files from the zip file.
- On the Javelin Server, open a File Explorer and navigate to the Javelin Install directory. By default this would be C:\Program Files (x86)\Grid-Tools\Javelin\ directory.
- Rename the existing WebDriver.dll and WebDriver.Support.dll files to WebDriver.dll.original and WebDriver.Support.dll.original
- Paste in the new versions of the WebDriver.dll and WebDriver.Support.dll files extracted from the selenium zip file.
When testing the Javelin flow, you may see a new error displayed:
“Execution complete with error:The geckodriver.exe file does not exist in the current directory or in a directory on the PATH environment variable. The driver can be downloaded at
https://github.com/mozilla/geckodriver/releases.”
<Please see attached file for image>

If this is the case, go to
https://github.com/mozilla/geckodriver/releases and download the gekodriver file. If you are using the 64-bit version of Firefox, I would use the 64-bit version of the gekodriver.
<Please see attached file for image>

Unzip the downloaded gekodriver-<release>-win32/64.zip and place the geckdriver.exe file in the Javelin install directory. By default this is the C:\Program Files (x86)\Grid-Tools\Javelin\ directory.
Your Javelin flow should now open the Firefox driver when running the “Open Browser” component in Javelin.
<Please see attached file for image>