I have seen a similar error in the past when using NOLOCK on an active table with a blob column. The scenario is that someone starts a query that...