Getting an error when exporting a report to excel
I am getting an error when exporting a report to excel. Error on the tracer is below;
Section 'pzRDExportWrapper' execution error on page '' of class 'Rule-Obj-Report-Definition'. : Method org/apache/poi/xssf/streaming/SXSSFWorkbook.getFontAt(I)Lorg/apache/poi/ss/usermodel/Font; is abstract |
Pegasystems Inc.
US
Hello,
I feel it would be better if you share us the complete stack trace noticed in the PegaRULES while running the export to excel functionality and attach it in the text file, that way it can help us to analyze the stack trace, if possible you can share the tracer log also. Based on your above explanation i assume you are using the OOTB export to excel functionality on the Report Definition and nothing has been customized.
Thanks,
Mahesh M
Pegasystems Inc.
US
Its strange that the root cause behind the failure of pzRDExportWrapper section is not available in your stacktrace, not sure whether you trimmed it or its complete stacktrace,
2019-04-04 08:33:05,321 [ttp-nio-8081-exec-27] [TABTHREAD2] [ ] [--] (e_Obj_Report_Definition.Stream) ERROR -- engincan.yildiz - Section 'pzRDExportWrapper' execution error on page '' of class 'Rule-Obj-Report-Definition'. 2019-04-04 08:33:05,321 [ttp-nio-8081-exec-27] [TABTHREAD2] [ ] [--] ( internal.mgmt.Executable) ERROR -- engincan.yildiz - Exception 2019-04-04 08:33:05,322 [ttp-nio-8081-exec-27] [TABTHREAD2] [ ] [--] (ngineinterface.service.HttpAPI) ERROR -- engincan.yildiz - --: com.pega.pegarules.pub.PRRuntimeError
If its trimmed please share the complete stack trace of the use case to identify its root cause also have couple of questions,
- Which Pega version are you using?
- Did the system gone through any recent upgrade/update?
- Is the issue happening for all the report definitions or specific to any?
EIB
PL
I just replaced the host and ip with "--". That's the log file I got after clicked export to excel.
- Version is 7.4.
- The system has not updated recently.
- It is happening for all report definitions.
Pegasystems Inc.
US
Going forward, I would recommend you to go ahead with the SR creation as we don't have enough information to identify its root cause from the shared logs. As a last try you can restart the server to check the behavior, sometimes restart fixes this kind of strange issues.