-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot launch Edge from a service #7
Comments
Is this on the same machine? If not, note that Edge is not supported on Windows Server. |
I see the same behavior trying to run via a teamcity agent on a windows 10 Pro OS. I can run my test script manually but when the agent attempts to start Edge it gets the same error message "ERROR: The process "MicrosoftEdge.exe" not found." |
I see the same behavior on a Windows 10 Pro running GoCD agent as a service. Its unable to launch edge. |
Hello? Gays! 95% emitting08 07 2020 16:09:02.373:INFO [launcher]: Trying to start Edge again (1/2). 08 07 2020 16:10:02.579:INFO [launcher]: Trying to start Edge again (2/2). 08 07 2020 16:11:02.691:ERROR [launcher]: Edge failed 2 times (timeout). Giving up. My EDGE have name C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe |
Do you have new Edge (Chromium) or legacy Edge (ChakraCore) installed? |
I am able to run FireFox and Chrome using the same config. But when I tried to add Edge, it gives me this errror 19 04 2021 09:56:05.915:INFO [launcher]: Starting browser Edge 19 04 2021 09:56:27.489:ERROR [launcher]: Cannot start Edge 19 04 2021 09:56:27.489:ERROR [launcher]: Edge stdout: 19 04 2021 09:56:49.075:ERROR [launcher]: Cannot start Edge 19 04 2021 09:56:49.075:ERROR [launcher]: Edge stdout: 19 04 2021 09:57:10.667:ERROR [launcher]: Cannot start Edge Any leads to solve this issue? |
This might have something to do with this issue? |
I can start Karma with Edge on the command line when I do it manually. However if I have a Windows Service running under say "Network Service" it does not look it can find it.
Console output:
The text was updated successfully, but these errors were encountered: