What are the challenges you face when working across database platforms? Take the survey

backup jobs just start failing with error 300

joesjoes Posts: 11
edited January 19, 2007 1:51PM in SQL Backup Previous Versions
SQL Backup - Professional edition.

I get these errors every now and then for now reason. No permissions have changed, I have serveral servers backing up to the same shares with no issue.

Below is the error msg.

SQL Backup job failed with exitcode: 300 SQL error code: 0 [SQLSTATE 42000] (Error 50000). The step failed.

Can someone help please.

joe s


  • Options
    peteypetey Posts: 2,358 New member
    When SQL Backup runs a backup, it requires SQL Server to have a certain amount of contiguous free memory. If SQL Server is unable to service the request, the backup process is aborted and reattempted, with a smaller amount of contiguous free memory. If SQL Server is able to service that request, the backup proceeds. However, a warning (300) is logged to inform you that SQL Server may be running into a low memory condition.

    If you look for the corresponding SQL Backup log file (default folder is C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\<instance name>, it should provide some memory statistics at the time the initial backup failed.

    You can configure SQL Backup to request a lower amount of memory initially, by using the MAXTRANSFERSIZE option. The help file has details on this.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Options
    thank you for your answer, now the error makes more sense.
    joe s
Sign In or Register to comment.