In station administrator there is a time out setting. You can change it to no time out or to a time out it starts at midnight and ends at 5 AM, or something similar to that. That should help with the issue

That's the other thing... Station Administrator exe file cannot be found.  I haven't been able to locate it since the upgrade.  It's not on the server or the individual workstations.  Each user has an icon for it, but we get an error message that the file associated with it has been moved or deleted and would we like to remove the icon.  Did the file name change in the new version?

It’s called Tsadmin.exe in new versions. Try right click - run as administrator. You can also try to load it from within Timeslips by clicking on special. 

In addition to Caren's comment, I have noted times when users needed to close and re-open Timeslips and/or reboot workstation for the database timeout settig to change properlyn in the later versions.

your message/scenario doesnt sound like the typical TSAdmin DB Timeout message. if you had a DB time out set for 30 min, then everyone would be logged out with a pop up that says "Sage Timeslips DB Closed, Your Db has been closed due to inactivity" This action closed all dialogs in Timeslips leaving only that pop up. if someone has a MODAL window open such as a slip entry or data entry window in EDIT MODE then their system will not close until that dialog is handled or cancelled.
IF they had a slip open with a timer running and the slip was Saved with the timer running then the slip entry would close. if the slip timer was running and slip was not saved still in edit mode then the system would prompt to close and save the slip and perform a function based on the users preference settings and the general DB settings.

each user has their prefs for how to handle saving data entry windows so check their setup>preferences>interface>navigation rules>saving rules

the DB has a setting to over ride the user preference settings under setup>general>firm>other>close DB rules

if you are not getting that initial Db closed message then its possible you may have some other system in place on the workstations or servers that is disconnecting the DB engine connection or network drive connection between servers and workstations like a sleep feature that wakes up when it detects network activity again so check your server network connection settings or workstation hibernation/power saving settings.