"Cannot access the path:" backup error
So, I recently started using Acronis True Image 2016 for full PC backups, and for a few weeks, it was fine no problems. Now, every time I connect my external hard drive to the computer to backup, Acronis gives the error "Cannot access the path". Can you guys help me figure out what's causing this? Thank you :)
Btw, the external hard drive is a WD My Passport Ultra, if that helps.
I haven't connected any other USB devices to my computer lately, and the drive letter is the same as it's always been. Should I change the drive letter anyways? And, how do I do that?
Are you sure the drive letter has not changed in Windows? Open Windows File Explorer and confirm that the drive shows the same letter as is shown in the True Image application.
Yes, the drive letter in Windows File Explorer is the same one as shown in True Image.
In True Image look to the right of the backup task name. You should see a \/ looking symbol. Click on that and in the menu do you see an option for validate? If yes what happens when you select it?
Alright, it's validating the backup right now. Should I just wait until it finishes?
Yes. If the task itself does not run as scheduled post back again.
Error Message During Backup
I was running a full disk backup. It had been running for several hours. Then before completion I got an error message:
"Cannot access the path E:\Entire PC (Desktop-F1365890_full_b1_s1_v2.tip"
So I stopped the backup, the drive shows up but when I try to access it I get:
"An error occured while opening the backup archive. Cannot continue the operation because the backup is corrupted, or is being used by another process, or you do not have enough premissions to perform the operation."
See attachments for screen shots of error messages.
Any ideas as to what has happened?
What type of drive is your E: drive and how is it connected to your computer?
If this is an external USB drive, then what type of USB is being used, i.e. USB 2.0 or 3.0?
Is the same standard used for both the Port and the drive?
If this is an external drive, how is it powered, i.e. from the USB port or independently with its own power source?
Please download the MVP Log Viewer from the link in my signature and check for messages in the backup task log(s) that may show more information on this issue?
Hi Steve,
Thanks for the quick response and offer to help. Here are the answers to you questions, I hope it gives you some clue as to what the problem is.
Regards,
Roy
What type of drive is your E: drive and how is it connected to your computer? - It is a WD1.0TB WD10JPVX internal HD enclosed in a Sabrent SATA to USB 3.0 enclosure.
If this is an external USB drive, then what type of USB is being used, i.e. USB 2.0 or 3.0? - USB 3.0
Is the same standard used for both the Port and the drive? Yes, HP Envy LT is USB 3.0
If this is an external drive, how is it powered, i.e. from the USB port or independently with its own power source? Powered from USB port
Please download the MVP Log Viewer from the link in my signature and check for messages in the backup task log(s) that may show more information on this issue? - Here is the last section from the Log Viewer, the sections previous to this are similar (I have run a surface scan and CHKDSK on the drive with no errore indicated):
id=60; level=4; module=485; code=35; date/time=4/6/2017 2:13:01 AM
message=Cannot access the path: E:\Entire PC (DESKTOP-FI23496)_full_b1_s1_v2.tib; line_tag=0x4D3F22948E29F1C7
Error_Code=ASMA5QHH8SmOlCI/TUNhbm5vdCBhY2Nlc3MgdGhlIHBhdGg6IEU6XEVudGlyZSBQQyAoREVTS1RPUC1GSTIzNDk2KV9mdWxsX2IxX3MxX3YyLnRpYgAkbW9kdWxlAEF0aV9kZW1vbl92c182NTgxACRmaWxlAEFrOlw2NTgxXHByb2R1Y3RzXGltYWdlclxhcmNoaXZlXGltcGxcdXRpbHMuY3BwACRmdW5jAEFgYW5vbnltb3VzLW5hbWVzcGFjZSc6OkdlbmVyYXRlR3VpRXJyb3JXaXRoUGF0aAAkbGluZQBO8AAAAAAAAAAALQAEAOxqP2pnq44dVGhlIHNwZWNpZmllZCBmaWxlIHBhdGggZG9lcyBub3QgZXhpc3QuAFBhdGgAV0U6XEVudGlyZSBQQyAoREVTS1RPUC1GSTIzNDk2KV9mdWxsX2IxX3MxX3YyLnRpYgAkbW9kdWxlAEF0aV9kZW1vbl92c182NTgxACRmaWxlAEFrOlw2NTgxXHByb2R1Y3RzXGltYWdlclxhcmNoaXZlXGltcGxcb3BlcmF0aW9uc1xhcmNoaXZlX21lc3NhZ2VfY2FsbGJhY2suY3BwACRmdW5jAEFUcnVlSW1hZ2U6OkFyY2hpdmU6OkFyY2hpdmVNc2dXcml0ZUNhbGxiYWNrUHJvY2Vzc29yOjpQcm9jZXNzV3JpdGVDYWxsYmFjawAkbGluZQBOwwQAAAAAAAAALQAEAN74ITt7dF/zVGhlIHNwZWNpZmllZCBmaWxlIHBhdGggZG9lcyBub3QgZXhpc3QuAGZ1bmN0aW9uAEFDcmVhdGVGaWxlTm9DYWNoZVcAcGF0aABXXFw/XEU6XEVudGlyZSBQQyAoREVTS1RPUC1GSTIzNDk2KV9mdWxsX2IxX3MxX3YyLnRpYgAkbW9kdWxlAEF0aV9kZW1vbl92c182NTgxACRmaWxlAEFrOlw2NTgxXGZpbGVcd2luZG93c1x3aW5udF9kaXIuY3BwACRmdW5jAEF3aW5udF9kaXI6Ok9wZW5GaWxlACRsaW5lAE7VAQAAAAAAAADw/wAA9LjtZL39KL1UaGUgc3lzdGVtIGNhbm5vdCBmaW5kIHRoZSBwYXRoIHNwZWNpZmllZABjb2RlAE4DAAeAAAAAACRtb2R1bGUAQXRpX2RlbW9uX3ZzXzY1ODEAJGZpbGUAQWs6XDY1ODFcY29tbW9uXGVycm9yLmNwcAAkZnVuYwBBQ29tbW9uOjpFcnJvcjo6QWRkV2luZG93c0Vycm9yACRsaW5lAE42AQAAAAAAAAA=
id=61; level=4; module=4; code=45; date/time=4/6/2017 2:13:01 AM
message=The specified file path does not exist.; line_tag=0x1D8EAB676A3F6AEC; hide=1
id=62; level=4; module=4; code=45; date/time=4/6/2017 2:13:01 AM
message=The specified file path does not exist.; line_tag=0xF35F747B3B21F8DE; hide=1
id=63; level=4; module=0; code=65520; date/time=4/6/2017 2:13:01 AM
message=The system cannot find the path specified; line_tag=0xBD28FDBD64EDB8F4; hide=1
id=64; level=2; module=485; code=35; date/time=4/6/2017 2:13:01 AM
message=Cannot access the path: E:\Entire PC (DESKTOP-FI23496)_full_b1_s1_v2.tib To specify another location, click Browse.: ⎂Retry//⎂Cancel//
id=65; level=2; module=485; code=35; date/time=4/6/2017 4:37:31 AM
message=Cannot access the path: E:\Entire PC (DESKTOP-FI23496)_full_b1_s1_v2.tib To specify another location, click Browse.: ⎂Retry//⎂Cancel//: User response: ⎂Cancel
id=66; level=3; module=316; code=1; date/time=4/6/2017 4:37:33 AM
message=Terminated by user.
Start= 4/5/2017 10:50:23 PM
Finish= 4/6/2017 4:37:33 AM
Total Time= 05:47:10
Roy, thanks for the further information and log file snippet.
The Error Code information just confirms what is already shown in the other messages in the log; the code data is just Base64 encoded text which when decoded says:
Cannot access the path: E:\Entire PC (DESKTOP-FI23496)_full_b1_s1_v2.tib
The specified file path does not exist.
Path E:\Entire PC (DESKTOP-FI23496)_full_b1_s1_v2.tib
The specified file path does not exist.
The system cannot find the path specified
The key factor that is likely to be at play here is that your USB 3.0 drive is being powered from the USB port and given the time period taken for the backup action, it is likely that the connection to the drive has been lost due to a timeout or sleep timer coming into play.
You said in the first post that you got an error when trying to access the drive, i.e. the backup is corrupted etc, but did you try to open the drive from within Acronis or using Windows Explorer? I suspect that the backup is considered to be corrupt simply because it is incomplete and may still be locked by the Acronis backup process until the cancel takes full effect.
Problem Found - Maybe?
Hi Steve,
I think I may have found the problem. Looking at the log file I saw a number of the " Cannot access the path: E:\Entire PC (DESKTOP-FI23496)_full_b1_s1_v2.tib " embedded in the log, and based what you surmised I am guessing there were problems accessing the E: drive and Acronis was doing a number of retrys. That would account for the longer run time. Probably at some point a retry threshold was reached and the error message was presented to the screen.
So, to experiment I first reformatted the E: drive, then plugged into a different USB port on my LT, and started a new (clean) backup, and it completed successfully in a little under 2 hours. :) I looked at the log and there were no errors. So maybe I have a slightly marginal USB port (although it seems to work for just normal wrting/reading from a connected drive)?
Being the good engineer that I was (I'm retired now), tonight I will try to confirm by reformating, plugging into the suspicious port, and running a backup to see if it fails again and/or if the log is clean.
I'll let you know the results tomorrow.
Thanks again for your help,
Roy
Roy, sounds like a good plan of attack on this issue. Hope the results show all is OK.