I have a Windows Server 2003 sp2 AD with around 30 Windows XP Pro machines (SP3). I was recently asked to implement some auto backups on a few of the machines. I attempted to schedule ntbackup on these machines. With a Admin User I selected the proper folders and location to back them them up. Just to make sure the backup ran correctly I then ran the job manually. It ran perfect and backed up to the proper location. The problem comes I click the 'set schedule' button of NTBackup. I immediately get an error and the program shuts down. The following is logged to the event viewer: Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 4/20/2009 Time: 1:38:57 PM User: N/A Computer: IT Description: Faulting application ntbackup.exe, version 5.1.2600.5512, faulting module ntbackup.exe, version 5.1.2600.5512, fault address 0x0001b68d. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/even... Data: 0000: 41 70 70 6c 69 63 61 74 Applicat 0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 6e 74 62 ure ntb 0018: 61 63 6b 75 70 2e 65 78 ackup.ex 0020: 65 20 35 2e 31 2e 32 36 e 5.1.26 0028: 30 30 2e 35 35 31 32 20 00.5512 0030: 69 6e 20 6e 74 62 61 63 in ntbac 0038: 6b 75 70 2e 65 78 65 20 kup.exe 0040: 35 2e 31 2e 32 36 30 30 5.1.2600 0048: 2e 35 35 31 32 20 61 74 .5512 at 0050: 20 6f 66 66 73 65 74 20 offset 0058: 30 30 30 31 62 36 38 64 0001b68d 0060: 0d 0a .. It doesn't make any sense. Why would it run manually but not let me set a schedule? I have been searching for any type of solution online for a week now to no avail. If anyone has any ideas they would be greatly appreciated. Thanks!

Run it from the server as NTbackup supports backups from UNC paths. Additionally you can enter the eventID into eventid.net and that may give you some pointers as to the error.

schedule it under an admin account not the server system account which is the default and doesn't have pc access rights. It works manually because its running under your account.

Problem solved. Some file permissions must have gotten scrambled a bit. As soon as I reset all of the permissions on the system files the program starts and runs normally. So it was a winXP issue and not a Server2003 issue. The problem may be related to an article on MSKB that detailed some steps to protect against the Conicfer virus a few weeks ago. It involved a GPO that changed some permissions on the workstations. I don't remember the details exactly. Its the only way that I can think of that permissions could get scrambled on multiple desktops at the same time. Thank you all for your support and details.