Home Forums Discussions General Discussion Upgraded to 7.0.12 yesterday morning and performance is crawling now?

We upgraded all systems to AC Certified 2014 yesterday morning and today in clinic, the interface is super draggy and slow to respond. Several fields have lost data when tabbing back and forth. Any idea what could be the cause of this performance hit? Any advice appreciated..

what was the previous version - 6.3.3 or earlier?

So you upgraded yourself, since it was on a Sunday, I presume. Has Angel Support weighed in? That is where I would start. By the way, I've started a Version 7 discussion thread. (New Version 7 Users Unite!) so that we early adopters can share experiences and ideas about the new version.

Actually, we did have Ryan, one of the Ac Support Techs, call in and step us through the upgrade process. We upgraded 12 systems starting with the Main Server first and then proceeded from room to room until all stations were upgraded.

Three systems failed the upgrade initially, but I think that was just a connectivity issue as opposed to something with the software installer itself. After all systems were upgraded, we picked back up the three failed ones and worked with those until the upgrade took. Mostly when machines fail (here at least) the issue is always due to systems attempting the upgrade process when the Windows OS was not fully updated itself. That has always been our thorn - making sure everybody stays up to date with just Windows itself. Thankfully, though, that process is not particularly difficult.

So, moral of the story is:
A. Come in at least an hour prior to your scheduled AC 7 upgrade call and update all systems.
B. Then back up all AC and Windows OS things (we already were doing this with AC's backup service anyway).
C. Then accept the AC Tech call and let them proceed with their upgrade routine.

Plus, AC Techs can simultaneously upgrade eight machines; you just have to log in to all eight to allow this. Once that happens, the bulk of your "fleet" can be upgraded pretty quick. We were averaging about 10-15 minutes per machine which is reasonable. And on Sunday you'll be in and out in about two hours. This is my third upgrade round and it was not that painful.

I am waiting on a response from AC Support as to why the interface is so draggy. My first guess would be a "database tuner" answer but I will continue to fill ya'll in on our experiences here. I do know that when AC first starts up, it sits there and loads up all the structural elements of its database first so your usage experience is supposed to be faster somehow. That would lead me to conclude that the more records you have the longer the load; that makes sense to me not being all that technical.

Anyway, good luck with your 7 upgrades. Our AC Tech Ryan was quick, good and knew exactly where to go and what to do.

thanks for the info

I have an update on our upgrade. Recall that we upgraded to AC Certified 2014 on 6.22.14. The responsiveness and performance of the AC interface was slow and draggy. After a server reboot yesterday afternoon, the interface is still slow. Any suggestions? It would seem that the responsiveness issue is tied to SQL services.

We resolved this issue on Friday. After speaking with AC Support, here is what we did:

First, we downgraded the .NET Framework that was running on our main server (that AC runs from) because AC Certified 2014 and servers don't necessarily play well with the different versions of the .NET Framework. I believe that we had the .NET 4.5 version and our server played better with the .NET 4 version instead of 4.5 for some reason.

I did not know this, but you can "hide" a component update like the .NET Framework so that the Windows Updater does not "see" it and consequently update it each time your automated system Updater does its thing - system wide. The AC Support Tech did this - he "hid" the .NET Framework so it artificially stays at version 4 in order to work with the server better. And you can "unhide" things just as easily. This was the solution that was implemented.

Second, after the .NET Framework version was artificially stuck at v4 from the server's end, we noticed that all our other hardwired computers could use AC normally; they suffered no drag to the interface EXCEPT the wireless laptop in one of our Exam rooms. The wifi connection on that laptop was found to have the only draggy experience when using the AC interface, so the solution was to simply hardwire via Ethernet the laptop. Once restarted, AC Certified 2014 worked just fine on the now hardwired laptop. So for now, we are simply leaving that laptop plugged into the wall and moving on. It's kind of a hacky solution, yeah, but the wifi here has always suffered and nobody can tell us why.

So it's fixed, all machines are running AC Cert 2014 as of Friday and so far we have experienced no further problems.

If any of ya'll field any slow, draggyniess with the AC 2014 interface itself, consider focusing on wifi connectivity, or the .NET Framework version running on your current server. It took us four days of troubleshooting and question asking to arrive here so maybe this is what you should try if anyone else has this similar issue with upgrading to AC Cert 2014.