Data entry APP error:RangeError: Invalid time zone specified: GMT+08:00

when I open 2.40 's dhis-web-aggregate-data-entry data entry app,got this error:

RangeError: Invalid time zone specified: GMT+08:00
RangeError: Invalid time zone specified: GMT+08:00

Using the Data Administration app in Maintenance, please select Clear application cache and reload apps. After that is cleared, open the app again using your browser’s Guest mode. If the issue doesn’t happen again then please clear your cache.

If the issue happens again in Guest mode please take a screenshot of the Network tab in your DevTools F12, and we might need to request the Catalina.out log (without sensitive info)

Thanks!

I have done work as you said, still got this error,no info in Catalina.out

RangeError: Invalid time zone specified: GMT+08:00
RangeError: Invalid time zone specified: GMT+08:00
at Date.toLocaleString ()
at http://100.64.0.1:10009/dhis-web-aggregate-data-entry/static/js/app.47d2c000.chunk.js:1:8397
at Object.useMemo (http://100.64.0.1:10009/dhis-web-aggregate-data-entry/static/js/main.5b22e0fa.js:2:285781)
at t.useMemo (http://100.64.0.1:10009/dhis-web-aggregate-data-entry/static/js/main.5b22e0fa.js:2:389061)
at http://100.64.0.1:10009/dhis-web-aggregate-data-entry/static/js/app.47d2c000.chunk.js:1:8373
at ye (http://100.64.0.1:10009/dhis-web-aggregate-data-entry/static/js/app.47d2c000.chunk.js:1:8483)
at http://100.64.0.1:10009/dhis-web-aggregate-data-entry/static/js/app.47d2c000.chunk.js:1:11595
at Ce (http://100.64.0.1:10009/dhis-web-aggregate-data-entry/static/js/app.47d2c000.chunk.js:1:11789)
at sr (http://100.64.0.1:10009/dhis-web-aggregate-data-entry/static/js/app.47d2c000.chunk.js:1:380040)
at ea (http://100.64.0.1:10009/dhis-web-aggre

1 Like

Thanks, @linxd. Sorry that you’re having trouble with the data entry app.

Could you check the api/system/info of your instance and let us know what the value for serverTimeZoneId is?

My guess is that the format of the serverTimeZoneId is invalid and that this is then causing problems in the data entry app.

When we know the value of your serverTimeZoneId, we can determine if this is something we need to fix in the back end code (how the serverTimeZoneId value is generated), in the front end code (the the data entry app error), or both.

1 Like

{“contextPath”:“http://100.64.0.1:10009”,“userAgent”:“Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36”,“calendar”:“iso8601”,“dateFormat”:“yyyy-mm-dd”,“serverDate”:“2023-05-30T16:03:49.600”,“serverTimeZoneId”:“GMT+08:00”,“serverTimeZoneDisplayName”:“GMT+08:00”,“lastAnalyticsTableSuccess”:“2023-05-17T09:51:57.079”,“intervalSinceLastAnalyticsTableSuccess”:“318 h, 11 m, 52 s”,“lastAnalyticsTableRuntime”:“00:01:37.198”,“version”:“2.40.1-SNAPSHOT”,“revision”:“c877443”,“buildTime”:“2023-05-29T16:39:36.000”,“jasperReportsVersion”:“6.20.5”,“environmentVariable”:“DHIS2_HOME”,“fileStoreProvider”:“filesystem”,“readOnlyMode”:“off”,“nodeId”:“”,“javaVersion”:“11.0.14”,“javaVendor”:“Oracle Corporation”,“osName”:“Linux”,“osArchitecture”:“amd64”,“osVersion”:“5.19.0-1.el7.elrepo.x86_64”,“externalDirectory”:“/data/dhis/conf”,“databaseInfo”:{“name”:“dhis240”,“user”:“dhis”,“url”:“jdbc:postgresql://172.18.87.238:5438/dhis240”,“databaseVersion”:“PostgreSQL 11.19”,“spatialSupport”:true},“readReplicaCount”:0,“memoryInfo”:“Mem Total in JVM: 4000 Free in JVM: 3005 Max Limit: 7000”,“cpuCores”:8,“encryption”:false,“emailConfigured”:false,“redisEnabled”:false,“systemId”:“6f6ffce1-ad8a-491c-be03-f46abe696c53”,“systemName”:“xxxxxxxxxxxx”,“clusterHostname”:“”,“isMetadataVersionEnabled”:false}

1 Like

Thanks @linxd. The serverTimeZoneId I would expect for this time zone would be Etc/GMT+8.

I will follow up with some of my colleagues to see how we can fix this.

Thanks for letting us know about this issue.

1 Like

No thanks. Thanks for your best work!

1 Like

Thank you @tzemp and @linxd ! Are we creating a Jira bug issue for this? @linxd would you like to create one with your account and share it here: Projects - Jira

Thanks! :slight_smile:

A ticket has been created: DHIS2-15361

We’re discussing how to best address it and if there are work arounds in the meantime.

2 Likes