It means the sessions are hung. Server thinks they're still connected. As an immediate fix, restart the Server process.
For a more permanent fix, you can try to educate your users about leaving themselves logged in (depending on their level of tech savvy). Another method is provided here:
It basically involves using an OnTimer script to force a record commit. The hung sessions are usually less severe (it's easier to kick the client off) if there are no open records.
Thanks for the link and the additional info.
The end users could be logged into for 5 or 10 minutes and generate 5 logins that are stuck. They aren't logging out, they're trying to use FileMaker Go 14 on their iPad's or iPhones... the only thing they notice is FileMaker is a little slow. But during that 10 minute session FileMaker Go will hang for a minute or two and then start working again. That's all they notice. What I see on the server console is them logging in, not logging out, but then logging in again and again. They see no error message except after some time, they get the error that they are already editing the record.
Do you still think it's an education thing or maybe how we have the database configured?
It sounds like a wonky network connection. If the users aren't putting their devices to sleep with records open, but you're seeing hung sessions, it could be that the connections are being dropped but Server can't disconnect them because the device is inaccessible.
Do you have any messages about connections being terminated in the log?
No messages in the log because they're connections are not being terminated. They can turn off the device, go home, and come back the next day and when they turn the device back on and launch FileMaker Go, sometimes it will reconnect with the login from yesterday but sometimes it will create a new login.
But, we haven't narrowed it down to the iPad's going to sleep, and we haven't even narrowed the problem to a particular OS. It seems to happen more often to an iPad running the latest version of Go. But it can happen to Windows machines, the least, iPads the most but Wi-Fi being used is the common denominator.
We've resorted to restarting FileMaker Server twice a day now to help alleviate the problem of locked records. We have approximately 40 users and they aren't happy.
When you say, "Create a new login," does that mean you're running some kind of session model (creating a record in a sessions table), or does that mean in the log?
Again, it sounds like a network issue. What kind of network setup is this? Have you had anyone on your network team run any kind of network diagnostics? That's what needs to be run to ground, because simply restarting the server is not a good idea. You'll eventually damage your databases doing that.
Looking in the admin console... multiple logins show under the activity tab.
We had pretty much exactly the same behavior you're describing a couple of weeks ago. Turns out a Windows patch munged up one of the DNS servers, which was periodically scrambling the communication to the FileMaker servers. When that happened, people's connections were hung. Took about a day to isolate, but until the server group did, pretty much nothing worked.
Again, it sounds like to me you have an infrastructure issue. Could be server-related or directly tied to your network. But that needs to be ferreted out and fixed. Otherwise, you're risking your databases by just continuously restarting the server with hung sessions (especially if records are open).
Wow! Mike, you are awesome. We just demoted this server from being a domain controller. Well, not just... but two months ago. You've definitely given me something to look into. Thanks!
It's hard to say what was the ultimate solution to this. Mike was right that we had a misconfigured, yet unused DNS server service running on the server that hosted FileMaker Server. However, I also patched the server with version 14.03 at the same time. Either way, it appears my problem is solved.