We have a client running our .NET application which connects to SQL Server 2005 on the backend. A few weeks ago the database crashed and the whole server had to be rebooted. This happened again today and I got the log file from their DBA which seriously offered no clue as to what’s really going on. I searched on Google and Bing and only found one other mention of this on a Russian programmers forum. Given that my Russian sucks (i.e. non-existent) I decided to throw out to the geniuses on stackoverflow. Here’s the non-informative log message:
SQL Server Assertion: File: T:\Yukon\sql\ntdbms\storeng\dfs\manager\lckmgrp.h, line=675 Failed Assertion = ‘m_iteratorInSafeState’. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
Any ideas?
I thank you in advance for your thoughtful replies.
Erick
After a bit more digging to another error that had a similar signature, I was able to determine the client needed to upgrade to Service Pack 3 since they were still on SP 1. This was also confirmed by Microsoft support.