Failed to set a named property on 'Storage': Setting the value of '' exceeded the quota

Hi Team,
I am trying to load the data entry module and I get the following console error and the module doesn’t load all for some users

*‘Failed to set a named property on ‘Storage’: Setting the value of ‘’ exceeded the quota’

The module works on lower levels

Hello, @omunyao welcome back to the CoP! To start with, I would like to ask you to post what version of DHIS2 are you using? Additionally, the version of Tomcat and Java?

Thank you!

Dear @Gassim ,

I also facing this issue and i am using DHIS2 version-2.30 java 1.8 and tomcat - 9.0.53 and postgres 10

Uncaught DOMException: Failed to set a named property on ‘Storage’: Setting the value of ‘’ exceeded the quota.
at Object.success (
at i (
at Object.fireWith [as resolveWith] (
at A (
at XMLHttpRequest. (

Please suggest

Thanks and Regards

Mithilesh Kumar Thakur

Hi @Mithilesh_Kumar_Thak,

Before we try to get into the logs and configurations, since you are using java 8 then I’d recommend you update to Java 11. For its importance please see the instructions from @bobj in this qoute (from another topic). After that if you still see the same issue then please post the log (without sensitive info):

We just came across the same problem today (DHIS 2.36.6).

Apparently, it’s related to the 5MB localStorage per-domain limit set by browsers. Firefox has a configurable setting ( to customize that limit - once increased, the error goes away. Chrome does not have a configurable setting, AFAIK.

The data being stored is the response of /dhis-web-dataentry/getMetaData.action, which grows with the number of data sets.

The DHIS2 team could provide a better solution for this, but, as a mitigation measure, try to reduce the number of data sets that the user has access to.

1 Like

If the war file is 2.30 you can’t use java-11, you can only use java-8 but if the war file is 2.32 then java-11 works fine

1 Like

Good to know! Thanks! (:

To clarify, this has nothing to do with Java nor the backend, so changing Java versions or heap space won’t have an impact. This is related to how much data you can store in the local store of the web browser.

When loading data entry module, DHIS 2 will load a lot of metadata over to the browser for offline functionality purposes, in particular if you have many org units and many heavy data set forms.

A work-around is to to go to Apps > Maintenance > Org unit levels, and for the higher levels (Global, National, Province) set the max number of org units levels to something like 2. This will make sure only org units for the given number of levels relative to the user org unit will be loaded.




Made me think it had to do with the heap space :sweat_smile: Thank you for the clarification @Lars! :+1: