• Could this have happened following a reboot of the Windows box hosting SQL Server?