Wednesday, March 21, 2012

Problems with Poison Message Processing

I am getting the following Error and I can't find it in the Manual.

Failure to send an event notification instance of type 'BROKER_QUEUE_DISABLED' on conversation handle '{5D273374-E84F-DB11-B3BC-0004239AB15C}'. Error Code = '8429'.

I have checked the service name for the notification and it appears to be okay.

Any ideas would be welcomed,

Gary

select * from sys.messages where message_id = 8429

The conversation endpoint is not in a valid state for SEND. The current endpoint state is '%ls'.

This indicates that the dialog is ended prematurely, probably by a dialog error. The ERRORLOG file and the system eventlog will contain an entry indicating the error which ended the notification dialog. The corrective action depends on the said error.

HTH,
~ Remus

|||

Thanks Remus,

I will send the error from the log the next time I recreate it. It has rolled off of the log for now.

Gary

|||

Hi All!

Remus, could you please help me?

I received error message when I processing messages:

"The conversation endpoint is not in a valid state for SEND. The current endpoint state is 'ER'"

You sad " The corrective action depends on the said error."

How can I fixed my problem with endpoint state = 'ER'?

Thank you very much for help!

Sveta

|||

It means that the dialog carrying the notifications was ended with an error. The NT EventLog should contain an entry like this:

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17003
Date: 11/9/2006
Time: 11:25:06 AM
User: N/A
Computer: REMUSR64
Description:
Closed event notification conversation endpoint with handle '{387BECFA-2770-DB11-9D68-00123F783601}', due to the following error: '<?xml version="1.0"?><Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8490</Code><Description>Cannot find the remote service &apos;s&apos; because it does not exist.</Description></Error>'.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 6b 42 00 00 10 00 00 00 kB......
0008: 09 00 00 00 52 00 45 00 ....R.E.
0010: 4d 00 55 00 53 00 52 00 M.U.S.R.
0018: 36 00 34 00 00 00 07 00 6.4.....
0020: 00 00 74 00 65 00 6d 00 ..t.e.m.
0028: 70 00 64 00 62 00 00 00 p.d.b...

The actual error (highlighted) will probably be different in your case, but it will indicate what the problem is.

HTH,
~ Remus

No comments:

Post a Comment