We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy.
Unfortunately, activation email could not send to your email. Please try again.

Exception encountered in SyncFusion Grid

Thread ID:

Created:

Updated:

Platform:

Replies:

63179 Jun 28,2007 10:19 PM Jul 12,2007 01:22 AM Windows Forms 8
loading
Tags: GridControl
Yang Xuemei
Asked On June 28, 2007 10:19 PM

I encountered an InvalidArgument exception thrown by SyncFusion Grid. Below is the detailed exception:
Exception object: 01b30e58
Exception type: System.ArgumentException
Message: Value does not fall within the expected range.
InnerException:
StackTrace (generated):
SP IP Function
0012EC70 0C6E20BA Syncfusion.Windows.Forms.Grid.GridRangeInfo..ctor(Int32, Int32, Int32, Int32)
0012EC8C 0C6E2B40 Syncfusion.Windows.Forms.Grid.GridRangeInfo.Cells(Int32, Int32, Int32, Int32)
0012ECA4 0C7A7012 Syncfusion.Windows.Forms.Grid.GridCellModelBase.OnActiveTextChanged(Syncfusion.Windows.Forms.Grid.GridCellEventArgs)
0012ECB8 0C7A6F5D Syncfusion.Windows.Forms.Grid.GridCellModelBase.SetActiveText(Int32, Int32, System.String)
0012ECD4 0C7A6B32 Syncfusion.Windows.Forms.Grid.GridCellRendererBase.OnBeginEdit()
0012ECE4 0C7A6808 Syncfusion.Windows.Forms.Grid.GridCurrentCell.BeginEdit()
0012ECEC 03BB5E3E Syncfusion.Windows.Forms.Grid.GridControlBase.FixCurrentCellGotFocus(Boolean)
0012ED34 0C8DEA46 Syncfusion.Windows.Forms.Grid.GridControlBase.OnControlGotFocus()
0012ED3C 0C8DE9F8 Syncfusion.Windows.Forms.Grid.GridDataBoundGrid.OnControlGotFocus()
0012ED58 0C8DE885 Syncfusion.Windows.Forms.ScrollControl.RaiseControlGotFocus()
0012ED60 0C8DE83A Syncfusion.Windows.Forms.ScrollControl.OnGotFocus(System.EventArgs)
0012ED68 7B06BF34 System.Windows.Forms.Control.WmSetFocus(System.Windows.Forms.Message ByRef)
0012EDA0 7B072EB5 System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
0012EE04 0C7A94D8 Syncfusion.Windows.Forms.ScrollControl.WndProc(System.Windows.Forms.Message ByRef)
0012EE14 0C7A9264 Syncfusion.Windows.Forms.Grid.GridControlBase.WndProc(System.Windows.Forms.Message ByRef)
0012EE34 7B07A72D System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
0012EE38 7B07A706 System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
0012EE4C 7B08B845 System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)
00000000 00000001 System.Windows.Forms.UnsafeNativeMethods.SetFocus(System.Runtime.InteropServices.HandleRef)
0012F02C 7B082D91 System.Windows.Forms.ContainerControl.FocusActiveControlInternal()
0012F080 7B0692D3 System.Windows.Forms.Form.set_Active(Boolean)
0012F08C 7B067337 System.Windows.Forms.Form.WmActivate(System.Windows.Forms.Message ByRef)
0012F098 7B063E4E System.Windows.Forms.Form.WndProc(System.Windows.Forms.Message ByRef)
0012F0A8 00FC5769 Slb.Horizon.NewUIFramework.SlbConsole.WndProc(System.Windows.Forms.Message ByRef)
0012F0C4 7B07A72D System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
0012F0C8 7B07A706 System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
0012F0DC 7B08B845 System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)
00000000 00000001 System.Windows.Forms.UnsafeNativeMethods.PeekMessage(MSG ByRef, System.Runtime.InteropServices.HandleRef, Int32, Int32, Int32)
0012F328 7B08463F System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32, Int32, Int32)
0012F3C8 7B08432D System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
0012F434 7B08416B System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
0012F464 7B0C69FE System.Windows.Forms.Application.Run(System.Windows.Forms.Form)
0012F474 11013003 Slb.Horizon.NewUIFramework.NewConsole.Main(System.String[])

StackTraceString:
HResult: 80070057


Below is the event argument object:
Name: Syncfusion.Windows.Forms.Grid.GridCellEventArgs
MethodTable: 0c780318
EEClass: 0c6b6ec8
Size: 16(0x10) bytes

MT Field Offset Type VT Attr Value Name
790f7b5c 400017d 44 System.EventArgs 0 shared static Empty
>> Domain:Value 001953d0:0140464c <<
790fed1c 4000139 4 System.Int32 0 instance 2147483647 rowIndex
790fed1c 400013a 8 System.Int32 0 instance 2147483647 colIndex


Is this a known issue or some information about it?

thanks,

haneefm [Syncfusion]
Replied On June 29, 2007 02:04 PM

Hi Xuemei,

