I'm fairly new to Bentley products, but so far haven't had any issues that weren't resolved by following a KB article or forum post here.
However, this week I have a user on Connection Client 188.8.131.52 with Windows 10 Pro who can't log in to Connection Client. The program is running and is viewable in the task bar, but we cannot open it and right-clicking does not provide the usual context menu.
If we kill the process another one spawns but this has the same result. So far we've tried:
- uninstalling and re-installing
- deleting %localappdata%\Bentley\MySELECT.DB and %localappdata%\Bentley\Licensing\LicenseService.DB
- checking for available updates
- restarting all available Bentley services we could see
Does anyone have any thoughts on what might be happening? It may be worth noting that the user previously had v10.x of the Connect client (unfortunately I don't know which exactly, but it was early enough that it needed to be upgraded) - however there doesn't appear to be any traces of this left in the system.
i Have the same issues after new contract. I can open the connection client but i can´t login. :-(
I'm getting this
I find it incredible that you make a mission critical piece of software dependant the the vagaries of what Microsoft might do to its broswer. Surely a simple form for requesting an email and password doesn't need to rely on 3rd party software?
Just curious, if you all can push the Connection Client updates out to everyone, is there a reason you can not push out the older version till this issue gets resolved? I really do not want or should need to get with our 300+ users to do this workaround. We have always told our users to be sure to keep on the updates so that we don't run into issues. Really hope this doesn't turn into a similar issue like gINT and the Microsoft Access Database issue that has been going on for nearly a year with nothing being resolved other than the work around!
This issue is not just affecting Bentley, from what we are told there are other companies that are having issues due to this as well. This is a priority for us and we will continue to make it a priority by pushing for our vendor to fix this asap.
For current updates I would suggest going to https://status.bentley.com/ This site will be updated whenever we have more details to provide.
Having the CONNECTION Client push out the .109 build would not be helpful to those users already on .16/18 as they could not sign in to get the update.
Microsoft has identified the issue and we have created a new build of the CONNECTION Client to work around the issue. We are currently testing the build and hope to have it available in the next day or so. We are also working to see if Microsoft can push out a patch so that users are not required to install the new version of the CC.
Any future updates on this issue will be posted on the status page I mentioned above. https://status.bentley.com/
Answer Verified By: Anthony Murdoch
Hi... well, It's June already and I keep having the same problem with all updates of version 11. And each time I update other software of my suite, like Ram Connections or Staad Foundations, automatically updates Connection Client first, and then, stop working. So I have to go back to any version 10.