
This has been fixed
This article applies to:
- Acronis Backup & Recovery 10 Advanced Server
- Acronis Backup & Recovery 10 Advanced Server - Small Business Server Edition
- Acronis Backup & Recovery 10 Advanced Server - Virtual Edition
- Acronis Backup & Recovery 10 Advanced Workstation
- Acronis Backup & Recovery 10 Server for Windows
- Acronis Backup & Recovery 10 Workstation
Symptoms
- Using Acronis Backup & Recovery 10 Agent for Windows, you run a backup or validation task;
- The backup task completes successfully. In the operation log, there is a warning:
Failed to open the archive by ID

Cause
This is a GUI issue. This message should be logged internally, and not in operation logs.
During a backup or other operation with a backup archive Acronis Managed Machine Service parses the contents of the .meta folder in the backup location and compares it with the actual TIB files in the vault. Warning Failed to open archive by ID appears when an inconsistency between the .meta folder and the actual TIB files is found and fixed.
Solution
(!) This has been fixed and the fix is available in the latest build of the product. See Installation of the Latest Update of an Acronis Product.
This warning can be safely ignored. The backup archive itself is not affected.
To work around without installing the new build, you can eliminate this error message by replacing the product's DiskBundle.dll library with an updated DLL that has the fix:
- On the machine with the Acronis Agent for Windows where you receive this error, go to Start-Run -> services.msc -> and stop Acronis Managed Machine Service;
- Rename DiskBundle.dll to DiskBundle.dll.old in the following folder:
- Windows 32 bit: C:\Program Files\Acronis\BackupAndRecovery\
- Windows 64 bit: C:\Program Files (x86)\Acronis\BackupAndRecovery\
- Download diskbundle.zip and extract it. Place the extracted DiskBundle.dll in the following folder:
- Windows 32 bit: C:\Program Files\Acronis\BackupAndRecovery\
- Windows 64 bit: C:\Program Files (x86)\Acronis\BackupAndRecovery\
- Again go to Start-Run -> services.msc -> and start Acronis Managed Machine Service.
More information
This has been fixed.