Cannot save the report file. Invalid end row index

Qalyptus Server
#1

Goodday,
i’ve created a report on desktop version. this report contains 2 excel output files.
so Qalyptus is creating 2 Excelfiles by itterate to a field.
this field is called test and consists of 4 values. 010, 020, 030, 040.
within this report I also am filtering on this field. the report only need to create 2 excel fiels for values 030, 040.

in desktop this works fine and all fiters and itteration work perfectly. I got the reports generated.
now I’ve also pushed this to the server and now I’m getting in error when executing a task. the task is set to test mode and if complete it needs to send an email to me. (got this set up)

I’m getting the following error (see below)

  1. what does this error mean
  2. how can I prevent/fix this

Error:

2023-06-15 11:28:46,609 INFO  End of exporting data
2023-06-15 11:28:46,609 INFO  Start creating and saving reports
2023-06-15 11:29:01,953 ERROR Cannot save the report file. Invalid end row index.. Details:    at    .(Int32 , Int32 , Int32 , Int32 )
   at QalyptusEngine.Excel.ExcelCreation.CreateOutputFiles(List`1 ObjectProperties, Workbook template, String tempFilesDir, String _tempFolder, List`1 _destinations, Report report, List`1 fileAttributes, Notification notification, Boolean isIteration, List`1 createdReports, List`1 fieldsValue) in D:\Documents\Projects\Qalyptus\QalyptusEngine\Excel\ExcelCreation.cs:line 0
2023-06-15 11:29:01,953 ERROR An error occurred while exporting data
2023-06-15 11:29:01,953 INFO  End report: QLIK REPORT
2023-06-15 11:29:02,085 ERROR An error occurred while generating reports. Make sure all resources are accessible
2023-06-15 11:29:02,085 ERROR Value cannot be null.
Parameter name: source
2023-06-15 11:29:02,085 INFO  End of the task: QLIKSENSE - APP
#2

Hi @MartWClimber,
Curious error!
Please restart the Qalyptys Server service and try again.
Please let me know.

Thank you
Jeremie

#4

Hi Jeremie,

the report now runs on server as well. turns out that when I created the report it is an iterative report.
for filtering I used the same fields as where the iterative report is using. therefore it started with a value and got 0 values back to put into the report. this is why it crashed.

I’ve fixed. thx for helping

#5

Great!
Thank you, Mart, for your feedback.

#6