CONNECTION Client Microsoft Edge error, I have installed the latest release 11.00.02.16.
Installs requires an admin account, once installed the following error occurs during CONNECTION client launch
Appears to be looking for the admin account user folder which doesnt exist, and wont on most users machines
Any ideas
Chris
We've been having the same problem for weeks now. Would like some guidance from Bentley about this.
I just reproduced this issue in a test environment. It occurs if you explicitly right-click on the installer and select "Run as administrator" or execute the installer from an Administrator Command Prompt or Windows PowerShell console. Once the installer finishes, it starts the Bentley Licensing Service and CONNECTION Client as the administrator account, not the user. When the Edge WebView controller starts as the normal user and attempts to communicate, it fails because of permissions issues. Note the different users in the screenshot below:If this occurs, restarting the machine should resolve the issue since all administrator instances of the Bentley Licensing Service and CONNECTION Client will be stopped. To avoid the issue in the future, please run the CONNECTION Client installer as a normal user. When clicking the Install button, Windows will prompt for credentials to elevate the installer only, note the processes that start after its completion.
Do the two error windows specify a path in the user's own user profile or another user's?
The user's own user profile.
Following up as this issue is still ongoing...
My apologies for the delay! I have created a service request and will reach out to you directly via email for diagnostic logs for further troubleshooting. You will be receiving an email from me in the next 5-10 minutes. If you do not, please let me know. In the meantime, if some users are production down, please downgrade to CONNECTION Client 11.00.01.109 or earlier on affected machines since the issue involves the new Microsoft Edge integration introduced in 11.00.02.16.
The problem was ultimately determined to be a folder permissions issue which was resolved with the following steps: