M-Files Auto - log out triggering constantly.

I've not heard of any widespread issues.  Have you raised this with support?

Dominik said:

Hi, I would like to share my experience with this issue as well.

Short version: I have this issue as well, any information?

Long version: 

Today a user called in to tell me that he is having an issue with opening M-Files, so I connected to his computer. What happened is that whenever he wanted to open up M-Files, he got the auto-logout message pop up and even if he clicked "No", it popped up again right away until he clicked "Yes" and logged off. He basically could not open up M-Files at all.

I didn't have much time to check his registry keys or other specific settings, but I will provide as much info about the situation as I can.

Time: This happened few days after a company-wide update of M-Files through the automatic updates setting. Few details on that are in this post. Previously users used varying versions I think from approx. 20.8 all the way to 22.2., all of them then recieved the update to 23.4., which is what the mentioned user is using now. Also, I am not sure if he was able to use M-Files after the update at least once before this issue happened, but I will be able to get more information next week.

Settings: In the new Advanced Vault Settings (AVS) > Automatic Logout I did not change anything, like so:

I think that the user doesn't have any special logout timer settings changed through registry keys either (I did not check though), but even if he had, from what I've read, the minimum logout time is 1 minute.

What I will try next (not all at once of course): Restart his computer, check his registry keys, change the "Inactivity Time for Automatic Logout" setting in AVS to some non-default value.

My questions: I see that this post is marked as solved, so maybe it was solved individually through support? Can you provide any information? Thank you in advance.

Regards, Dominik

Previously written and accidently deleted...

Hi we've had had this issue too for two users. But both users who had it I noticed they had pending Windows updates. Once these were applied and machine was restarted in both cases we no longer faced the issue.

Update: I had to uninstall and install version 22.2. to repair this...

What I tried before doing this:

- restarted PC
- checked Windows updates (everything was up to date)
- restarted MFStatus, MFClient, MFSetup, MFAUClient
- changed server AVS settings for automatic logout multiple times
- both changed and deleted the AutomaticLogoutTimeoutInMinutes registry key
- disabled/enabled automatic updates registry keys (Common\Updates\Enabled and %MFilesVersion%\AutomaticUpdate)
- changed, deleted and re-set the Vault connection settings
- disabled and enabled the user having the problem
- changed the user's license types (no license, read-only, etc.)
- reinstalled (fully uninstalled, installed back) version 23.4. manually (msi)
- fully uninstalled, installed version 23.1. manually (msi)

None of the above worked except installing version 22.2... I've heard from our distributor support that there was a change sometimes last year about Automatic Logouts. I was only able to find changes with IDs 163100 (May) and 163868 (August), so maybe one of these changes is the cause? They seem like non-threatening changes though.

One more thing that I'd like to mention is that this already happened in October of 2022 to one of our other users (who is also an mfiles admin) and for him it was apparently fixed by just updating mfiles to a newer version. I cannot confirm this though, because I didn't look into this issue too much before. I also don't know his version when the issue happened or the version he updated to, or any details besides what I mentioned, sadly.

I would be glad if this issue was looked into a little bit. I know this is only two people out of hundreds in our company to which it happened, but it's just frustrating to have M-Files behave in unpredictable ways that cannot be solved besides using an older version.

Thank you.

Another update: 

Uhhhhmmmm... So, what happened now was that he had automatic updates turned on (because of Group Policy) and it updated back from 22.2. to 23.4. and it didn't work again, AND I could not reinstall his version back to 22.2. anymore (there was some error). So I told him to restart the computer so that I can try to reinstall after restart. I then jokingly said "let's try it now after restart, just in case it will work after the second restart".

Well... It worked. The second restart after automatic update helped.

To whoever will read this in the future and will try to fix this same issue, good luck.

Hi, seems to have resolved itself since rolling out 23.1 (previously on 22.10).

I also tried similar troubleshooting beforehand:
- restarted PC
- checked Windows updates (everything was up to date)
- restarted MFStatus, MFClient, MFSetup, MFAUClient
- changed server AVS settings for automatic logout multiple times
- both changed and deleted the AutomaticLogoutTimeoutInMinutes registry key
- disabled/enabled automatic updates registry keys (Common\Updates\Enabled and %MFilesVersion%\AutomaticUpdate)
- changed, deleted and re-set the Vault connection settings
- disabled and enabled the user having the problem
- changed the user's license types (no license, read-only, etc.)

If the problem occurs again, I'll attempt more of the suggested troubleshooting but hasn't occurred since the update. 

Thanks for all the suggestions!

Hi,

I had the same problem after I updated to 23.4 and configured the autologout via the Advanced Vault Settings the problem was gone.