Notifications
Clear all
Topic starter
We installed SP13 on Saturday. Yesterday went smoothly, but today each has had several crashes at random times. We have never experienced anything like this before, and we have been on Centricity since 2004. The only change that we can think of between yesterday and today is that Oracle restarted overnight for backup. GE is on the case, but has no ideas yet.
Posted : November 22, 2016 5:09 am
By crashes do you mean at individual workstations or I am assuming at the server level? What do you do to restore operations?
We are looking to upgrade to SP13 in a couple weeks.....
Posted : November 22, 2016 5:51 am
Topic starter
I am talking about individual PCs. Users are able to log right back in, but it is still very inconvenient.
Posted : November 22, 2016 5:57 am
Am considering SP13 and would really like to hear more about any issues.
What SP did you come from when upgrading to SP13?
We are currently on 9.8.11.
Thanks, Jill
Posted : November 22, 2016 9:03 am
Topic starter
The only other problem is that clicking on the Patient Education button generates numerous script errors. We came from 9.8.6, which was working fine for us, but we were forced to upgrade for Meaningful Use purposes. We had been hoping to hold off any upgrades until there were some actual new features we could use (such as in 9.10), but our MU numbers were clearly wrong in some categories.
Posted : November 22, 2016 9:16 am
Topic starter
This morning it was not possible to log into the EMR at all. Since I suspected that yesterday's problems were related to JBoss, I decided to restart JBoss on the application server. (Java now uses only 220MB of RAM vs. 8GB pre-SP13.) JBoss would not restart, with server.log reporting "account is locked." What account? It did not say, but I suspected that it was the CWS account since that is what is used when running the Server Configurator. I used the Oracle SQL command "alter user CWS account unlock" and tried again. Same result--"account is locked." At that point I tried GE after-hours support. After an hour of struggles, it turned out that the solution was to unlock the CWS account, then use Server Configurator to reset the CWS password to the same thing that I set it to on Saturday. Why was all of this necessary? That's a question that I hope GE can answer today.
And it continues to baffle me as to why it is necessary for the evil JBoss server to be running for someone to be able to log into the EMR. Without the JBoss server's peripheral functions, it would still be possible to read documents, view attachments, view appointments, etc. The presence of a server that even most people at GE do not understand should not be required for login. Up until EMR 9.8, the application server could even be turned off and users could still log in.
Posted : November 23, 2016 2:18 am
Topic starter
It turned out that our crashing problems were due to a former JBoss server that was repurposed in 2014. This machine still had JBoss running on it, which had not been a problem until JBoss's CWS user password had to be changed because of the new Server Configurator installation process. No one remembered that there was a CWS user or what its password might be, so the password had been unchanged since the user's creation in 2008.
The old JBoss server kept trying to connect to Oracle using the old password, and eventually the CWS account would become locked, and trouble would begin. Once JBoss was uninstalled from the old server, the only remaining problem is that the Patient Education button does not work for some users.
Posted : November 30, 2016 2:17 am
