At any rate, this is a legitimate message coming from SQL Server, but my first guess to the issue you are fighting is as mentioned above.