Thank you for your post.
We do have some previous reports of this issue. It may be due to an update issue. It is reportedly resolved by:
-Uninstalling FileMaker Server
-Renaming FileMaker Server folder
-Reboot the machine
-Download the most recent installer (220.127.116.114)
I will also add this thread to the report and let you know if we obtain any further information!
1 of 1 people found this helpful
Just out of the blue we got this problem at one of our customers. They have 140 licenses in an ASLA. Usually a the maximum peak during a day is between 70 and 100. Most of the time around 80 people are connected + 2 robot. Friday afternoon when everybody need to do their final time billing for the week we have seen peeks up to 130 users.
I have set the max. number of users to 160 (140 is the actual license limit), but allowing for some not being disconnected fast enough.
But two weeks ago the alarm bells rang. When users tried to connect they where rejected. The dialog said that the max number of users was reached.
An existing group of less than 140 people was able to take up 160 connections (not talking about license connections).
It is was not acceptable to restart the server, so I increased the permitted max to 200. And expected the problem to go away over night.
Next day the bells rang again: Now 200 users was connected out of less than 140 possible:-)r
Due to the fact that restart was out of the question I increased the max. limit to 300 and had somebody from the FileMaker development team at the company restarting the server during the night.
24 hours after more than 250 users was connected. At 5 in the morning!
Instead of restarting again I selected all the users and disconnected them from the server.
They did not get disconnected as I would have expected, more than one hour after there was nearly 300 connected users (the people coming in for work adding to the list).
But then the miracle happened, at around 9 the number dropped to the actual number of connected users and the many ghost users disappeared.
I waited a week before setting the max. number down to 160.
It was the first time I experienced this problem and it seem to have gone away again. Knock under wood
FileMaker Server 14.0v2 (updating to v4 now*).
Windows Server 2012R2
Many processors, 64 GB ram, SSD server class disk for databases.
*Will upgrade to 15 during the summer, most important because of the performance improvements
Thanks for sharing your experience CarstenLevin. Sounds very much like my situation. Did you happen to notice remote calls in progress stack up? Were there any user complaints about database performance? While I didn't get complaints, I did see the wait times and elapsed times get up above 10 million microseconds.
Hi sgripman, the solutions on this server are very complex and demanding, but it is also a very powerfull server.
There was no problems with performance and the server statistics was OK.