Notifications
Clear all
General Discussion
6
Posts
4
Users
0
Reactions
97
Views
Topic starter
Hi there,
We upgraded our Test environment with the SP11 last Friday and ran into some problems.
During the installation, we were prompted to verify a publisher named - 7za.exe and we clicked "Ok" to that.
The file is located in C:\GEDeployment\InstallScripts\
The installation went on fine without any other problem.
Now the CPS doesn't run and the net browser shows the following massage.
HTTP Status 404 - /centricitytest/cps/
type status report
message /centricitytest/cps/
description The requested resource (/centricity/cps/) is not available
May I ask if anyone has seen this kind of error with the CPS SP11 and know how to fix it? Please let me know!
Thank
Posted : November 30, 2015 11:05 am
Simon, I am sorry you have encountered issues with your SP11 upgrade. Please contact Support at 888-436-8491 so they can assist you further.
Posted : December 1, 2015 12:23 pm
Hi Simon,
I see in another community that you were successful in your upgrade to SP11. Can you confirm that?
Posted : December 2, 2015 8:10 am
Topic starter
Hi John,
We were able to upgrade to the SP11 with a different copy of that.
Thanks
Simon
Posted : December 2, 2015 9:14 am
We encountered the same issue. It ended up being caused by specific files not being extracted from the zip file properly.
Ours was fixed by rebuilding the Staging Folder. (Be sure to rightclick and "Unblock" the zip file before extracting.)
-James
Posted : December 3, 2015 5:55 am
Is anyone experiencing the Drug interaction settings not working?
After further testing on SP11 I am finding that EVERY chart that has a prior Drug interaction of any severity, that does not already have a drug interaction override reason applied, will be locked in such a manner that the visit cannot be signed until the drug interactions have reasons applied.
I currently have ALL system and user prefference drug interaction override settings off.
I have found that if no drug interactions existed in the chart prior to the upgrade, users see no change unless they add a med during the visit that already resides on the allergy list, they are forced before signing to override this interaction, which is new as all settings for Drug interaction overrides are shut off.
Even if a user wanted to do a phone note in a chart that had a med on both the med and allegery list prior to the upgrade without a overrride reason, they cant even document text and sign without satifing the override reason for old interactions... Anyone seeing this?!? I have only tested in our Demo enviroment but interested in your feedback. (GE ticket filed, will update here if I get a resolution)
Posted : December 4, 2015 10:32 am
