Page 1 of 1
19.1 beta exception on AWS EC2 server
Posted: Fri Mar 22, 2019 1:20 pm
by wjstarck
Hello-
I am testing OD on a AWS EC2 instance of Windows Server 2016.
I have compiled the latest beta of 19.1 (19.1.
and it runs fine on my Windows 10 desktop. But, if I upload all the files and my db to the EC2 server, I get the following exception at runtime:
Code: Select all
Error Encountered - 03/22/2019 3:01:14 PM
Unhandled exception: ThemeSetByUser is an invalid pref name.
System.Exception
at OpenDentBusiness.Prefs.GetOne(String prefName) in C:\Users\wjs\Desktop\ODVersions\opendental19.1\opendental19.1\OpenDentBusiness\Data Interface\Prefs.cs:line 152
at OpenDentBusiness.Prefs.GetOne(PrefName prefName) in C:\Users\wjs\Desktop\ODVersions\opendental19.1\opendental19.1\OpenDentBusiness\Data Interface\Prefs.cs:line 145
at OpenDentBusiness.PrefC.GetBool(PrefName prefName) in C:\Users\wjs\Desktop\ODVersions\opendental19.1\opendental19.1\OpenDentBusiness\Cache\PrefC.cs:line 153
at OpenDentBusiness.UserOdPrefs.SetThemeForUserIfNeeded() in C:\Users\wjs\Desktop\ODVersions\opendental19.1\opendental19.1\OpenDentBusiness\Data Interface\UserOdPrefs.cs:line 339
at OpenDental.FormLogOn.butOK_Click(Object sender, EventArgs e) in C:\Users\wjs\Desktop\ODVersions\opendental19.1\opendental19.1\OpenDental\Forms\FormLogOn.cs:line 154
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at OpenDental.UI.Button.OnClick(EventArgs ea) in C:\Users\wjs\Desktop\ODVersions\opendental19.1\opendental19.1\OpenDental\UI\Button.cs:line 108
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
I was hoping you might have suggestions as to how to resolve it (I am accessing the server via RDP, and if I look at themes it does say that backgrounds are turned off by RDP)
Re: 19.1 beta exception on AWS EC2 server
Posted: Fri Mar 22, 2019 1:57 pm
by jsalmon
That error makes it sound like your database didn't quite finish the 19_1_1 script. Does your preference table contain rows for the following PrefNames? ThemeSetByUser, GlobalUpdateWriteOffLastClinicCompleted
Re: 19.1 beta exception on AWS EC2 server
Posted: Fri Mar 22, 2019 3:06 pm
by wjstarck
Yes, that's it thanks.
Re: 19.1 beta exception on AWS EC2 server
Posted: Fri Mar 22, 2019 3:11 pm
by wjstarck
One more question, on the same box:
I'm getting this when I try to send a NewCrop Rx. eConnector service is setup and running:
Code: Select all
A technical error has been automatically reported to your EMR/PM vendor. Contact them for more information. MSG 3 - Credentials: partner invalid or not authorized - MSG01
Original XML:
<?xml version="1.0"?>
<NCScript xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://secure.newcropaccounts.com/interfaceV7">
<Credentials>
<partnerName>OpenDentalLexi</partnerName>
<name>demo</name>
<password>demo</password>
<productName>OpenDental</productName>
<productVersion>19.1.8.0</productVersion>
[snip for HIPPAA]
</PatientCharacteristics>
</Patient>
</NCScript>
TIA
Re: 19.1 beta exception on AWS EC2 server
Posted: Fri Mar 22, 2019 5:00 pm
by jsalmon
Try building in Release mode? Looks like demo credentials were sent over.
Re: 19.1 beta exception on AWS EC2 server
Posted: Fri Mar 22, 2019 8:33 pm
by wjstarck
Yes that's it thank you.
Last one: I am having trouble get the eConnectorService running on this PC (it will install but won't start). Is that because I have it running on my production PC? This is my development machine (AWS EC2) that I am trying to get set up to move my production OD install over to.
I've tried opening AWS firewall ports 49997, 49999, 50000 and 50002 but the service still won't start. I've tried uninstalling the eConnector service on my production PC but it still won't work.
Re: 19.1 beta exception on AWS EC2 server
Posted: Mon Mar 25, 2019 8:28 am
by cmcgehee
You might need to set the "Update Server Name" to the name of the computer where your eConnector is running. This can be set in Setup -> Miscellaneous. If that isn't it, there should be a folder named "Logger" in the eConnector installation folder that should tell you why the eConnector isn't starting.
Re: 19.1 beta exception on AWS EC2 server
Posted: Mon Mar 25, 2019 10:40 am
by wjstarck
I had to manually install the EConnector service and change the servername in that dialog to my AWS instance servername from 'localhost'.
Working now, thanks.
Re: 19.1 beta exception on AWS EC2 server
Posted: Mon Mar 25, 2019 11:05 am
by wjstarck
Whelp, one step forward, two steps back.
I have the EConnector installed and running, but now when I try to write an eRx I get:
'Based on a period of inactivity, you have been automatically logged-out of your account. To resume prescribing, re-enter the website address. It is recommended that this address is added to your browser Favorites list'
I have ports 80 and 443 open on the AWS firewall, what website address is it referring to and how would I re-enter it?
Re: 19.1 beta exception on AWS EC2 server
Posted: Mon Mar 25, 2019 2:21 pm
by cmcgehee
Here's our internal documentation about what to do when you encounter this issue:
Solution 1: Close the eRx window and Open Dental. Clear the cache and cookies out of Internet Explorer. Re-open Open Dental and try eRx again.
Solution 2: Add NewCrop to the trusted sites in Internet Explorer. From Within Internet Explorer -> Settings "Gear icon in upper right" ->Security tab ->Trusted sites ->Sites ->Type: "secure.newcropaccounts.com" ->Add. Close IE and try eRx again.
Re: 19.1 beta exception on AWS EC2 server
Posted: Mon Mar 25, 2019 7:30 pm
by wjstarck
#2 did the trick, Chris. Thank you