Access is Denied
I'm trying to recover from a tib file but all I keep getting is an error message saying:
You are possibly trying to work with others files or folders when working with [xyz filename]
I don't understand what it is actually trying to indicate. I'm not doing anything with the file I am trying to recover as it doesn't already exist for me to do anything with.
Does it mean I cannot do anything in windows with other files or folders?
Anyone know what I need to do?
Thanks
Hi Steve,
I am using the recovery facility within ATIH 2016 to recover a folder (containing three/four files) from a tib file.
Ok, thanks for the update, the first thought is to ask if you have any Windows Explorer windows open to the drive / folder where your TIB files are held, this in case you have a lock on the file you are trying to open?
Next, try closing ATIH 2016 and then using Windows Explorer, open the folder where the TIB file is. then right-click on the file you want to recover files from and select to either Mount or Validate the image. If you Mount the image, you can copy and paste files from the image as needed, otherwise, Validate will check the file integrity is good.
Hi Steve,
There are no windows open to the drive other than the one where I am right clicking and trying to mount / verify.
After closing ATIH, I tried to verify the tib file which took about 1hr and when it had finished, ATIH just reverted to the main screen you see when you first open it. There were no errors or success indications which I could see !?!?!?!?!?
If I try to mount I get an error saying "Specified archive cannot be mounted since it contains no partitions".
It does contain something at 123GB!! If I try to recover usinf ATIH, I can see the folder structure and files which is when I get the problem described in the first post.
If you have run a validation for the problem archive file, then there will be a service_... log file for that validation in the C:\ProgramData\Acronis\TrueImageHome\Logs folder - this folder path may be hidden on some systems.
You can open the log file in any standard text editor though the format is XML. Look for a service log file for the date / time when you ran the validation action.
I've had a look in that folder and I couldn't see any log file which looked as if it contained any validation info.
I deleted all of the log files in that directory with the thought that if I re-ran the validation today, it would only contain the latest log file and one of them would be the validation.
That was wishful thinking as now everytime I run validation I get the BSOD. I do get a log though containing:
<?xml version="1.0" encoding="UTF-8" ?>
<log uuid="156649CB-8E33-469D-A872-ADC096D3A5F6" product="True Image" version="19.0" build="5634" task="EA1A78BB-366B-468A-A480-073CFF73BF02" >
<event id="1" level="2" module="100" code="2" time="1458325390" message="Operation  started manually." />
<event id="2" level="2" module="100" code="0" time="1458325390" message="Operation description: Stage Description." />
<event id="3" level="2" module="100" code="11" time="1458325392" message="Priority changed to Low." />
<event id="4" level="2" module="11" code="1026" time="1458325393" message="<bold>Validate Backup Archive</bold><endl/><tabpoint value=30><indent value=4>Location:	<indent value=10><textcolor value="navyblue">"F:\Old_Pootah_Disk_2015_07_22_13_50_52_704F.TIB"</textcolor></indent><indent value=4><endl/></indent><endl/>" />
Not sure this tells me whether it was successful or not!!
Thanks for the log file content, unfortunately it does not show a successful validation as the log ends after reporting event id 4 - see the 2 PDF documents attached - one is yours, the second is my successful validation to show the difference.
The more concerning factor is that you say you are now getting a BSOD when you attempt to run validation for the problem archive. That sounds like a more serious problem and should be investigated.
Please download a copy of the free 'Who Crashed' tool and install this, then use this to analyse the BSOD dump files that should have been created. This should give an indication of what caused the BSOD.
The other place to check is in the Windows Event Logs - you can open this by using 'eventvwr.msc' at the Windows run prompt. Look for any critical events in the log first, then look at error events.
One important point that the log file shows is that you are not using the latest version of ATIH 2016 - you are running build 5634 - the latest build is 6027 - I would strongly recommend that you download and install the 6027 version from your Acronis Account before doing anything else, just in case this problem is related to your old build version.
Crashing no longer a problem.
Tried updating to latest version but still encountered the same problems. I decided to try my 2013 version since this was the version it was created with. Although I still cannot mount, I can validate. It is a valid file, apparently.
I've tried recovering the file to a different location on the HDD to see whether it is a problem recovering to the desktop, still the same problem. Likewise, I tried to recover to the portable HDD the tib is located on, but again the same error.
Not very encouraging or an endorsement of Acronis products. I will be seriously considering whether I use Acronis products after this. I've backed up using some "professional" tools only to find I am unable to recover. To all intents and purposes, I might as well not backed up in the first place.
At this point I would recommend going directly to the Acronis web site http://www.acronis.com/ and follow the options to Contact Support as you have a Recovery Issue here that entitles you to receive help in getting your system working again. You will need to login to your Acronis Account and have registered your True Image product.
See http://forum.acronis.com/forum/111708#comment-335853 for a recent confirmation of free support for recovery issues by one of the Acronis Support Engineers on these forums.