Hi Carl,
There are a couple factors that contribute to making this very difficult to triage and this is what we have today:
- Less than 1/10 of 1 percent of practices are reporting this. We recognize some may not be reporting it.
- We believe it is limited to Windows 10, various builds. Only Win 10 users have reported it so far and we believe Win 10 is the predominant release everyone is running but we really have no visibility onto a clients OS release unless they tell us.
- Impacted users are on AC version 10. But then AC version 10 is the predominate version with over 90% of practices operating on this version.
- There were no programming changes made to the Write Scripts or Orders button/processing logic in version 10
- We have zero reports of this occurring in our hosted environments, all running Windows 2016 Server OS
- We cannot replicate this in house even using automation which simulates a users actions many thousands of times.
- Windows errors login is cryptic and can lead you down a rabbit hole as you note so it's of little help
- MS Support is of no assistance in this particular issue as we lack sufficient information to report.
- "Unhanded exception" errors are generic and of no help here other than to tell us there's some problem executing code. We do try to resolve them where we can but it's like diagnosing a patients problem when all you have to go by is they say " I don' t
feel well some days, others I feel fine."
- We have no explanation as to why 2 PC's with identical hardware in every respect yield different results . However we can't be 100% confident in the accuracy of that statement. If would be nice if someone on the board here could confirm with
absolute certainty.
- We have discovered some unique coding behind a few buttons in AC which include the Write Scripts and Orders buttons. This code has been in place for at least 6 years now. As MS makes OS changes it could expose incompatibility issues that were
not present previously.
Next steps:
- We've removed the unique coding behind the buttons in Version 11.1.
- We've also added extensive reporting to our error logs so when this occurs in the future we can narrow it down to a specific section of code to help us triage this more effectively. Today the error reports that the problem occurred somewhere in the state
of Texas. The new code hopefully will give us a street address, or at least a zip code.
- Version 11.1 will be available for beta next Monday and we're hoping that we can get a few practices experiencing this problem to accept beta to determine if we fixed the problem or at least get us more detailed logging. If you don't want to be an initial
beta site then maybe update after it's been in the field at other practices for a few weeks. Beta is expected to run at least 6 weeks and we plan to GA in April.
- We continue to investigate but honestly we've run out of options here until we can get more information with the new code in v11.1.
- If we can pin down the cause of the problem in beta then we can fix it in the GA release in April. If no one will take beta and we can't identify this until 11.1 is in GA then we have to do another release which will take more time.
I have attached a link to the 11.1 release notes here. These are beta and there will a few modifications but they're pretty close to final. If anyone is interested reply here or email me at cconrad@harriscomputer.com
V11.1 release notesBert...is there a way for me to enable HTML so my links are clickable?
