Remote Launch not working with Selenium 2.0

Hi Harpreet

It sounds like the Selenium server is not listening on port 7054:

http://stackoverflow.com/questions/16140865/unable-to-bind-to-locking-port-7054-within-45000-ms

This is not something we can really help all that much with since it's a Selenium internal issue, however if you need more details, I'd recommend sending us a help desk ticket with additional information about your Selenium configuration, in particular verifying that Selenium is listening on that port.

Regards

Adam

This error typically occurs because Firefox or the Selenium WebDriver is stuck, or another process is already occupying port 7054. To fix this, open your Task Manager, kill all active firefox.exe and geckodriver.exe processes, and then restart the Spira RemoteLaunch service.