Actually, I did finally figure out my issue.  The timer that I was using was a System.Timers.Timer, not a Windows.Forms.Timer.  The timer that I was using works on a separate thread, not the main thread as a Windows.Forms.Timer does.  When I changed out the variety of timer, I was golden!

Mike,

I have the troublesome area at least pinpointed if not actually figured out.  I have a reminders service that has a timer ticking every 30 seconds.  This timer elapsing may raise an event which carries a datatable as payload.  This binds to a grid.  The curious thing is, I do not experience any errors in this area, only later and on other, unrelated grids. 

Are the grids sharing some resource behind the scenes that could be getting involved here?

I have checked and checked for how this could be happening, but I don't see how it's possible.  I've seen in many forum posts for this and other controls that such kinds of errors are typically traced back to threading issues.  Unless I'm doing something where I don't realize I'm actually using threading (built into some other components I'm using perhaps) then I am stymied.

I am having the same issue. The first time I set the datasource, it is fine (I am using just a datatable to bind), but sometimes on subsequent times when I set the datasource, I get this stack trace.

at Infragistics.Win.UltraWinGrid.UltraGridBase.Set_ListManager(Object newDataSource, String newDataMember)
at Infragistics.Win.UltraWinGrid.UltraGridBase.set_DataSource(Object value) etc….

I do use background threads in my application, but nowhere in the program flow involved with setting these grids..

I'm using 2008.3.

Any ideas?