Issue metadata
Sign in to add a comment
|
Legacy Browser Support gives an error "The alternative browser could not be opened. Contact your administrator."
Reported by
kytech...@gmail.com,
Nov 21
|
||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36
Steps to reproduce the problem:
1. Open Chrome and go to a site listed in Enterprise Mode.
2. Chrome presents the redirection screen and fails to open IE 11
3. The error listed in the summary is presented to the user.
What is the expected behavior?
The expected behavior is it opens Internet Explorer 11 in the document mode as defined in our enterprise mode group policy. This behavior was working perfectly and suddenly stopped.
What went wrong?
The behavior suddenly stopped. The Native_Log.txt file (in the user profile) reports the following:
[*ERROR!*] : core\browser_switcher_core.cc:183 : Could not start the alternative browser! Handle: 00000002 2
[info] : native_component\lbs_native.cc:251 : Command finished with response : {"error":"Cound not invoke alt browser.","id":6,"success":false}
WebStore page: https://chrome.google.com/webstore/detail/legacy-browser-support/heildphpnddilhkemkielfhnkaagiabh?hl=en
Did this work before? Yes Chrome 69 and LBS 5.4. We upgraded to see if it would resolve the issue and it did not.
Chrome version: 70.0.3538.102 Channel: stable
OS Version: 10.0
Flash Version: No Flash
I have the Chrome version 70.0.3538.102 with Legacy Browser Support 5.5.0.0. The Legacy Browser Extension is version 5.5. OS version Windows 10 1803. This was working perfectly for a while and suddenly stopped. We do not know what caused this as we have not made any policy changes.
,
Nov 21
As per comment #0, the issue seems to be related to enterprise. Hence, routing the issue to inhouse team for further triaging. Thanks...!!
,
Nov 21
,
Nov 21
The error code you are seeing means the alternative browser (IE11 in your case) is not found where LBS is looking for it. Can you please check how is your AlternativeBrowserPath policy configured. If it is set to empty or to ${ie} then your browser associations in the registry might be wrong. In this case check what the reigstry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\IEXPLORE.EXE" or "HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\IEXPLORE.EXE" point to and correct it if needed.
If you are using a concrete path to IE in this policy check if it is still correct.
,
Nov 22
,
Nov 26
We were using the hard coded path of the browser that was set correctly based on the browser path.
After modifying this policy to use ${IE}, the problem was resolved. Did something change where we can no longer use hard coded paths?
,
Nov 26
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 27
Not really. If you believe the path was right before as well and has not changed it is indeed weird that this regressed. You can try reverting back to using the hard coded path and see if it still doesn't work for you but using the ${ie} alias is a more hassle-free option in my opinion.
,
Nov 27
,
Dec 5
kytechguy@, Please check the issue on latest chrome stable-71.0.3578.80 and update the bug accordingly as per C#8 .Adding needs-feedback label. Thanks..! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Nov 21