All client backups are failing

Event Log:

    Backup job 0 on SERVER1 did not succeed. Reason: NotConfigured

BackupLaunchpad.log:

[7660] 150825.102050.5917: BackupLaunchpad: Program.Main(): BackupLaunchpad started
[7660] 150825.102050.6138: General: Initializing...C:\WINDOWS\System32\Essentials\BackupLaunchpad.exe
[7660] 150825.102050.6407: General: Color branding started
[7660] 150825.102050.6407: General: Processing Microsoft default SKU branding colors XML
[7660] 150825.102050.6507: General: Branding colors XML parsing started
[7660] 150825.102050.6517: General: Branding colors XML parsing ended
[7660] 150825.102050.6517: General: Looking for OEM branding colors XML
[7660] 150825.102050.6527: General: No OEM informations available
[7660] 150825.102050.6527: General: Color branding complete
[7660] 150825.102050.7007: BackupLaunchpad: BackupLaunchpadControl constructed
[7660] 150825.102050.7097: BackupLaunchpad: BackupDisconnectedControl constructed
[7660] 150825.102050.7107: Backup: Trying to connect to provider Async.
[7660] 150825.102050.7117: BackupLaunchpad: BackupLaunchpadProperties: constructed form
[516] 150825.102050.7147: Backup: Waiting for connection with the provider.
[2200] 150825.102050.7737: Backup: New connection detected. Try fetching all data
[2200] 150825.102050.7947: Backup: Connected to provider Successfully
[7660] 150825.102050.7967: BackupLaunchpad: Updated status to failed
[7660] 150825.102050.7967: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Failed and error NotConfigured
[7660] 150825.102050.7977: BackupLaunchpad: Updated status to failed
[7660] 150825.102050.7977: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Failed and error NotConfigured
[7660] 150825.102050.7987: BackupLaunchpad: Updated status to failed
[7660] 150825.102050.7987: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Failed and error NotConfigured
[7660] 150825.102050.7987: BackupLaunchpad: Synchronized state
[7660] 150825.102050.8137: BackupLaunchpad: Updated status to failed
[7660] 150825.102050.8137: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Failed and error NotConfigured
[7660] 150825.102050.8137: BackupLaunchpad: Synchronized state
[7660] 150825.102053.6935: BackupLaunchpad: Updated status to starting
[7660] 150825.102053.8745: BackupLaunchpad: BackupLaunchpadControl.backupObjectModel_StartBackupAsyncCompletedEvent: StartBackupAsync ended
[7660] 150825.102053.8765: BackupLaunchpad: Updated status to failed
[7660] 150825.102053.8765: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Failed and error NotConfigured
[7660] 150825.102053.8785: BackupLaunchpad: Updated status to progress 0
[7660] 150825.102053.8795: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status InProgress and error None
[7660] 150825.102053.8795: BackupLaunchpad: Updated status to progress 0
[7660] 150825.102053.8795: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status InProgress and error None
[7660] 150825.102053.8836: BackupLaunchpad: Updated status to failed
[7660] 150825.102053.8845: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Failed and error NotConfigured

I have run Robert Pearman's Configuration Troubleshooter on the server and clients and all is showing ok.

What is going on here and how can I fix it?

• Edited by mikcon Tuesday, August 25, 2015 12:44 AM

Hi Eve,

Thank you for taking the time to reply. A short while ago I was playing around with it and I decided to repair the backups once again and this time, straight after that it started working! I had done this a few times before but it had no effect. I'm not sure what happened here but backups have started running again so I'm happy.

Kind regards

• Marked as answer by Eve WangMicrosoft contingent staff, Moderator 3 hours 18 minutes ago

Hi,                                   

I am glad to hear that the problem has been resolved.

It seems to be a suspended backup component and recovered after repairing, but unsure.

Best Regards, 
Eve Wang