x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 9 replies
  • Subscribers 240 subscribers
  • Views 3709 views
  • Users 0 members are here
Browse Forums
Sage 100 Contractor Announcements
119
topics
57
replies
Sage 100 Contractor General Discussion
1k
topics
4k
replies
Sage 300 CRE Announcements
168
topics
526
replies
Sage 300 CRE General Discussion
3k
topics
9k
replies
Sage Construction Management Announcements
4
topics
0
replies
Sage Construction Management General Discussion
17
topics
21
replies
Sage Estimating Announcements
39
topics
3
replies
Sage Estimating General Discussion
189
topics
448
replies
BradShoaf

Client connection problems after Sage server restarts

Posted By

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. 

  • 0 in reply to BarbTorrence

    Thanks for your reply, Barb.  Have you raised this issue with Sage Support before?  If so, did they provide any advice other than to restart the clients?

  • 0 in reply to BradShoaf

    No, I have not pursued with Sage. I presumed it was something wonky on our network/server that was causing the issue. Telling users to reboot at the end of every day or after the server is rebooted after hours is not going to cut it because you know they won't remember to do it. Until they can't get TL to run. Then they'll call me complaining that they can't get in. I don't remember having this problem before upgrading to 20.3.

Reply
  • 0 in reply to BradShoaf

    No, I have not pursued with Sage. I presumed it was something wonky on our network/server that was causing the issue. Telling users to reboot at the end of every day or after the server is rebooted after hours is not going to cut it because you know they won't remember to do it. Until they can't get TL to run. Then they'll call me complaining that they can't get in. I don't remember having this problem before upgrading to 20.3.

Children
No Data

*Community Hub is the new name for Sage City