• Any updates to this thread? We just received this error on a SQL 2008 R2 server here in our environment.