I think the point was that it wasn't an NHibernate problem, it was a SQL Server problem. The first link when you google that error message gives a good troubleshooting process, and the guy gave no indication that he had searched first. But it agree that it was an over the top response.