Not sure if this is the right forum for this question, but my closest searches (thought disappointing) have suggested it is probably a SQL-related issue.
We're getting this error once every other week or so on an ASP.NET application built on .NET Framework 3.5 running against SQL Server 2005. I can't find much info on this error, but we are up to date on our SQL Server service packs. When we get this error no one is able to make a connection and we end up having to reboot the server.
Has anyone experienced this error and found a solution for it?