Skip to main content

Hello,

 

We are currently on 22R2 for IFS Cloud and we have encountered an error. I created a quick report to pull some values via SQL and we want to schedule this report to attach an excel file of the output onto an email and send it to our users.

We scheduled the report and have the emailing set up properly, but we never received any emails. The only thing we received was this error on the print manager logs.

 

Thanks,
Bryan

 

“Exception while generating Plugin Output Caused by: Error while rendering the report. 11 retries were made. The last error message is Server returned a status other than OK: 500 Message: Internal Server Error”

@bdoucette can you also check the application messages? Are there any errors there as well?

One time when I scheduled a quick report, I was also getting errors in the Background Job that the user didn’t have access to run the Quick Report.

Hi @Marcel.Ausan 

It never hit the application messages, once it failed on the print manager it stopped. The permissions are fine, I double checked they can access all quick reports and I added the specific projection for this one quick report. It seems there might be an error with the system not knowing when to export as excel, but im not sure how else a SQL quick report would be exported…

Thanks,
Bryan

Hi @bdoucette,

I have noticed this error due to ifsapp-reporting-ren container failure as well. Could you please try restarting your ifsapp-reporting-ren Pods in Kubernetes and see if the error persists? In addition, please try a Quick Report that would yield a small result set to narrow down whether the error is caused by the QR itself. 

Hope this helps!

Hi @Charith Epitawatta 

I’m not entirely sure how to restart that without back-end access but I just got the report I scheduled last week. Nothing changed so maybe the ifsapp-reporting-ren pods in Kubernetes restarted over the weekend. Either way, the issue seems to be fixed now.

Thank you for the support and investigation though.

Best,
Bryan

@Charith Epitawatta  is there any way on IFS cloud to identify by ourselves that the container is throwing errors? Would be very helpful to provide this info to the admin users

 

@Charith Epitawatta Are there any limitation in this area? We have some QR which are scheduled and that should be sent by mail. From what we have seen is that for one QR, that ends up being larger than 100 mb in xml_report_data_tab, is that if fails to render to excel format (which seems to be standard for scheduled reports that should be sent by mail) and mail it to the recipient. We can see errors in the reporting-ren pod, saying “...java.lang.OutOfMemoryError: Java heap space...”. We have tried to adjust the memory limits for the pod (to 3.5 gb), approx 3 times the default size for the pod but it still fails.
So we suspect that there is a limit set on 100 mb or is there any other parameters we can adjust to render reports larger than 100 mb?

Reply


Terms & ConditionsCookie settings