Database location "forgotten" - TS 2016, Win 10

SUGGESTED

Upgraded some of my workstations to Win10.  Now when I launch Station Administrator, it says it can't find Timeslips.cfg.  I go ahead and set the location of the file, andd I can then function.  But when I close and re-open, it "forgets" the location again.

Having a similar problem when I launch the program from some of the workstations.  Others will remember.

Did Data Verification repair, cleared all the licenses, and this still occurs.

Any ideas on what is doing this and how to fix?

  • 0

    Sounds like you probably don't have enough permissions as the logged in to the computer user to make the change. You might try launching Station Administrator by right clicking on it and choose run as admin. See if that makes the change stick. 

  • 0
    SUGGESTED

    This actually is a Windows issue on those workstations, and not a Timeslips issue.

    The Windows Registry contains the location for the CFG file.  When Timeslips launches, it pulls that key (if it exists) and reads where the location of the CFG was the last time it was updated. 

    Since it is a key located in HKEY_Current_User, if you are using a different Windows Profile, it will be blank when you launch Timeslips, and will prompt to locate the file. 

    If the path is invalid, such as might be the case with a mapped drive being disconnected, or not having been mapped in another Windows profile,  or if the CFG file is not located there having been moved or deleted, you will get this error. HINT: Use a UNC path to the CFG - those problems are resolved.

    If you don't have rights to update the registry, the path will be blank next time you launch the program and cycle back through this issue.  I've seen some of these high performance  Security applications put the registry back in it's current state, also causing such behavior.

    The key in the registry for Timeslips 2016 is -- HKEY_CURRENT_USER\Software\Sage\Timeslips\v24BDE\General -and is the Installation Path parameter.  In your case, as a multi-license install, it is best entered as something like Installation Path =\\Server\Apps\Timeslips\ - of course making this match your server machine name, share name, and location. 

    Running, installing or generally using the 'Run as Administrator' function can be, and usually is, problematic.  It should only be used as a temporary fix, and never as a permanent solution.