x Want to participate? Join the group to interact
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 4 replies
  • Subscribers 67 subscribers
  • Views 2347 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
8k
replies
Sage Construction Management Announcements
4
topics
0
replies
Sage Construction Management General Discussion
15
topics
20
replies
Sage Estimating Announcements
39
topics
3
replies
Sage Estimating General Discussion
189
topics
442
replies
BobbyS

Estimating extremely slow after reboot of terminal server for windows non admin user

SOLVED
Posted By

Hello all!  We are having an issue where Estimating on a remote app "terminal services" after reboot of the terminal server runs extremely slow for windows non admin users.  This has happened before and a combination of rebooting the database server and app server  eventually resolves the issue. However, this time it is NOT.  

 

We have intermittently had this issue since version 17.1.  We are currently 18.11.  Any help would be appreciated

Parents
  • +1
    verified answer

    We might of had a revelation today with our specific case. 

    In our environment we have multiple domain controllers. For simplicity we'll say DC1 and DC2.

    Today I restarted DC1 to do some updates. This normally shouldn't matter, because that's what DC2 is for. As soon as DC1 restarted, Sage Estimating began running extremely slow on the Remote App Server. A restart of the Sage Estimating Database server made no difference, neither did a second restart. 

    On the Sage Estimating Database server I opened a command prompt and ran nltest /dsgetdc:DOMAIN NAME and it returned the Sage Estimating Server was authenticating against DC2, which again, shouldn't matter. I then ran nltest /Server:SAGEDBSERVERNAME /SC_RESET:DOMAINNAME\DOMAINCONTROLLERNAME to reset it back to DC1.

    Instantly Sage Estimating performance was back to normal!

    I currently don't know why the Sage Database server authenticating to a secondary DC would cause this problem. I will attempt to replicate this problem in our environment after hours, maybe it's a fluke?

Reply
  • +1
    verified answer

    We might of had a revelation today with our specific case. 

    In our environment we have multiple domain controllers. For simplicity we'll say DC1 and DC2.

    Today I restarted DC1 to do some updates. This normally shouldn't matter, because that's what DC2 is for. As soon as DC1 restarted, Sage Estimating began running extremely slow on the Remote App Server. A restart of the Sage Estimating Database server made no difference, neither did a second restart. 

    On the Sage Estimating Database server I opened a command prompt and ran nltest /dsgetdc:DOMAIN NAME and it returned the Sage Estimating Server was authenticating against DC2, which again, shouldn't matter. I then ran nltest /Server:SAGEDBSERVERNAME /SC_RESET:DOMAINNAME\DOMAINCONTROLLERNAME to reset it back to DC1.

    Instantly Sage Estimating performance was back to normal!

    I currently don't know why the Sage Database server authenticating to a secondary DC would cause this problem. I will attempt to replicate this problem in our environment after hours, maybe it's a fluke?

Children
No Data

*Community Hub is the new name for Sage City