February 14, 2013 at 11:03 am
There was a SQL connection error last night, which it then resolved by itself. I am just trying to anaylze what exactly happened. By looking at the SQL server error log for that particular timing, I see the below message:
"Sourcespid45s
Message
The query notification dialog on conversation handle '{75A4EE5E-7E72-E211-9F96-001CC4E5C2E2}.' 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-c10de0bf-349b-40ad-b3e0-51a2e7ce82cc' because it does not exist.</Description></Error>'."
I see the same error happend 10 times within the same minute.
Can anyone experience similar error or if you have any idea about this error, please let me know.
Thanks,
SueTons.
Regards,
SQLisAwe5oMe.
February 15, 2013 at 1:21 am
Do you have a custom message broker running?
We get that a lot due to SQL dependencies when our message broker service stops and starts, as it drops and recreates the queues services procedures etc with a new GUID.
February 15, 2013 at 7:08 am
anthony.green (2/15/2013)
Do you have a custom message broker running?We get that a lot due to SQL dependencies when our message broker service stops and starts, as it drops and recreates the queues services procedures etc with a new GUID.
How can I find this?
SueTons.
Regards,
SQLisAwe5oMe.
February 15, 2013 at 7:13 am
Ask your developers if they have wrote a message broker would be the best bet.
February 15, 2013 at 8:14 am
Dev team have no idea,
is it possible to pull out the name of the service?
SueTons.
Regards,
SQLisAwe5oMe.
February 15, 2013 at 8:37 am
Service probably changed now.
Check all your databases to see if they have a service broker service running in them then trace what is trying to call the service and the procedures.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply