Client connection problems after Sage server restarts

We're experiencing an issue with users who are logged into Windows during a Sage server restart.  Whether the user has Sage 300 open or not, the Actian service begins using more CPU usage and the user is unable to connect to the Sage server until he restarts the desktop.

The Sage server is a dedicated member server and not a Domain Controller.  The user can see a network share on the server but cannot open Sage nor run TimberScan.exe which runs from the mentioned server share.

After restarting the PC, everything is fine.  Has anyone else seen this behavior?  If so, was there a fix other than forcing users to logoff at end of day?

Thanks for your input.

Parents
  • 0

    YES! I have this problem with multiple users EVERY TIME we reboot our dedicated server. Some times it takes multiple reboots of workstations before they will connect. I DREAD having to reboot the server for updates, because I know everyone will be calling me because they can't run Timberline or Timberscan. 

Reply
  • 0

    YES! I have this problem with multiple users EVERY TIME we reboot our dedicated server. Some times it takes multiple reboots of workstations before they will connect. I DREAD having to reboot the server for updates, because I know everyone will be calling me because they can't run Timberline or Timberscan. 

Children