Backup failed with error "Access is Denied"
Hello,
I haven’t made an incremental backup to the cloud for one year, last successful incremental backup was using the latest version of Acronis True Image at that time. And today I upgraded to the Acronis Cyber Protect Home Office to the latest version, and initiated another incremental backup to the cloud, but it failed with error "Access is Denied".
Any idea how I could resolve this issue? Thank you for the help!
the logging detail is below:
cancellable |
true |
cancelRequested |
false |
completedAt |
2023-01-05T04:49:45Z |
context |
{ "BackupPlanName": "DESKTOP", "CommandID": "D332948D-A7A9-4E07-B76C-253DCF6E17FB", "Specific": "Business", "_runtime": { "bytesProcessed": 2957550919680, "bytesSaved": 2957550919680, "sourceStamp": 6827487 }, "isLegacy": true, "title": "Activity name" } |
enqueuedAt |
2023-01-05T04:49:09Z |
executor |
{ "id": "4228c465-99f6-4831-843a-df6a0132dab1", "clusterId": "" } |
id |
1285492228501622800 |
idString |
1285492228501622784 |
issuer |
{ "id": "", "clusterId": "" } |
policy |
{ "id": "143bcef2-60d6-4d26-ace5-f99fe96b7252", "type": "backup", "name": "DESKTOP" } |
priority |
normal |
queue |
legacySync |
resource |
{ "id": "2FF7BC07-F086-45F9-B177-0715CF6E648E", "type": "instance", "name": "DESKTOP" } |
result |
{ "code": "error", "error": { "domain": "environment", "code": "AccessDenied", "reason": "AccessDenied", "context": { "_src": { "code": 262164, "fields": { "$module": "ti_demon_vs_40173" }, "src": { "file": "c:\\jenkins_agent\\workspace\\common\\ati-main-win-ati\\937\\home\\backup_worker\\impl\\backup_worker.cpp", "func": "`anonymous-namespace'::ReturnCodeToError", "line": 193, "tag": "0xaa33a143c434a60f" }, "suberror": { "code": 262164, "fields": { "$module": "archive3_adapter_vs_40173" }, "src": { "file": "c:\\jenkins_agent\\workspace\\common\\ati-main-win-ati\\937\\archive\\ver3\\adapter\\error.cpp", "func": "`anonymous-namespace'::ConvertArchive3Error", "line": 61, "tag": "0xc8d8731ce106f9cb" }, "suberror": {}, "text": "访问文件被拒绝。", "types": { "$module": "A" } }, "text": "访问文件被拒绝。", "types": { "$module": "A" } }, "cause_str": "访问文件被拒绝。", "effect_str": "访问文件被拒绝。" }, "kbLink": { "build": "59", "lineTag": "0xC8D8731CE106F9CB", "os": "Windows", "product": "", "serCode": "0x00040014+0x00040014", "version": "1.0" } } } |
startedAt |
2023-01-05T04:49:09Z |
state |
completed |
tenant |
{ "id": "244200", "uuid": "b4fa396d-6980-4a8e-b0a2-395ffc123c11", "name": "YIYANG PAN (ypan91@gmail.com)", "locator": "/1/244196/244200/" } |
type |
D332948D-A7A9-4E07-B76C-253DCF6E17FB |
updatedAt |
2023-01-05T04:49:47.782165038Z |
uuid |
8ba62609-3e43-44e5-9524-7293add8b2f9 |


- Anmelden, um Kommentare verfassen zu können

Hi Steve,
I am using the personal version, ACPHO.
thank you
- Anmelden, um Kommentare verfassen zu können

Sorry but I do not recognise the format and content of the log information that you posted above for how ACPHO logs normally look?
I would suggest using the MVP Assistant tool to review the logs to see if there are errors there that would inform why your backup is failing?
Download a copy of the MVP Assistant log viewer tool and use this to look at the logs to see if they show any issues during the operation process?
The latest version of the new log viewer tool is at the link below.
MVP Assistant - New 2.0 with Rescue Media Builder (New Version 2.3.2) BETA Version 2.4.0.1 available, see posting below.
If you have Disks & Partitions backups created on ATI 2020 or later using .tibx files, then look in the Backup Worker logs.
If you have Files & Folders backups using .tib files (or Disk backups from earlier versions using .tib files) or using Cloning then look in the Demon logs.
Other logs are shown by the MVP Assistant under the 'Active Logs' heading of the Log Viewer page of the Assistant.
The Schedule2 log contains information related to scheduled task but is one of the more difficult logs to read / work through.
The log files should be zipped to preserve their original file names if sharing in the forums and would need to be less than 3MB in size, otherwise you would need to share the zip file via a Cloud share service such as OneDrive, Dropbox etc.
Are you able to create local backups to an external HDD or network drive?
If only backups to the Acronis Cloud are failing, then I would suggest raising this directly with Acronis Support as they can check the server side of the operation and your account etc.
- Anmelden, um Kommentare verfassen zu können

Hello Yiyang.
To troubleshoot the issue the following KB must be followed:
https://kb.acronis.com/content/61489
Please check the following solutions:
- Grant the SYSTEM Windows account, the current Windows user account (local backups) or NAS account (if the error message refers to a file/folder on a NAS) full control rights over the file/folder indicated in the error message
- Acronis True Image 2018 and earlier versions: see https://kb.acronis.com/content/61362
- Reboot PC/Mac and NAS (if used) to lift any locks that other applications may have put
- Right-click the disk with backup source, select Properties – Tools – Check, enable the option to automatically correct the found errors (if this option is present) and run the check/scan.
- If the error message references a NAS, run the check using NAS control panel.
- Find which folder or folder exactly cannot be accessed. If the path to it is not displayed in the product’s GUI, look into the full log using Log Viewer and find what file/folder cannot be accessed. Try opening or copying the file/folder in question. If the operation fails – attempt deleting it. If the deletion fails, the file/folder must be corrupted: try deleting it using this method https://www.technorms.com/9240/delete-undeletable-files-easy
If you have any questions regarding the issue please contact our support line with the results of those troubleshooting steps https://kb.acronis.com/content/8153
Hope this helps!
- Anmelden, um Kommentare verfassen zu können