Tracker Capture: Error in registration- Could not encrypt data, indicates a configuration issue

adolphe · 13 October 2016 14:36

Dear All,

Can anyone advise on how to go about this tracker issue?

We had a running TB patients tracking instance on 2.21 and we recently upgraded to dhis2.23. Here is how the system is set:
Web API:
Browse it here
Current user:
akamugunga
Version:
2.23
Build revision:
ec434ea
Build date:
2016-10-08 06:54
Jasper reports version:
6.1.0
User agent:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36
Server date:
2016-10-13 15:34
Last analytics table generation:
2016-10-13 00:00
Time since last analytics table generation:
15 h, 33 m, 42 s
Last analytics table runtime:
20 m, 39 s
Environment variable:
DHIS2_HOME
External configuration directory:
/var/lib/dhis2/individualrecords
File store provider:
filesystem
Database type:
PostgreSQL
Database name:
individualrecords
Database user:
individualrecords
Java opts:

Java version:
1.8.0_66
Java vendor:
Oracle Corporation
OS name:
Linux
OS architecture:
amd64
OS version:
3.13.0-40-generic
Server memory:
Mem Total in JVM: 3882 Free in JVM: 3377 Max Limit: 3882
CPU cores:
30

After upgrading, the aggregate side works fine we can use data sets and logo-banner image is displayed correctly, however in the tracker capture we can’t register a new patient (save and continue). The system pops up a registration error message “Could not encrypt data, indicates a configuration issue”.

Checking from web console i can’t figure out how to deal with the error.

Regards

···

On 13 October 2016 at 08:27, channara rin rin.channara@gmail.com wrote:

Dear all,
by the way, can i create ID code attribute that auto increase number by itself like auto generate ID code?

if not, can i do manual script to make auto generate ID code?

thank you

channara

Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

Adolphe Kamugunga
MIS Technical Advisor
Mobile: +250 788 740 578
Email:kaadol@gmail.com
Skype: ka.adolphe

RWANDA

Seleman_Ally · 13 October 2016 14:48

Hi Adolphe,

Sound more like tracked entity attribute issue to me. Looks like in version 2.21 one of your attribute was encrypted, And version 2.23 encryption procedure is different.

Use any procedure which is OK with you to open table called trackedentityattribute. Column (Attribute) Confidential will read False or true ( Change any true to false). It can solve your problem

Sele

···