Toad World® Forums

System.ArgumentOutOfRangeException causes filtering issues in Object Explorer

After working in the latest build for an hour or two I keep getting this error: (usually 2- 4 times in a row):

System.NullReferenceException
Object reference not set to an instance of an object.
Stack Trace:
at Quest.Toad.Editor.EditorForm.ExecuteSmartIdle(BarItem barItem)

With this error appearing once:

System.ArgumentOutOfRangeException
Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
Stack Trace:
at System.Collections.ArrayList.get_Item(Int32 index)
at DevExpress.XtraBars.BarItemLinkReadOnlyCollection.get_Item(Int32 index)
at Quest.Toad.Editor.EditorForm.ExecuteSmartIdle(BarItem barItem)

When it gets in this state attempting to open a new connection to another server displays this error 5 times:

System.NullReferenceException
Object reference not set to an instance of an object.
Stack Trace:
at Quest.Toad.Editor.EditorForm.ExecuteSmartIdle(BarItem barItem)

Then this error:

System.ArgumentOutOfRangeException
Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
Stack Trace:
at System.Collections.ArrayList.get_Item(Int32 index)
at DevExpress.XtraBars.BarItemLinkReadOnlyCollection.get_Item(Int32 index)
at Quest.Toad.Editor.EditorForm.ExecuteSmartIdle(BarItem barItem)

Filtering objects in the object list starts to ignore the new filter text you type and leave the filter the way it was:

ObjectExplorerFilterIssue.jpeg

In fact, it doesn’t seem to matter what you put there – or even if you clear it. The object list is now stuck in this filtered state.

The only solution is to close the app and re-open. This happens for me on a regular basis on build 6.6.0.371

Hi Darren,

This error has been fixed in our internal build. We will release a new beta soon to address this error.

Thanks,

Vincent


From:
DarrenM

Sent:
‎10/‎12/‎2014 12:13 AM

To:
toadssbeta@toadworld.com

Subject:
[Toad for SQL Server - Beta Discussion Forum] System.ArgumentOutOfRangeException causes filtering issues in Object Explorer

System.ArgumentOutOfRangeException causes filtering issues in Object Explorer

Thread created by DarrenM

After working in the latest build for an hour or two I keep getting this error: (usually 2- 4 times in a row):

System.NullReferenceException

Object reference not set to an instance of an object.

Stack Trace:

at Quest.Toad.Editor.EditorForm.ExecuteSmartIdle(BarItem barItem)

With this error appearing once:

System.ArgumentOutOfRangeException

Index was out of range. Must be non-negative and less than the size of the collection.

Parameter name: index

Stack Trace:

at System.Collections.ArrayList.get_Item(Int32 index)

at DevExpress.XtraBars.BarItemLinkReadOnlyCollection.get_Item(Int32 index)

at Quest.Toad.Editor.EditorForm.ExecuteSmartIdle(BarItem barItem)

When it gets in this state attempting to open a new connection to another server displays this error 5 times:

System.NullReferenceException

Object reference not set to an instance of an object.

Stack Trace:

at Quest.Toad.Editor.EditorForm.ExecuteSmartIdle(BarItem barItem)

Then this error:

System.ArgumentOutOfRangeException

Index was out of range. Must be non-negative and less than the size of the collection.

Parameter name: index

Stack Trace:

at System.Collections.ArrayList.get_Item(Int32 index)

at DevExpress.XtraBars.BarItemLinkReadOnlyCollection.get_Item(Int32 index)

at Quest.Toad.Editor.EditorForm.ExecuteSmartIdle(BarItem barItem)

Filtering objects in the object list starts to ignore the new filter text you type and leave the filter the way it was:

In fact, it doesn’t seem to matter what you put there – or even if you clear it. The object list is now stuck in this filtered state.

The only solution is to close the app and re-open. This happens for me on a regular basis on build 6.6.0.371

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for SQL Server - Beta
notifications altogether.

Toad for SQL Server - Beta Discussion Forum

Flag
this post as spam/abuse.

Hello,

I am running into this same issue for weeks on end, but for TOAD for Db2 and not SQL Server. I am running TOAD 6.0.0373. I have not been able to re-create the issue. I was wondering if this issue has been documented for DB2 if you can find out and if this patch will fix my issue. Any help would be greatly appreciated. Thanks! Robert

For Toad DB2, this issue was addressed in our v6.1 version.

That version is currently in beta and the beta can be downloaded at:

www.toadworld.com/…/default.aspx

Please try the latest v6.1 beta.

Thanks

Jeff