It may be a fluke that just occurred but check in Event Viewer and SQL Server Logs to see if any other specific event occurred around the time the problem started. Also, check job histories to see if any may have reported an issue or ran extremely long during the time of the condition.