Re: [Dhis2-devs] Meta Data Import Problem When upgrading from Version 2.13 to 2.20

Hi there. This does not seem to be related to the issue which you reported above. Is the startup hanging at a certain stage now? This can be notoriously difficult to diagnose. Can you turn on the postgresql logs and see at which stage the startup fails by looking for database errors in the logs

Re: [Dhis2-devs] Meta Data Import Problem When upgrading from Version 2.13 to 2.20

Hi there. It looks like you user may be restricted. Are you importing this with a superuser account? Can you check the database (in the organisationunit table) and see if any of the imported data is there? Regards, Jason On Fri, Aug 21, 2015 at 7:25 AM, Mihayo Mathayo wrote: > Hello Jason,

Re: [Dhis2-devs] Meta Data Import Problem When upgrading from Version 2.13 to 2.20

Hello Jason, I have done as you said,the org units were all imported but users' permission is denied and i can not see the imported org units on the organisation unit link menu even after running analytics. See the attached screenshots. Regards On Fri, Aug 21, 2015 at 7:17 AM, Jason Pickering <

Re: [Dhis2-devs] Meta Data Import Problem When upgrading from Version 2.13 to 2.20

Hi there. Have you tried to upgrade the 2.13 instance database first to 2.20,following all of the necessary documented upgrade steps, and then perform the export? There have been numerous model changes since then which will likely affect the import. Regards, Jason On Fri, Aug 21, 2015, 05:58 Mi

Re: [Dhis2-devs] Meta Data Import Problem When upgrading from Version 2.13 to 2.20

Hi, I checked the xml file every org unit has opening date ..but to my surprise during importation they are ignored. Am thinking of trying other versions like 2.18 or 2.15 but I cant find the download links.. On Aug 21, 2015 1:23 AM, "Juan Manuel Alcantara Acosta" < jmalcanta...@gmail.com> wrote:

Re: [Dhis2-devs] Meta Data Import Problem When upgrading from Version 2.13 to 2.20

Hi Mihayo A copy of the log would be useful to help you but based on the list of conflicts shown in the image you included, the ignored org units are missing the opening date, check your XML and add a valid date where it's missing, here's an example: http://dhis2.org/schema/dxf/2.0"; code="OU_2

[Dhis2-devs] Meta Data Import Problem When upgrading from Version 2.13 to 2.20

Hello Team, Am having a problem with upgrade of dhis2 instance from version 2.13 to 2.20.The issue am facing is on importing meta data where top level,level two and level three OrganizationUnits are ignored but the lowest level organizations units are imported into version 2.20. Attached screens