This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Another bug after upgrade to 21.8.10524.3 - critical - Auto Logout does not work

Although the settings of both the desktop clients and the Web app are made for automatic decomposition according to this instruction:

https://m-files.force.com/s/article/mfiles-ka-44709

there is a gradual occupation of all concurrent licenses, which leads to the inability of the next user to enter. In general, at the moment it is not very busy and there are really three and five users working competitively. There is also a difference in the information about currently logged in users and the currently used competing licenses.

Not to mention that in all the versions I've worked with after the upgrade, it is unknown why M-Files decided to reset the settings in the IIS and it is necessary after each update to run the Web chat from the above instructions.

Parents
  • I ran into this issue aswell.

    I opened a support ticket today.

    I will post the resolution, as soon at I get an answer.

  • Hello Radu Moca,

    Is there any new information about this bug? ( gradual occupation of all concurrent licenses ) . We have same problem - difference in the information about currently logged in users and the currently used competing licenses. It is a huge problem for us.. Thanks you

  • Hi, Pkjack,

    I also open ticket to M-Files. At this moment M-Files guys investigate the problem.

    If I have any useful information I'll share with community.

  • Hello,

    They are still investigating.

    I sent some logs from M-Files server and now waiting for response.

  • This is the response till now:

    A short status update: This issue is still under our investigation of our development support team. We also reported this problem as a new product issue ID 160480 to our product development.

    Note: When our product development has created a fix for some issue, the issue's ID is reported also on our release notes here: www.m-files.com/.../
    From the release notes you see when we have released a new version that includes a fix for the issue.

  • It's the same here. Obviously we will have to wait for a new release. I wonder how many installations are affected and whether the release of concurrent licenses only applies to users who use the Web or those who use the desktop client. At the moment I can't confirm that the desktop users are affected. Some had more impressions?

  • Hi Radu, the issue report is still open. Apologies of the inconvenience to server admins that are having issues because of this. 

    By the tests I had an information that restarting the mfserver.exe would solve the issue. 

    For Cloud Vault customers, they should contact support as they have no access to the server processes. 

    This is just a workaround for this issue. Nothing more. 

  • Hi Timo,

    I can confirm that restarting the M-Files Service Server frees the licenses and can be a solution to the problem for a short period of time - depending on the activity of the users.
    All the colleagues who decide to use this workaround should be aware that a large number of tickets from users can come their way. The reason is that restarting this service can lead to unexpected behavior on the clients side

Reply
  • Hi Timo,

    I can confirm that restarting the M-Files Service Server frees the licenses and can be a solution to the problem for a short period of time - depending on the activity of the users.
    All the colleagues who decide to use this workaround should be aware that a large number of tickets from users can come their way. The reason is that restarting this service can lead to unexpected behavior on the clients side

Children