Invalid file reference. (0x7001A) Tag = 0xEF8B1618A4C0DE18

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 1

Hello,

Been using Acronis for years for BKUP/RECOVERY for years. Recently I have had a problem backing up. Acronis has a hit on this but provides NO solution. Does anyone know what that might be?

I have a DELL laptop and have run all of their checking software and all reports 'OK', so I am out of answers.

Thanks in advance!

PS the problem shows up like this: Invalid file reference. (0x7001A)
Tag = 0xEF8B1618A4C0DE18

PPS - I use the 2010 version

Mon, 02/28/2011 - 01:40
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 24
Comments: 3268

Hello Jan,

Welcome to our Forum, we're glad to greet you here! Thank you for finding time to report about the issue, I will be glad to help you.

Have you tried the solutions suggested in this KB article? In general, you need to make sure you're using the latest product update (if not - install it), but it also has a couple of additional tips.

In case you did, but the issue remained, please gather Acronis Info from the problem machine and send it to me, I'll be able to check what's wrong.

Let us know if you have any questions or concerns, I'll be glad to help!

Thank you.

Mon, 02/28/2011 - 16:53
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 1

Hi Yana,

Here is what I did to resolve the issue:
1. I downloaded the latest build of TC. This did not fix it.
2. Ran CHKDSK - It ran at first but then seem to hang up. This did not fix it.
3. Booted in SAFE mode. This fixed it.

Thanks for the time.

Wed, 03/02/2011 - 02:03