I just encountered this error. Similar to previous posts, the errorlog grew dramatically (> 16GB) and SQL Server stopped accepting connections. I also am running SQLSafe for db...