date:20170716

Re: [Dhis2-users] OAuth token api status: 403 access denied.. urgent please!

2017-07-16 Thread Viet Nguyen

Hi guys,

I'm investigating this issue, will update you soon.

On Fri, Jul 14, 2017 at 9:42 PM, Jesus Solano-Roman <
asol...@broadinstitute.org> wrote:

> Hello Andrei.
>
> I believe we have the same issue, also not luck with the demo server. I
> had sent an email to the dev listserv but I think that's not an active
> group anymore. I'm copying my original email down here, perhaps someone can
> help us both. It's good to know we're not the only ones with the problem.
>
> ___
>
> *Hello all.*
>
> *I am following the guide posted here
> https://docs.dhis2.org/master/en/developer/html/dhis2_developer_manual_full.html#webapi
> 
> to obtain credentials to eventually create a web app.*
>
> *I created a client on DHIS2 (see attached image). I should note I am
> running the DHIS2 instance locally, therefore my server url is
> http://localhost:8085  (I cannot use https).*
>
> *Then on the terminal I run:*
>
> *curl -X POST -H "Accept: application/json" -u demokenema:$SECRET
> $SERVER/uaa/oauth/token -d grant_type=password -d username=admin -d
> password=district*
>
>
> *And I get*
>
> *{"error":"access_denied","error_description":"Access is denied"}*
>
>
> *I have attempted to solve this in many ways without luck. I eventually
> want to create HTTP requests in a JS application, but I can't even seem to
> get credentials using a curl request. Any help would be appreciated.*
>
>
> *Thanks!*
>
>
>
> *Antonio.*
>
> On Fri, Jul 14, 2017 at 10:15 AM, Andrei Evguenov 
> wrote:
>
>> Hi, we’ve been using DHIS2 2.6 in development phase (without updating
>> instance for the 2-3 months).  Upon deployment updated to the newest
>> release and having some headache with 403 access denied response when
>> trying to acquire token. At first I thought it was our server setup, but it
>> seems even dhis2.play.org/dev/uaa/oauth/token is giving the same
>> response, curl or postman.
>>
>> A couple of things to note: There is a correct response when client id
>> and or secret are missing or are incorrect. But if they are correct we
>> always getting 403 access denied, even if grant_type, password and or
>> username are missing (the body get’s completely ignored).
>>
>> I can provide you server setup details, but it seems the problem is
>> evident @ dhis2.play.org/dev/
>>
>> Older dhis.war we have works fine btw. If I was to have a stab in the
>> dark, I would aim for springframework.
>>
>> By the way api works fine with basic auth, can even POST, PATCH etc..
>>
>> Cheers,
>> Andrei @ Sustainable Solutions
>>
>> ___
>> 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
>>
>>
>
> ___
> 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
>
>


-- 

Viet Nguyen
Software Developer, DHIS 2
University of Oslo
http://www.dhis2.org
___
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

Re: [Dhis2-users] Database version - how to tell

2017-07-16 Thread Edward Robinson

An update on this, it turns out the encryption.password setting in the 
hibernate.properties file was overwritten with an incorrect value.  Fortunately 
someone on the team recalled what it was previously as the file had not been 
backed up along with the database.  That accounts for the 
org.jasypt.exceptions. EncryptionOperationNotPossibleException error.  I am now 
able to get the system up and access the UI.  Lesson, always backup 
hibernate.properties along with the database!
I am still getting some errors and warnings, they may be benign, but if anyone 
has insight into them, I would appreciate it greatly, particularly the errors:

