Hi Mike,

I have an open case number for this - "CAS-40329-O7D41C".

You'll be able to see all the detail in there, but I am suggesting there is a problem with the cached graphics mechanism in the UltraExplorerBar control (which seems to be a univeral mechanism across infragistic controls, including the UltraGridExcelExporter). We are seeing the problem, specifically when an UltraExplorerBar group is selected.

internal void AnimateGroupSelection(UltraExplorerBarGroup newSelectedGroup)
(UltraExplorerBar.cs – Line 17485)

(DrawUtility.ReleaseCachedGraphics() is not being called within AnimateGroupSelection which I believe is causing the problem).

In our code, if we select the group .Selected = True we get the error in our main application. If we omit this, the problem goes away.

It took us 3 - 4 days (changeset by changeset in Team Foundation Server) to work this one out.

(I did by the way check the windows handles on a few of our servers where users run the application, and all looked normal. Handles did not go over 600 at any point in the day).

Kind regards,

Andrew

Hi,

I have the same error when I cancel the export of a grid in PDF or Word with plus than one bands and large amount of data (during the "Measuring and laying out the grid for export to.."). Apparently all work fine but when I try to export another grid is say "Parameter not valid" in the  InitializeComponent.

I try to declare the UltraGridWordWriter, UltraGridDocumentExporter and UltraGridExcelExporter as shared and add the handler dynamically in the load form event but now it say "Parameter not valid" during the ExportAsync in the function:

Private Sub BtnExportExcel_Click(sender As System.Object, e As System.EventArgs) Handles BtnExportExcel.Click
        UltraGridExcelExporterObject.ExportAsync(MyGrid, MyPath)
End Sub

I cannot reproduce in a small environment.

I have the last relase of infragistic v12.2

Hi,

I am still getting this issue infrequently on Production.

It is producing on only one client but I am unable to reproduce it on my local system. I have Infragistics V12.1 Version.

The code which is causing problem is as below:-

this.ultraGridExcelExporter = new Infragistics.Win.UltraWinGrid.ExcelExport.UltraGridExcelExporter(this.components);

Please let me know if this issue is fixed or there is any Hotfix available for this.

Thanks,

Kuldeep Agrawal

Hi,

Can you tell me anything more about the circumstances under which it occurs?

For example, does it happen when your application has been running for a long time? Or does it happen immediately after the app has only been running for a few minutes?

Are you sure the customer's machine is using the same version of the Infragistics assemblies that you are?

Does it happen when exporting a large Excel file or does it also happen for smaller files?

Hey Mike,

There is no certain scenario in which it is reproducing. Client was not doing anything with excel exporting etc at the time the error popped up.

And client is also using the same version of Infragistics as I am.

Please let me know if any workaround is available.

Thanks,

Kuldeep

That Exception is very vague and can occur for any number of reasons. Have you tried getting the latest service release?

If that doesn't help, can you reproduce the issue in a small sample project and post it here so we can check it out?

Hi,

We are using Infragistics 14.1 WinForms and we are getting this error from production as well.

is there any solution to this?

Details:

Inner Exception:

Parameter is not valid.

   at System.Drawing.Graphics.GetHdc()

   at Infragistics.Win.UltraWinGrid.ExcelExport.UltraGridExcelExporter..ctor()

   at Infragistics.Win.UltraWinGrid.ExcelExport.UltraGridExcelExporter..ctor(IContainer container)

its  also  happened with  me  in this  version  13.1.20131.2124 not  in  exporting  just  in  initializing  in this  generated  code  

 Me.UltraGridExcelExporter1 = New Infragistics.Win.UltraWinGrid.ExcelExport.UltraGridExcelExporter(Me.components)

Where can I get the service Release for 13.1.

Yes, my application use background threads. but we didn't have this issue with the earlier version of infragistics but just this release.