Favorites Disappearing

Good Day Friends! 

I work for an MSP and we support the Sage products. A few of our clients are experiencing issues with the Favorites menu in the Sage client mysteriously disappearing every few months or so and we have to re-open the favorites file from the server to their client. Is anybody else having this issue? Every time i reach out to the user they wonder if there is a way to resolve this from happening and I am unaware. 

If you are able to provide insight it would be greatly appreciated! 

  • 0

    Yes, I am having the same problem... thought I was going crazy.  Unfortunately I do not have a solution.

  • 0

    Hi CogyG,

    If are using a desktop configuration file that is not either the default name (Default.dskx) or in the default location (C:\Users\<username<\AppData\Roaming\Sage\Common Desktop\Version 3.0\Configuration\Default.dskx)The path to the desktop configuration file is stored in the Windows Registry:

    Computer\HKEY_CURRENT_USER\Software\Timberline\Desktop

    Because the is a Current_User key, if another user logs in to the workstation, or the user gets a new workstation, the desktop configuration would revert to the default until it the modified configuration file is selected in Desktop settings. 

    It sounds like the customized configuration file path in the registry may be getting lost, either from renaming or deleting the Timberline or the Desktop registry key (for troubleshooting) or from reinstalling or updating Windows.

    I hope this helps the next time you run into this.

    Thanks!

  • 0 in reply to Jesse Gordon

    The configuration file has been renamed and is also placed on the network so multiple users are applying the file with for the favorites at the same time. My theory was; since the file is on the network, it might be getting lost when disconnecting from the office network. I wonder if i make a local copy of the file on all devices, would that stop the file from disappearing? For example place it under the path you gave me above. 

  • 0 in reply to CodyG

    I would think that would work, if nothing else it may narrow it down to an issue with a particular user or workstation.