'Error E7B70001: Win32/Win64 API true failed,' occurs when attempting a backup with System Recovery while a disk is in an offline mode.

book

Article ID: 100007423

calendar_today

Updated On:

Description

Error Message

Error EC8F17B7: Cannot create recovery points for job: Drive Backup of source (E:\).
Error E7B70001: Win32/Win64 API true failed.

Error EBAB03F1: OS error 2147755013. 0xE7B70001 (System Recovery)
 (UMI:V-281-3215-6071)

 

Windows events:

 

Log Name:      System
Source:        VDS Basic Provider
Event ID:      1
Task Category: None
Level:         Error
Keywords:      Classic
Description:
Unexpected failure. Error code: 2@01010013

Log Name:      System
Source:        Ntfs
Event ID:      57
Task Category: (2)
Level:         Warning
Keywords:      Classic
Description:
The system failed to flush data to the transaction log. Corruption may occur.

Log Name:      System
Source:        Microsoft-Windows-FilterManager
Event ID:      3
Task Category: None
Level:         Error
Keywords:     
Description:
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xc03a001c.


Log Name:      System
Source:        Disk
Event ID:      51
Task Category: None
Level:         Warning
Keywords:      Classic
Description:
An error was detected on device \Device\Harddisk2\DR2 during a paging operation.

 

Cause

Suspect disk enumeration issue on the client while a drive is in offline state and still connected.

Resolution

Workaround: Enabling the offline drive (i.e. making the drive online) through Window's Disk management utility or completely disconnecting the offline drive.

 

 

Issue/Introduction

Attempting a backup with System Recovery of a disk while another disk is in an offline state generate the error and Windows events listed below during the snapshot phase (i.e. the first 5% of the backup job) and fails the backup. This error occurs with either recovery point set or independent backup jobs, including those jobs where the offline drive was not added. Enabling the offline drive (i.e. making the drive online) or completely disconnecting the offline drive corrects the issue.