12009 Troubleshooting failed backup jobs within Enhanced Windows Backup Author: Products: URL: /Support_Kb.aspx?kbname=troubleshooting-ewbackup-failed-backups Created: 14-Sep-2005 Last updated: 14-Sep-2005
If you create a job within Enhanced Windows Backup and it seems to start and stop almost immediately when you run it, then there is probably a syntax error in the information being passed from Enhanced Windows Backup to NTbackup. One problem we have observed with early versions (<= 1.1.1003) is that it is possible to create a job with certain disallowed characters in the name e.g. '&'. This means that the job name is invalid to ntbackup and the job fails. To correct this problem, delete the job and re-create it with a name that just uses alpha-numeric characters.
If you create a job within Enhanced Windows Backup and it seems to start and stop almost immediately when you run it, then there is probably a syntax error in the information being passed from Enhanced Windows Backup to NTbackup.
One problem we have observed with early versions (<= 1.1.1003) is that it is possible to create a job with certain disallowed characters in the name e.g. '&'. This means that the job name is invalid to ntbackup and the job fails.
To correct this problem, delete the job and re-create it with a name that just uses alpha-numeric characters.
Click here to view a printable copy of this article