* WARN  2017-07-16 19:05:27,445 [127.0.0.1]:5701 [dev] [3.2.1] No join method 
is enabled! Starting standalone. (HazelcastInstanceImpl.java 
[localhost-startStop-1])
* ERROR 2017-07-16 19:05:45,648 HHH000388: Unsuccessful: alter table 
programstage add constraint fk_programstage_dataentryform foreign key 
(dataentryformid) references dataentryform (SchemaUpdate.java 
[localhost-startStop-1])
* ERROR 2017-07-16 19:05:45,649 ERROR: constraint 
"fk_programstage_dataentryform" for relation "programstage" already exists 
(SchemaUpdate.java [localhost-startStop-1])
* WARN  2017-07-16 19:06:37,114 RP discovery / realm validation disabled;  
(RealmVerifier.java [localhost-startStop-1])
* WARN  2017-07-16 19:07:16,113 Did not find any ViewResolvers to delegate to; 
please configure them using the 'viewResolvers' property on the 
ContentNegotiatingViewResolver (ContentNegotiatingViewResolver.java 
[localhost-startStop-1])
* WARN  2017-07-16 19:07:26,335 Did not find any ViewResolvers to delegate to; 
please configure them using the 'viewResolvers' property on the 
ContentNegotiatingViewResolver (ContentNegotiatingViewResolver.java 
[localhost-startStop-1])
* WARN  2017-07-16 19:07:29,027 Ignoring action package with no actions: 
struts-default (DefaultModuleManager.java [http-bio-8080-exec-7])
* WARN  2017-07-16 19:07:29,028 Ignoring action package with no actions: 
spring-default (DefaultModuleManager.java [http-bio-8080-exec-7])
* WARN  2017-07-16 19:07:29,028 Ignoring action package with no actions: 
dhis-web-commons (DefaultModuleManager.java [http-bio-8080-exec-7])
* WARN  2017-07-16 19:07:29,030 Ignoring action package with no actions: 
dhis-web-ohie (DefaultModuleManager.java [http-bio-8080-exec-7])
* WARN  2017-07-16 19:07:29,030 Ignoring action package with no actions: 
dhis-web-portal (DefaultModuleManager.java [http-bio-8080-exec-7])

Cheers,
Ed
___
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

[Dhis2-users] Database version - how to tell

2017-07-16 Thread Edward Robinson

Hi all, is there a way to tell what version the database is?  I'm attempting to 
get an instance going that was running previously.  I was told it was 2.16.  
Tomcat is having trouble firing up using the 2.16 .war and I notice an error in 
the stdout log that seems to indicate the app wants to make changes to the DB 
structure which makes me suspect the DB is possibly not 2.16:

* ERROR 2017-07-16 16:55:02,744 HHH000388: Unsuccessful: alter table 
programstage add constraint fk_programstage_dataentryform foreign key 
(dataentryformid) references dataentryform (SchemaUpdate.java 
[localhost-startStop-1])
* ERROR 2017-07-16 16:55:02,746 ERROR: constraint 
"fk_programstage_dataentryform" for relation "programstage" already exists 
(SchemaUpdate.java [localhost-startStop-1])

I'm also getting these in the log:
* ERROR 2017-07-16 16:56:18,693 
org.jasypt.exceptions.EncryptionOperationNotPossibleException
   at 
org.jasypt.encryption.pbe.StandardPBEByteEncryptor.decrypt(StandardPBEByteEncryptor.java:1055)
   at 
org.jasypt.encryption.pbe.StandardPBEStringEncryptor.decrypt(StandardPBEStringEncryptor.java:725)
   at 
org.jasypt.encryption.pbe.PooledPBEStringEncryptor.decrypt(PooledPBEStringEncryptor.java:498)
   at 
org.jasypt.hibernate4.type.AbstractEncryptedAsStringType.nullSafeGet(AbstractEncryptedAsStringType.java:143)
   at org.hibernate.type.CustomType.nullSafeGet(CustomType.java:127)
   at org.hibernate.type.AbstractType.hydrate(AbstractType.java:106)
   at 
org.hibernate.persister.entity.AbstractEntityPersister.hydrate(AbstractEntityPersister.java:2903)
   at 
org.hibernate.loader.Loader.loadFromResultSet(Loader.java:1668)
   at 
org.hibernate.loader.Loader.instanceNotYetLoaded(Loader.java:1600)
   at org.hibernate.loader.Loader.getRow(Loader.java:1500)
   at 
org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:712)
   at org.hibernate.loader.Loader.processResultSet(Loader.java:940)
   at org.hibernate.loader.Loader.doQuery(Loader.java:910)
   at 
org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:341)
   at org.hibernate.loader.Loader.doList(Loader.java:2516)
   at 
org.hibernate.loader.Loader.listUsingQueryCache(Loader.java:2361)
   at org.hibernate.loader.Loader.list(Loader.java:2324)
   at 
org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:490)
   at 
org.hibernate.hql.internal.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:355)
   at 
org.hibernate.engine.query.spi.HQLQueryPlan.performList(HQLQueryPlan.java:195)
   at org.hibernate.internal.SessionImpl.list(SessionImpl.java:1268)
   at org.hibernate.internal.QueryImpl.list(QueryImpl.java:101)
   at 
org.hisp.dhis.hibernate.HibernateGenericStore.getAll(HibernateGenericStore.java:345)
   at 
org.hisp.dhis.configuration.DefaultConfigurationService.getConfiguration(DefaultConfigurationService.java:70)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown 
Source)
   at java.lang.reflect.Method.invoke(Unknown Source)
   at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
   at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
   at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
   at 
