Hi,
I keep having this error everytime I update to version 11 of CONNECTION Client (al versions are the same, currently using 11.03.25). I usually use version 10 and works fine, but when other software needs to be updated, automatically updates CONNECTION Client. Also, RAM CONNECTION doesn't work with version previous than 11.
If I update to use RAM CONNECTION, I cannot use Staad.Pro, if I use Staad.Pro I cannot use RAM CONNECTION.
Can you please provide a working CONNECTION Client version?
Hello Saul,
Please follow the instructions give in the below support communities link; https://communities.bentley.com/communities/other_communities/licensing_cloud_and_web_services/w/wiki/54520/connection-client-says-working
Regards,Abhishek
Answer Verified By: Saul Cuen
Sorry, I verified as answer but today, after a week, the problem came back.
So is not the installation of Microsoft Edge WebView2.
Firewall...well.. it worked for a week, it always works for a week. I can uninstall, reinstall and works again... for a week, and then I get this screen.
Any other permanent SOLUTION?
When this no longer works, is the DLL that is mention in the article gone? That has been the cases we have seen. We have support tickets open with Mircosoft.
How can I install a previous version of RAM Connection? Previous version of RAM Connection worked with previous version of CONNECTION Client and Staad.Pro, and I could get a job finished.
As Glenn advised - check for the x64 folder as mentioned in the article, which Abhishek posted - see Solution #1:
If the issue persists and you are running a 64-bit operating system, confirm an x64 folder exists in the following location, noting <version number> is a placeholder for a four-part version number:
C:\Program Files (x86)\Microsoft\EdgeWebView\Application\<version number>\EBWebView
If the x64 folder is missing, please consult with IT to determine with Microsoft why the WebView2 component is not installing 64-bit components.
***NOTE: As a temporary workaround you can copy the x64 folder from another workstation that has it, but note the problem will return the next time WebView2 updates on the machine.
The previous version of RAM Connection could have worked without that issue as the version of the CONNECTION Client, that came with the installation package, was probably still relying on IE and not on Edge.