Hello Susmitha,

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.

Please let me know if you have any other questions or concerns on this matter.

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.

Thanks and Regards, 

Susmitha

Hello Susmitha,

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?

Please let me know if you have any other questions or concerns on this matter.