The error which you have mentioned, is an indication of threading issues. Are there multiple threads involved in your appilcation? If so, please check the Knowledge Base(KB) article link below.
http://www.syncfusion.com/support/kb/grid/Default.aspx?ToDo=view&questId=78

Intermittant errors can be indications of threading issues. Any calls into the grid must be done on the thread that creates it, and you can use grid.InvokeRequired to check for this.
Here is a sample.
LoadDataBackGroundThread

Best Regards,
Haneef

Yang Xuemei
Replied On July 10, 2007 05:52 AM

Hi Haneef,

We didn't have multithread in our application.So, it should not be an multithread issue.

Any other possiblities or clues about it?

thanks again,
Xuemei


>Hi Xuemei,

The error which you have mentioned, is an indication of threading issues. Are there multiple threads involved in your appilcation? If so, please check the Knowledge Base(KB) article link below.
http://www.syncfusion.com/support/kb/grid/Default.aspx?ToDo=view&questId=78

Intermittant errors can be indications of threading issues. Any calls into the grid must be done on the thread that creates it, and you can use grid.InvokeRequired to check for this.
Here is a sample.
LoadDataBackGroundThread

Best Regards,
Haneef

haneefm [Syncfusion]
Replied On July 10, 2007 04:31 PM

Hi Xuemei,

Thank you for your update.

I am not sure of what be might be causing this strange behavior without a working sample. Is it possible for you to upload us a minimal sample to reproduce the issue here? This will help us to analyse the issue further.

Exactly what version of Windows XP are you using?

Are you only installing Essential Grid or are you installing Essential Studio? Are you installing binaries only, or the source code version?

What version of the .NET framework and VS are you using?

Best Regards,
Haneef

Yang Xuemei
Replied On July 10, 2007 10:34 PM

hi, haneef,
thanks again.
It is not a common problem. I only encountered it once and made a dump file. It can not be reproduced any more.
I installed SyncFusion Suite 2.0.1.9. Very old version, i know. Only the Grid installed, and binary version.
i am using Windows XP professional 2002 version with SP2.
The .NET framework version is 2.0.Visual Studio is 2005.

Any way, thanks for your help,
Xuemei

haneefm [Syncfusion]
Replied On July 11, 2007 03:54 PM

Hi Xuemei,

Searching our Direct Trac database for instances of this error does show a few. The problem occurred for two reason. First one is multithreaded situations where there are calls into the grid that are not protected by grid.InvokeRequired checks. So, if you are using multithreads, you need to make sure there are no unprotected calls in the grid from a thread other than the thread that created the grid. Second one is GridRangeInfo.InternalCells() method. This GridRangeInfo.InternalCells() method problem has been resolved in Essential Version v3.2 and above, can you please try in any one of our latest version? There has been a change in the GridRangeInfo class to avoid an exception:

// From 3.2 release notes
*Added a check for top < 0 || left < 0 in GridRangeInfo.InternalCells to avoid exception being thrown.

Here is the modified GridRangeInfo.cs where we added a check for top < 0 || left < 0 in GridRangeInfo.InternalCells to avoid exception being thrown.

Best regards,
Haneef

haneefm [Syncfusion]
Replied On July 11, 2007 04:34 PM

Hi Xuemei,

Searching our Direct Trac database for instances of this error does show a few. The problem occurred for two reason. First one is multithreaded situations where there are calls into the grid that are not protected by grid.InvokeRequired checks. So, if you are using multithreads, you need to make sure there are no unprotected calls in the grid from a thread other than the thread that created the grid. Second one is GridRangeInfo.InternalCells() method. This GridRangeInfo.InternalCells() method problem has been resolved in Essential Version v3.2, can you please try in this version? There has been a change in the GridRangeInfo class to avoid an exception:

// From 3.2 release notes
*Added a check for top < 0 || left < 0 in GridRangeInfo.InternalCells to avoid exception being thrown.

Here is the modified GridRangeInfo.cs where we added a check for top < 0 || left < 0 in GridRangeInfo.InternalCells to avoid exception being thrown.

Best regards,
Haneef

haneefm [Syncfusion]
Replied On July 11, 2007 05:14 PM

Hi Xuemei,

Searching our Direct Trac database for instances of this error does show a few. The problem occurred for two reason. First one is multithreaded situations where there are calls into the grid that are not protected by grid.InvokeRequired checks. So, if you are using multithreads, you need to make sure there are no unprotected calls in the grid from a thread other than the thread that created the grid. Second one is GridRangeInfo.InternalCells() method. This GridRangeInfo.InternalCells() method problem has been resolved in Essential Version v3.2, can you please try in this version? There has been a change in the GridRangeInfo class to avoid an exception:

// From 3.2 release notes
*Added a check for top < 0 || left < 0 in GridRangeInfo.InternalCells to avoid exception being thrown.

Here is the modified GridRangeInfo.cs where we added a check for top < 0 || left < 0 in GridRangeInfo.InternalCells to avoid exception being thrown.

Best regards,
Haneef

Yang Xuemei
Replied On July 12, 2007 01:22 AM

hi haneef,
thanks again.
Yes, we have renewed your latest version 4.4 suite. We will update it later.


CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.

;