Page 1 of 1

query crash

Posted: Thu Apr 19, 2018 5:39 am
by brushoffice
When we click on "user query" on some of our computers, open dental crashes due to "System.ArgumentException." It only happens on our front desk computers. Open dental support looked at it but were unable to determine the problem. Anyone else having this problem? Any suggestions? We are using version 17.3.71.0.

Re: query crash

Posted: Thu Apr 19, 2018 7:52 am
by cmcgehee
Can you share the full text of the exception that you get when Open Dental crashes?

Re: query crash

Posted: Thu Apr 19, 2018 9:48 am
by brushoffice
Please see below. Thanks in advance!

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: OpenDental.exe
Problem Signature 02: 17.3.71.0
Problem Signature 03: 5abd78dc
Problem Signature 04: System.Drawing
Problem Signature 05: 4.7.2558.0
Problem Signature 06: 59d41483
Problem Signature 07: 5b3
Problem Signature 08: 6b
Problem Signature 09: System.ArgumentException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Re: query crash

Posted: Thu Apr 19, 2018 10:31 am
by JoeMontano
Sadly we can't use this to help identify where the issue is.
You should be getting a popup when OD crashes, we need the text from that textbox.

Re: query crash

Posted: Thu Apr 19, 2018 11:35 am
by brushoffice
The popup says:
Open Dental has stopped working
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.

Re: query crash

Posted: Thu Apr 19, 2018 12:17 pm
by cmcgehee
This error looks like the kind where hardware or the operating system is corrupted. Something that might fix this is having your IT reinstall the .NET framework.