Getting an Exception Error:2601.....SPID has a CommandType of BRKR EVENT HNDLR ("LastWaitType" is BROKER_EVENTHANDLER)
Wednesday, December 19, 2012 1:06 AM
I'm Getting an Exception Error:2601.....The SPID for this exception has a CommandType of "BRKR EVENT HNDLR" ("LastWaitType" is BROKER_EVENTHANDLER).
Some Profiler output:Broker:Conversation Group Microsoft SQL Server Service Broker Activation
Broker:Conversation STARTED_OUTBOUND Microsoft SQL Server Service Broker Activation
Exception Error: 2601, Severity: 14, State: 1 sa
Broker:Conversation CLOSED Microsoft SQL Server Service Broker Activation
This repeats over and over again. How can I track this down? Thank you!
I'm not sure if this has anything to do with it since it doesn't always follow that the following transmission status shows up for messages stuck in the transmission queue. I'm including it since it's happening like this right now. It likely started because of some attempt on my part to figure the above out.
Connection attempt failed with error: '10060(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)'.
- Edited by SPLLC Development Wednesday, December 19, 2012 1:08 AM
Thursday, December 20, 2012 8:56 AMModerator
For error 2601, this error occurs when you attempt to put duplicate index values into a column or columns that have a unique index. Microsoft® SQL Server™ does not allow two rows to have the same index value (including NULL) in columns that have a unique index. SQL Server checks for duplicate values when the index is created and each time the table is modified using the INSERT or UPDATE statement.
Please check your conversation, if you need duplicate index values in the indexed column(s), drop the unique index and create a nonunique index.To use a unique index on data that contains duplicate values, you must change some values to prevent the duplication. You can change the data already in the table by using the SELECT or UPDATE statement, or you can change the data to be inserted.
For the second error 10060, please refer to this thread:
TechNet Community Support
- Marked As Answer by Iric WenModerator Thursday, December 27, 2012 8:58 AM