Hello Bobby,

I came here to post a question about a similar issue.  Did you ever find the solution?  What we have found is that Estimating (18.12) will, at some point, start to run slowly via our Terminal Services offering.  When I say slowly I mean clicking from field to field will take 10-20 seconds to move and then it will sometimes catch up but then slow down again.  I noticed that clicking on the menu at top is not slow.

If we close other apps open via terminal services it speeds up again but will then slow down again when I open the apps back up.  Its not an issue with server speed or resources.  

Rebooting the database servers =does seem to alleviate the issue for a bit.

Hey Jeff,

I work with Bobby who posted the question a while back. This problem has always plagued us and it's always after we reboot our Remote App Server. The performance for domain admins is always normal but standard domain users, the system will just drag. It could take 2-4 minutes just to get the application to load (the loading splash screen will just lag while it runs through the loading process) and after that it takes a long time to load an estimate and everything lags. We've eventually found, at least for now, a minimum of 2 restarts in a row of the SQL server where the estimating DB is, will typically solve the problem (without restarting the Remote App Server). I wish I had a better answer, but like most things Sage there is no rhyme or reason to this problem.

Hi Daniel,

Thanks for the reply.  I had not called Sage on this case yet because we only have the silver plan and I am not sure they will have a fix for it so did not want to waste a call.  It may be environmental to Terminal/Citrix use.  I cannot say for sure if the problem happens only when I reboot our host terminal server as I just started looking into it.  One big difference between myself and your issue is that the slowness was mostly evident after Estimating opened.  It would take 10-20 seconds to respond to a single mouse click.  If you did a bunch of clicks in a row it would do them all after 10-20 seconds.  Did you see that same specific thing?  Also the slowness for me would go away if I shut other terminal server apps I had open (though those apps are hosted on another terminal server!) . But like you, at least for this week, the problem I myself saw went away after rebooting the server hosting the Estimating DB.  The last two days I kept Estimating open along with the other apps and each time I went back to Estimating it was fine.  If I find any other "clues" I will be sure to post them here.  Was hoping someone from Sage might also chime in as to whether they have seen this before.

Thanks

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?