Hi All ,
I am reaching out to address a critical issue that we are currently facing while utilizing the export method within your software library.
Our team has been using the export functionality to export sizable data sets, and we recently encountered a significant challenge when attempting to export a data set comprising 900,000 records. Unfortunately, during the export process we encountered an error that prevented the successful completion of the operation.
The error message we received is as follows :
Specified Path Does not Exists.
To help you better understand the situation, we have included some relevant details below:
Attaching Sample code screenshot:
-- Creating Record
-- Exporting (900,000 record) by using ultraGridExcelexport
-- getting Specified Path Does not Exists Error.
Thanks and Regards,
Susmitha
Hello Susmitha,
I have been investigating into the behavior you are seeing, but unfortunately, I cannot see your screenshots because they are too small and zooming in just makes them too blurry to read. I believe I can provide some information on why this error happens, though.
I have been doing some research on why this error can happen, and it appears that this can happen if you export to a .xls file and exceed the maximum row count of that file extension. The .xls file type supports a maximum of 65,536 rows, which your 900,000 rows vastly exceed. You need to export to a .xlsx file extension if you are not doing so already.
Please let me know if you have any other questions or concerns on this matter.
Hi All,
I am Exporting record into .xlsx file extension only using workbookFormat.Excel2007.
To help you better understand the situation, I have included some relevant details and I am Reattaching the screenshot in pdf format.
CreatingTestrecord.pdfExportMethod.pdfErrorMessage.pdf
Thanks and regards,
I have tried this on my end but have not yet been able to reproduce this issue, but I do have a couple of additional questions for you on this matter that might help us to track this down. Can you please provide answers to the following?
1. What is the specific version of Infragistics for Windows Forms that you are using? For example, if you were using version 23.1, this version number would look like 23.1.20231.XXXX. It can be found in the properties window of one of the DLLs that you are referencing.
2. When is this error occurring for you? Does it happen immediately, or is it after the Export has run for a while?
Hi Andrew Goldenbaum,
Please find the details below,
1. We are using Infragistics4.Win.UltraWinGrid.ExcelExport.v22.2.dll, version 22.2.20222.16.
2. For processing 900,000 records, it took more than 20 hours before encountering an error.
I have been looking back through your attachments in this case, and I’m curious to know what the actual exception you are seeing in this case is. It looks like your try/catch block is throwing out the same MessageBox regardless of the type of exception encountered with your “Properties.Resources.Message_Failed” message in this case, and so this may not be correct to the actual exception you are encountering.
I would like you to modify the try/catch block to be something more along these lines and then try your export again, as this may help us to find what the actual issue is:
try { //do export here } catch(Exception ex) { MessageBox.Show(ex.ToString() + Environment.NewLine + ex.Message + Environment.NewLine + ex.StackTrace); }
It also may be worth printing out the ex.InnerException above. I personally have a feeling that what you are seeing is probably an OutOfMemoryException, as an Excel file with 900,000 rows and 25 columns would be a pretty huge file – the same structure with only 20,000 rows is 17MB, so with the assumption that it scales linearly, the resulting file with 900,000 rows would be nearly 750MB. Still, please let me know what the result is of the MessageBox mentioned above, as this will be more indicative of the type of exception you are hitting.
I also have to ask if this sized Excel file is actually representative of your actual business requirement in this case, or are you doing more of a stress-testing scenario? I ask, as I’m not sure what any human user would do with an Excel file of this size? Not to mention, Excel takes several seconds just to open the 20,000 row and 25 column one mentioned above, and so I’m not sure how long it would even take just to open one with 900,000 rows and 25 columns, but I would imagine it would probably be several minutes.