Officemanager.dsb error on 1 PC out of 4

SOLVED

Hi,

I'm trying to help a client of mine troubleshoot an error 1 of their users is experiencing. They, and only they, started receiving "Sage Timeslips cannot load the navigator file OfficeManager.dsb" when trying to open their company. I did find this KB  about the error and tried option 2, with no luck. I haven't risked reinstalling anything on the server yet as is still an isolated case.

I am open to any advice people have to give Slight smile

Edit: I was looking around their file server and there's no Sage software installed on there at all. So the company/database files are in a fileshare that is mapped to each user's workstation. And each user has their own installation Sage Timeslips on their workstations. No recent updates or version upgrades that I know of.

Edit 2: They do have some *.dbs files in another folder from where the company files are, which is located on the same file server. However these files don't look like they've been modified since their install date in 2012. The folder is "Enhanced Navigator".

  • +1
    verified answer

    So, Office Manager.dsb is one of the Enhanced Navigators.  Most of them have not been changed since probably 2012.  I would copy the one from the server to the local hard drive of the pc having the problem.

    Or just choose a different Enhanced Navigator.

    Or turn off the Enhanced Navigators entirely and use a Basic Navigator (without any reports).

    Nancy Duhon, Esq.

    Duhon Technology Solutions, LLC

    Master Certified Consultant for Sage Timeslips

    Providing individual Consultations and Third Party Remote Desktop Support - including older/unsupported versions.

    404-325-9779

    [email protected]

  • 0 in reply to Nancy Duhon

    Hi Nancy,

    Thank you very much for your reply. Looking into the EN folder on the workstation and I found it empty. I copied over the files as found on the server and voila!.

    Thank you for your help. <3

  • 0 in reply to BryanV

    Excellent new BrianV and thanks for coming back to post what worked for you so that the next user with that issue can see the fix works!