Restored timeslips backup, licenses still showing in use, can not clear

So my client got hit with a ransomware virus which encrypted a good amount of their data.  Luckily I had taken a backup of the timeslips db just days before.  I copied what I could from the timeslips network folder and restored the backup but currently it is preventing them from logging in saying all the licenses are in use.  I go into the admin tool and see all their computers listed in the licenses.  I try clicking the clear all option but it says some users are still logged in when the aren't.  Is there a way to force clear these licenses so I can reassign them?  Currently only two users can log in out of 8, so that is seriously hampering their work.  Please advise.

Parents
  • 0

    What version of Timeslips? If a new version look for the stations folder in the Timeslips database and delete the contents.

  • 0 in reply to Caren2

    It is version 2012

  • 0 in reply to TLGChris

    So I did what you suggested and I was able to get more users logged in, but now some are getting an error "Cannot access directory".  All users log in with the same user account to the shared storage, so it can't be permission issues.

  • 0 in reply to TLGChris

    Clear temp files. Can you be more specific about all users login with the same user account to the shared storage?  Are you in a terminal services environment? Each user should have their own temp file.

  • 0 in reply to Caren2

    They have a shared drive on the network where timeslips was installed.  They all use the same user name to connect to the shared drive.  The temp files would be on their local machines then?  Where are the temp files for this program located?

  • 0 in reply to TLGChris

    My guess is that you also have lock files hanging around.

    Plan to reboot the device Timeslips and it's data is installed on at some point soon.

    The lock files can also be on local workstations and look like pdoxusrs.lck, etc.

  • 0 in reply to AllenH

    I've rebooted the server as well as removed the pdoxusrs.lck but it is still giving that error.

  • 0 in reply to TLGChris

    Have you gone to the windows task manager and checked to see if tstimer.exe is running? If it is, you need to clear that in task manager. Check on all machines to see if it is running and clear it.

  • 0 in reply to DCWilk

    Allen Hardon suggested this earlier, but from you response it did not appear that you had tried this. It does not involve Station Administrator. You have to use Windows Task Manager to find TSTimer.exe and close it.

  • 0 in reply to DCWilk

    I have copied the KB article on point to the error you report below.  Given you say this was ransomware virus and you did what you could to copy the server folder, even all those items may not help you.  You may need to reinstall from CD or download which means you will need your installation codes.  You can get them from help/about menu and then clicking on support info from a working computer.  Good Luck!

    ----------------------------------------------------------------------------------------------------------------------------------------------

    This error could indicate multiple situations and can be resolved through one or more of the following steps.

    An instance of Timeslips may still be running on this machine. Using the Windows Task Manager, look for a running instance of TIMESLIPS.EXE in the Processes tab. If found, click on it and then End Process and reopen Timeslips.

    Delete all Temp files on the computer (see Article 14091 - Deleting Windows and Timeslips temporary files) in related resources below.

    Locate and delete the PDOXUSRS.NET, PDOXUSRS.LCK, PARADOX.LCK files and FULSES* folders on the Timeslips server.

    Delete LOGIN.DB & LOCKS.DB from the database folder.

    Check that you have not lost the network connection to the server. This can be done by clicking on My Computer and browsing to the Timeslips directory on the server.

    Verify that you have Windows permissions of Full Control in the Timeslips directory. Usually you would not be able to delete the files in step number 2 if you don't have rights to the Timeslips directory on the server. A further way to check this is to browse to the Timeslips directory on the server, create, rename and delete a new folder.

    Reboot the server.

    Disable opportunistic locking on the workstations by running the Diagnose this Computer in the Timeslips Station Administrator tool and changing system settings.

  • 0 in reply to AllenH

    I tried deleting temp files as well as pdoxusers.* and the others from the KB article with no luck.  Then I saw TSscheduler running in processes, killed that and ran again and it worked.  Not sure if that was just luck or that fixed it.

  • 0 in reply to TLGChris

    Good to hear you got it working!

Reply Children
No Data