This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 14.000000000000002%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETM%3C/text%3E%3C/svg%3E)
Hi, I made the transition by attaching databases from Server 2008 to SQL Server 2019 Developer. One of the databases uses Service Broker.
I noticed that in the Log file (which grew very large in a short time) the following error appeared:
The activated proc '[dbo].[SqlQueryNotificationStoredProcedure-f8159ca1-beff-4e33-9328-10cfe06c36cd]' running on queue 'A102.dbo.SqlQueryNotificationService-f8159ca1-beff-4e33-9328-10cfe06c36cd' output the following: 'Could not find stored procedure 'dbo.SqlQueryNotificationStoredProcedure-f8159ca1-beff-4e33-9328-10cfe06c36cd'.'
The error occurs very often for the same database but with a different GUID in the explanation. Can you tell me what I'm not doing right?
It appears that you have set up query notification somewhere, possibly with the SqlDependncy class.
I don't what is going on, but you will need to dig around: See which queues you have, and which of these SqlQueryNotificationStoredProcedure you have or have not. Not the least check for errors that indicates that they cannot be created.
thanks, I deleted the service and reactivated the Broker Service and now everything seems OK! Thanks a lot for the tips!