org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:96)
   at 
org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:260)
   at 
org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:94)
   at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
   at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
   at com.sun.proxy.$Proxy30.getConfiguration(Unknown Source)
   at 
org.hisp.dhis.startup.ConfigurationPopulator.execute(ConfigurationPopulator.java:48)
   at 
org.hisp.dhis.system.startup.DefaultStartupRoutineExecutor.execute(DefaultStartupRoutineExecutor.java:115)
   at 
org.hisp.dhis.system.startup.DefaultStartupRoutineExecutor.execute(DefaultStartupRoutineExecutor.java:85)
   at

Re: [Dhis2-users] Upgrading from 2.16

2017-07-16 Thread Bob Jolliffe

Regarding version you should be aiming for, you should always aim to
be not more than 3 versions back from latest release.  As security
issues arise and get addressed they are usually backported as far as
is practical.  But the developers only guarantee security support for
the last 3 versions.

On 16 July 2017 at 21:38, Edward Robinson  wrote:
> Some excellent tips, thank you Elmarie.
>
> Regards
>
> Ed
>
>
>
> From: Elmarie Claasen [mailto:elma...@hisp.org]
> Sent: Sunday, 16 July 2017 3:00 PM
> To: Edward Robinson 
> Cc: DHIS 2 Users list 
> Subject: Re: [Dhis2-users] Upgrading from 2.16
>
>
>
> Hi Edward,
>
>
>
> Wow this is quite far back. We upgrading some instances from 2.20 now and
> everything is going fine, provided that you drop SQL views before the
> upgrade. SQL views often hold table updates effected through war upgrades.
> From 2.23 to 2.23 you need to read about changes required to sms config if
> used.
>
>
>
> Read the upgrade documentation for each version, some has scripts which you
> must run, others execute an upgrade routine with first startup of the war
> file.
>
>
>
> We have find issues when not upgrading incrementally and also starting up
> the server after each upgrade, so this is recommended. You may find it
> difficult to find the link to older war files but check the URL for download
> of newer versions and just change the version number in the war accordingly.
>
>
>
> I would take care if any of the implementations are tracker because tracker
> got a major overhaul since then including changes in tables. You will find
> apps like individual records etc chenging to tracker and event capture.
>
>
>
> Through learning some hard lessons we usually upgrade on a test instance
> first and test all existing functionality properly. Also had some issues
> with table or column updates so we download a Sierra Leone database of the
> same version and compare the tables and columns in that instance vs ours
> with a SQL view.
>
>
>
> Good luck
>
>
>
> Elmarie
>
>
>
> On 16 Jul 2017 20:10, "Edward Robinson" 
> wrote:
>
> I have a couple of 2.16 installations that should probably be brought up to
> date.
>
> What are the major caveats I should be looking out for and what is the
> latest stable DHIS2 version that I should be aiming for?  It’s critical that
> service be maintained for the client, I will run the upgrades on another box
> and validate them before updating live but I wondered if anyone had anything
> specific that comes to mind that I should look out for or be aware prior to
> upgrading.  Do I need to upgrade incrementally?
>
>
>
> Thanks in advance!
>
>
> ___
> 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
>
>
>
> This message and any attachments are subject to a disclaimer published at
> http://www.hisp.org/policies.html#comms_disclaimer.  Please read the
> disclaimer before opening any attachment or taking any other action in terms
> of this electronic transmission.  If you cannot access the disclaimer,
> kindly send an email to disclai...@hisp.org and a copy will be provided to
> you. By replying to this e-mail or opening any attachment you agree to be
> bound by the provisions of the disclaimer.
>
>
> ___
> 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
>

___
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

Re: [Dhis2-users] Major speed issue with pg_restore

2017-07-16 Thread Edward Robinson

Hi Bob, apologies, it’s running on this hardware:
http://www.dell.com/support/home/ht/en/htbsdt1/product-support/servicetag/d2fvfx1/configuration
A bit dated, but definitely not a hardware error given the speedy / successful 
restore on Windows.
Regards
Ed

From: Bob Jolliffe [mailto:bobjolli...@gmail.com]
Sent: Saturday, 15 July 2017 3:02 PM
To: Edward Robinson 
Cc: Knut Staring ; dhis2-users 
; Hannan Khan 
Subject: RE: [Dhis2-users] Major speed issue with pg_restore

Ed you never answered my earlier question about the hardware you were running 
on?

On 15 Jul 2017 6:40 p.m., "Edward Robinson" 
> wrote:
Sorry for this slow response, time has not been on my side 
Also, thanks Bob, Knut and Hannan for your responses.

So to fill everyone in, I went through postgres.conf with a fine toothed comb.  
@ Bob, Shared buffers were set to 3200 though I'd set them to 1600 for the 
restore as per this article's suggestions:
http://www.databasesoup.com/2014/09/settings-for-fast-pgrestore.html
Overall I'm convinced the PGSQL environment had nothing to do with the issue... 
what I had suspect is that the combination of Ubuntu 16.04 and our hardware was 
not a good match.  I suspect the SATA channel in particular was the bottleneck.
To prove a point (I have two identical machines), I loaded Win Server 2012 R2 
and and installed PGSQL 9.5.5 on the box and, without so much as tweaking a 
single file, I restored the dump within 50 minutes.  We're likely upgrading the 
platform soon so I'm not going to break my back troubleshooting what is likely 
an issue that won't be there in 6 months time.  Dell didn't include Debian or 
Ubuntu on their list of supported OS for the hardware combination, though I 
have no reason to believe it couldn't work with a little effort and a bit of 
old school compiling, I just don't have the luxury of time to fiddle.  It 
worked well with 12.04 out of the box.
I just thought I'd post this in case anyone else was having similar trouble - 
if you've double checked the configs, it's quite possibly a lower level issue.
Cheers!
Ed
___
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

Re: [Dhis2-users] Upgrading from 2.16

2017-07-16 Thread Edward Robinson

Some excellent tips, thank you Elmarie.
Regards
Ed

From: Elmarie Claasen [mailto:elma...@hisp.org]
Sent: Sunday, 16 July 2017 3:00 PM
To: Edward Robinson 
Cc: DHIS 2 Users list 
Subject: Re: [Dhis2-users] Upgrading from 2.16

Hi Edward,

Wow this is quite far back. We upgrading some instances from 2.20 now and 
everything is going fine, provided that you drop SQL views before the upgrade. 
SQL views often hold table updates effected through war upgrades. From 2.23 to 
2.23 you need to read about changes required to sms config if used.

Read the upgrade documentation for each version, some has scripts which you 
must run, others execute an upgrade routine with first startup of the war file.

We have find issues when not upgrading incrementally and also starting up the 
server after each upgrade, so this is recommended. You may find it difficult to 
find the link to older war files but check the URL for download of newer 
versions and just change the version number in the war accordingly.

I would take care if any of the implementations are tracker because tracker got 
a major overhaul since then including changes in tables. You will find apps 
like individual records etc chenging to tracker and event capture.

Through learning some hard lessons we usually upgrade on a test instance first 
and test all existing functionality properly. Also had some issues with table 
or column updates so we download a Sierra Leone database of the same version 
and compare the tables and columns in that instance vs ours with a SQL view.

Good luck

Elmarie

On 16 Jul 2017 20:10, "Edward Robinson" 
> wrote:
I have a couple of 2.16 installations that should probably be brought up to 
date.
What are the major caveats I should be looking out for and what is the latest 
stable DHIS2 version that I should be aiming for?  It’s critical that service 
be maintained for the client, I will run the upgrades on another box and 
validate them before updating live but I wondered if anyone had anything 
specific that comes to mind that I should look out for or be aware prior to 
upgrading.  Do I need to upgrade incrementally?

Thanks in advance!

___
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

This message and any attachments are subject to a disclaimer published at 
http://www.hisp.org/policies.html#comms_disclaimer.  Please read the disclaimer 
before opening any attachment or taking any other action in terms of this 
electronic transmission.  If you cannot access the disclaimer, kindly send an 
email to disclai...@hisp.org and a copy will be 
provided to you. By replying to this e-mail or opening any attachment you agree 
to be bound by the provisions of the disclaimer.
___
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

Re: [Dhis2-users] Upgrading from 2.16

2017-07-16 Thread Elmarie Claasen

Hi Edward,

Wow this is quite far back. We upgrading some instances from 2.20 now and
everything is going fine, provided that you drop SQL views before the
upgrade. SQL views often hold table updates effected through war upgrades.
>From 2.23 to 2.23 you need to read about changes required to sms config if
used.

Read the upgrade documentation for each version, some has scripts which you
must run, others execute an upgrade routine with first startup of the war
file.

We have find issues when not upgrading incrementally and also starting up
the server after each upgrade, so this is recommended. You may find it
difficult to find the link to older war files but check the URL for
download of newer versions and just change the version number in the war
accordingly.

