Error 500 in push analysis

[Natalie_Tibbels]

Has anyone seen this error for a push analysis (in 2.33.3):

{“httpStatus”:“Internal Server Error”,“httpStatusCode”:500,“status”:“ERROR”,“message”:“could not extract ResultSet”}

It seems to happen when I have a catcombo assigned to the program where the data is coming from (not the data element, but with an attribute of the tracker program itself). It’s only one pivot table on the dashboard I’m using for the push analysis and it renders fine on the dashboard. Thanks!

[Scott (Scott Russpatrick)]

Hi @Natalie_Tibbels,

I’m not aware of that issue. Can you report a bug in jira please?

[Natalie_Tibbels]

I just tested the push analysis again now that I’ve assigned the attribute options to the OUs, and now the push analysis working for aggregate data! When the dashboard contains program indicators from tracker programs (still with attribute assigned and now shared with the OU), the push analysis fails: {“httpStatus”:“Internal Server Error”,“httpStatusCode”:500,“status”:“ERROR”,“message”:“ERROR: current transaction is aborted, commands ignored until end of transaction block”}

Reporting rates not working in 2.33

Hi @Dipali_Sahu, We have identified that the issue (at least in Uganda and Tanzania) is that attribute category options that are assigned to the data set do not have any organizational units assigned to them. This must be done to enable DHIS2 to calculate the expected number of reports. To address this issue: Assign all catigory options that are assigned to a data set to the organizational units you expect to receive a report for. [image] Run your resource tables. This makes sure that DHIS…

[Scott (Scott Russpatrick)]

Hi @Natalie_Tibbels,

Glad to hear that we have at least partially addressed the issue. Could you please make report the bug in jira for the program indicator attributes disrupting the reporting rate issue?