0
Not a bug

Warning : Issue login into Admin section on Edge for Windows 10 15002

Thomas-Louis Laforest 4 years ago updated by Ben Burner 4 years ago 10

The login is process but we are send back to the login page on succes.

Acces is working in internet explorer.

Happend on Win10 15002 (pre-relase to the next Win10 update)

ConnectWise Control Version:
Server Affected:
Host Client Affected:
Guest Client Affected:

Good morning,


Please update this thread with the following information:


1) On which version of ScreenConnect have you observed this behavior (e.g. 6.0.11622)?

2) Does the Edge browser console log any information when you attempt to navigate to the Admin page (open the browser console by typing F12 in Edge)?

3) Please confirm the user attempting to access the Admin page has the "Administer" permission

4) When you're redirected to the Login page, what reason code is appended to the url displayed in the browser address bar?


Cheers,

Ben

1) 6.0.11622.6115 and 6.1.12131.6219

2) Yes, for both version :

Fenêtre active : XXX
Fenêtre active : XXX
SCRIPT5007: Unable to get property 'appendChild' of undefined or null reference
Login (20,2)
SCRIPT5007: Unable to get property 'appendChild' of undefined or null reference
Script.ashx (3004,2)


3) Yes the user has access

4) On 6.0.11622.6115 : 3 on 6.1.12131.6219 : There is no reason on the URL but the message in the login box is the same as on 6.0.11622.6115



Warining 2: It now doing it on all logon try (the before the login for the main section was cached, but it's now expired)

Waiting for information

FYI juste updated to 15007 and same result on both SC version.

Good morning,


I have so far been unable to reproduce the Admin page login behavior you describe. I have tested this with ScreenConnect 6.0.11622 and 6.1.1231 on Windows 10, build 15007.1000 using the Edge browser.


Have you made any customizations to or installed any extensions on your ScreenConnect instance? If so, does temporarily disabling the customizations and/or extensions resolve the issue? Furthermore, does this behavior reproduce on all Windows 10, build 15007 machines, or is the behavior limited to a single machine?


If this continues to be an issue, I recommend submitting a support request with the support team so that one of our techs can take a closer look at your environment to determine what's interfering with the login process.


Cheers,

Ben

Waiting for information

We only have 1 machine on Insider Build.

The issue is still present on 15007 on my side.

There is no customization except some Web.Config/App.Config setting (all done with the extension)

Try disableling all extension and no change to the login page action.


Confirm me the path to request a support team review.


Good day


Under review

Good morning,


Please open a ticket with support by either starting a chat session or submitting a summary of the issue you're having -- both of these options are listed on the ScreenConnect support portal at https://www.screenconnect.com/Support


Regards,

Ben

Commenting disabled