I would take care if any of the implementations are tracker because tracker
got a major overhaul since then including changes in tables. You will find
apps like individual records etc chenging to tracker and event capture.

Through learning some hard lessons we usually upgrade on a test instance
first and test all existing functionality properly. Also had some issues
with table or column updates so we download a Sierra Leone database of the
same version and compare the tables and columns in that instance vs ours
with a SQL view.

Good luck

Elmarie

On 16 Jul 2017 20:10, "Edward Robinson" 
wrote:

> I have a couple of 2.16 installations that should probably be brought up
> to date.
>
> What are the major caveats I should be looking out for and what is the
> latest stable DHIS2 version that I should be aiming for?  It’s critical
> that service be maintained for the client, I will run the upgrades on
> another box and validate them before updating live but I wondered if anyone
> had anything specific that comes to mind that I should look out for or be
> aware prior to upgrading.  Do I need to upgrade incrementally?
>
>
>
> Thanks in advance!
>
> ___
> 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
>
>

-- 

*This message and any attachments are subject to a disclaimer published at 
http://www.hisp.org/policies.html#comms_disclaimer 
.  Please read the 
disclaimer before opening any attachment or taking any other action in 
terms of this electronic transmission.  If you cannot access the 
disclaimer, kindly send an email to disclai...@hisp.org 
 and a copy will be provided to you. By replying to 
this e-mail or opening any attachment you agree to be bound by the 
provisions of the disclaimer.*
___
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

[Dhis2-users] Upgrading from 2.16

2017-07-16 Thread Edward Robinson

I have a couple of 2.16 installations that should probably be brought up to 
date.
What are the major caveats I should be looking out for and what is the latest 
stable DHIS2 version that I should be aiming for?  It's critical that service 
be maintained for the client, I will run the upgrades on another box and 
validate them before updating live but I wondered if anyone had anything 
specific that comes to mind that I should look out for or be aware prior to 
upgrading.  Do I need to upgrade incrementally?

Thanks in advance!
___
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

Re: [Dhis2-users] android tracker capture syncing error: 'an event already exists'

2017-07-16 Thread Ignacio Foche

Hi Brian,

I think it may be related to this API issue
. Could you create a new Jira
issue

explaining how to replicate it through play.dhis2.org servers when
possible? Please use the "Maintenance of Android App" project and component
"Tracker Capture". Once we will study your case we will be able to propose
you a strategy to avoid that blocking situation.

Best regards.

Ignacio Foche



Le sam. 15 juil. 2017 à 13:48, Brian O'Donnell  a
écrit :

> Hi experts,
>
> Has anyone experienced errors syncing offline data capture with Android
> Tracker on v2.25?
>
> The following error message displays when trying to sync event data via
> wifi:
> *"program stage is not repeatable and an event already exists"*
>
> It is very similar to this issue on V2.26
> , yet it occurs
> even with a single (nonrepeatable) stage program. On investigation, the
> error sometimes shows up when mobile data have been successfully submitted
> to the server and can be viewed on the web, but the error message persists
> on mobile.
>
> Our assumption is this occurs due to poor network, since we also received
> errors that "you have run out of auto-generated UIDs" when trying to enroll
> new TEIs, and "tracked entity does not exist" when syncing new enrollments.
>
> My biggest question: what is the best strategy to sync data if these
> errors persist? Our users may enroll ~100 new TEIs at a time before going
> back online, so logging out and back in is not an option as this wipes
> their local data. Is there another way to remove the error, and ensure data
> are synced to server?
>
> Details:
> v2.25
> build 9b2e099
> occurs on both app v0.3.39 and app v0.3.34
> non-repeating single stage and multiple stage programs
> "Pre-generate event UID" is not ticked
> occurs on multiple user roles, devices, and networks
>
>
> Brian
> --
> [image: Akros]  Brian O'Donnell, MPAff
> Informatics Project Manager
> bodonn...@akros.com
> ___
> 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
>
___
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

Re: [Dhis2-users] OAuth token api status: 403 access denied.. urgent please!

Re: [Dhis2-users] Database version - how to tell

[Dhis2-users] Database version - how to tell

Re: [Dhis2-users] Upgrading from 2.16

Re: [Dhis2-users] Major speed issue with pg_restore

Re: [Dhis2-users] Upgrading from 2.16

Re: [Dhis2-users] Upgrading from 2.16

[Dhis2-users] Upgrading from 2.16

Re: [Dhis2-users] android tracker capture syncing error: 'an event already exists'

9 matches

Site Navigation

Mail list logo

Footer information