BSavoie (9/18/2010)
Wow, this is incredibly old. I forgot the specific details of the solution. I just remember that it was related to encrypted stored procedure(s). Sombody, or something was trying to access encrypted sprocs.Hope this gets you moving in the right direction.
Thank you, it looks like this error is generic enough to appear in various situations. I don't have encrypted sprocs in that environment, but I do have mirroring set up to a reporting server, and that seems to be related somehow to what happened in my case.
I may need to ask Microsoft for help in figuring this one out.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]