Exception: capacity was less than the current size

PDinCA

Build: 1.3.0.58
Client: Windows 7 Ultimate
Server: 2003 32-bit
DB: 2008 SP1

What: Viewed a deadlock. Clicked the next exception, which is a "Long running query" and the exception below occurs.

When: Every time I click on it.

SQL Response 1.3 has encountered a problem and needs to close.
If you were in the middle of something, the information you were working on may be lost.

Technical details:

capacity was less than the current size.
Parameter name: capacity

ArgumentOutOfRangeException

at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
at System.Collections.Generic.List`1..ctor(Int32 capacity)
at k.a.<>c__DisplayClass1.<RequestData>b__0(Object )
at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

AlertRepositoryLogFile:
For the time I tried to view the Alert:
15:31:48.557|Info |AlertRepository |36 |Begining old data cleanup.
15:31:48.557|Info |AlertRepository |36 |Cleaning old data
15:32:12.837|Info |AlertRepository |36 |Old data clean complete
15:32:12.837|Info |AlertRepository |36 |Checking for deleted servers
15:32:12.837|Info |AlertRepository |36 |Deleted servers checked
15:32:12.837|Info |AlertRepository |36 |Checking for old files
15:32:12.915|Info |AlertRepository |36 |Old files checked

Anu D

Many thanks for your post and apologies for the inconvenience caused.

Let us know if this happens for all the alerts on that server? Does the behaviour changes for the other SQL Server added (if any)?

Have you tried restarting the Alert Repository service? Kindly let me know if this makes any difference.

PDinCA

Of the 3 alert categories, this is the only one that causes the problem.

Alert Service restarted. UI bombs.