February 1, 2018 at 4:09 am
Hi Experts,
Getting a lot of below error message in SQL Error Log. We have SignalR running which have dependency on Service Broker. How to resolve this ?
Message
The query notification dialog on conversation handle '{FFD6B812-3F07-E811-80F6-005056940E84}.' closed 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 'SqlQueryNotificationService-c117a527-2848-4616-bcbd-6a9ee66f5091' because it does not exist.</Description></Error>'.
Message
Error: 9245, Severity: 16, State: 1.
Message
During the last time interval 2 query notification errors were suppressed.
February 1, 2018 at 6:39 am
VastSQL - Thursday, February 1, 2018 4:09 AMHi Experts,Getting a lot of below error message in SQL Error Log. We have SignalR running which have dependency on Service Broker. How to resolve this ?
Message
The query notification dialog on conversation handle '{FFD6B812-3F07-E811-80F6-005056940E84}.' closed 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 'SqlQueryNotificationService-c117a527-2848-4616-bcbd-6a9ee66f5091' because it does not exist.</Description></Error>'.Message
Error: 9245, Severity: 16, State: 1.Message
During the last time interval 2 query notification errors were suppressed.
Those errors are generally due to how the application implements and closes the notifications. Service Broker is reporting the errors but it's not caused by service broker.
It's basically from an application that exits or drops the service, queue, etc but there are still notification subscriptions. The following explains it better:
When it rains, it pours
You can try to figure out which subscription is "orphaned" by querying sys.dm_qn_subscriptions but that's not necessarily easy. If you do figure it out, you can use
KILL QUERY NOTIFICATION SUBSCRIPTION
You can pass in the subscription id. If you wanted to be more extreme and possibly break things, which you really need to understand what all the app is doing and and what the consequences for the app would be, you can pass in ALL as the parameter which removes all subscriptions
Sue
February 3, 2018 at 10:29 pm
Sue_H - Thursday, February 1, 2018 6:39 AMVastSQL - Thursday, February 1, 2018 4:09 AMHi Experts,Getting a lot of below error message in SQL Error Log. We have SignalR running which have dependency on Service Broker. How to resolve this ?
Message
The query notification dialog on conversation handle '{FFD6B812-3F07-E811-80F6-005056940E84}.' closed 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 'SqlQueryNotificationService-c117a527-2848-4616-bcbd-6a9ee66f5091' because it does not exist.</Description></Error>'.Message
Error: 9245, Severity: 16, State: 1.Message
During the last time interval 2 query notification errors were suppressed.Those errors are generally due to how the application implements and closes the notifications. Service Broker is reporting the errors but it's not caused by service broker.
It's basically from an application that exits or drops the service, queue, etc but there are still notification subscriptions. The following explains it better:
When it rains, it poursYou can try to figure out which subscription is "orphaned" by querying sys.dm_qn_subscriptions but that's not necessarily easy. If you do figure it out, you can use
KILL QUERY NOTIFICATION SUBSCRIPTION
You can pass in the subscription id. If you wanted to be more extreme and possibly break things, which you really need to understand what all the app is doing and and what the consequences for the app would be, you can pass in ALL as the parameter which removes all subscriptionsSue
Thanks Sue
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply