Exit Code 505

SQL_DudeSQL_Dude Posts: 11 Bronze 1
in SQL Backup
Over the weekend our SQL Backup jobs locked up on something and I had a huge mess to clean up on Monday.  I am not sure if it was the job that backs up all of the databases once a day or the one that backs up all of the log files every 15 minutes.  When I came in on Monday the log files had grown exponentially and the history of the jobs showed that they had been failing for a couple of days but the history stopped on Saturday and I did not receive any emails about failures after the time that it had stopped.  When I tried to start the backup job I got a message saying that the job was already running.  So I stopped all of the SQL Backup jobs and tried to run it.  The job ran for over and hour before throwing an error.  That was 8am this morning.  It is now almost midnight, we've been trying all day to get SQL Backup to start working again.  We did succeed in getting the Database backup job to run finally.  Unfortunately the Log backups fail and are now returning an Exit Code 505 error.  Not sure why this is happening now after these jobs had been running for several months with no issue.
Any idea of a way to fix this?
Tagged:
· Share on Twitter

Answers

Sign In or Register to comment.