Authentification in progress...
For the user accounts: where and what do I have to modify?
If you are able to authenticate against your domain at all, then you shouldn't need to modify anything else. The issue was that after upgrading to 3.2.0.0 the AuthenticationType was not set correctly and no user at all could log in.
Authentification in progress...
The AuthenticationType of my users had a value of 3 which I verified before leaving Friday night. This issue then occurred Saturday morning. I'm hesitant to leave this particular issue in production since we are a 24/7 shop.
While Georg may have more outstanding issues I am not privy to, it appears we share this one after upgrading to 3.2.0.0.
With that said, Georg tried the SQLite change and I tried the AV exclusion change. I can upgrade again and let it break, but I can't have it down for hours at a time waiting for time zones to align for a session. We can certainly attempt to get a session going so you can see it in action, but perhaps a simple log gather at the time it occurs may be more realistic?
Authentification in progress...
have you user account been modified to specify the authentication type?
In my case, yes I confirmed a value was set for all of my users and the issue still occurred.
Authentification in progress...
Maurice, I have had multiple issues with DVLS 3.2.0.0. They are listed in the current email thread that support has.
Regarding this particular issue, yes, I have it as well. I saw this thread after upgrading but before the issue occurred in my environment. Once this issue occurred Saturday morning and I confirmed all of my clients were unable to connect I decided that this version broke more than it fixed in my environment so I rolled back to 3.1.0.0.
It looks like Georg is also using AD. Perhaps it is related to the new code that was introduced for that? Are there perhaps more tables in the DB that need to be manually touched to make this version work?
Authentification in progress...
I am not. I experienced this issue over the weekend with two Windows 7 computers running RDM 11.1.0.0 against DVLS 3.2.0.0 which was previously working perfectly fine against DVLS 3.1.0.0. The other computer I experienced this on at the same time was a Windows 10 computer running RDM 11.5.0.0.
No changes were made on the client side so I'm not sure why this would be a file locking issue when only the server was upgraded.
Authentification in progress...
I'm having this issue as well on DVLS 3.2.0.0. This happens on both RDM 11.1.0.0 and 11.5.0.0 clients which previously had no issues on DVLS 3.1.0.0. I tried adding that directory to the AV white list but that did not help.
Win10/RDM 11.1.14.0/DVLS 3.1.0.0
I recently upgraded my workstation from Windows 7 to Windows 10.
On Windows 7 I was able to use RDM 11.1.12.0 (and all beta versions earlier, did not test 11.1.14.0) and see sessions that required being in a specific security group.
On Windows 10 with all beta versions of 11.1.5.0 and newer (I wasn't able to test 11.1.1.0) I am only able to see sessions that are not locked behind a security group. If I downgrade back to 11.1.0.0, everything works as intended.
Any ideas?