07-05-2009 06:08 AM
While running the weekly scheduled back up of Drive C, towards the end of the run, at about 75%, the backup stopped and I got the following error message:
Unable to write to file
Error EBAB03F1 The process cannot access the file because another process has locked a portion of the file
I followed the recommended fix process at the following page:
Run the Symatec Admin tool, restarted the computer, run a full system scan (with McAfee) and I run again a backup.
Same problem emerged at about 77% of the run.
I am running Norton Ghost 12.0 Version 22.214.171.124804 with Windows XP Professional, Version 5.1.2600
Did some search on previous postings but I could not locate fixes for similar problem. Any suggestions of how to fix the problem please?
Solved! Go to Solution.
07-10-2009 11:13 AM
A couple questions.
Have you been able to create a backup at all?
Does this error occur when creating a base or incremental backup or does it not matter?
What are you backing up to (what is the destination)?
Does it list a file or folder location?
07-10-2009 06:18 PM
Thank you Erik for responding to my enquiry,
I have been using Ghost 12 for almost two years without any problem. I am doing backup of C drive weekly and Document back up on a daily basis. Document back up continues without any problems; it has been the Computer back up that has been giving the error message since last week.
I am doing incremental backups; have not tried a base back up.
I am backing up onto a Samsung SP2514N external hard drive.
Full details of error report are: (When it first occurred)
Error EC8F17B7: Cannot create recovery points for job: My Computer Backup. Error E7D1001F: Unable to write to file. Error EBAB03F1: Insufficient system resources exist to complete the requested service.
Subsequent two attempts to re-run back up produced the following identical reports:
Error EC8F17B7: Cannot create recovery points for job: My Computer Backup. Error E7D1001F: Unable to write to file. Error EBAB03F1: The process cannot access the file because another process has locked a portion of the file.
Just a thought that may or may not have anything to do with this problem.
I was away on holidays for about 6 weeks, when the computer was idle, with no backups. Since then two incremental backups were OK, and it was the third that failed. Could the 6 weeks gap between incremental backups have anything to do with this?
Any assistance would be appreciated.
07-13-2009 09:35 AM
Not likely due to the lapse in time.
I'd take a look at your available resources. Try to trim down your running tasks. If that doesn't work, it's possible the reconciliation (which is resource intensive) may be what's happening. Is Windows set to manage your virtual memory settings? How much RAM do you have?
07-13-2009 09:06 PM
I usually run Ghost backup of C drive with no other programs running simultaneously, other than MacAfee.
I have 3 GB of RAM running at 2.8 GHz.
I did reset for Windows to manage virtual memory settings. (Was set at specified parameters, when and why I am not certain)
I re-run Ghost for C Drive backup and it failed again.
Error report, similar to previous reports:
Backup. Error E7D1001F: Unable to write to file. Error EBAB03F1: Insufficient system resources exist to complete the requested service.
Source: Norton Ghost
Some other information that may be of relevance:
During running of the backup I monitored CPU usage via Windows Task Manager and it was running from about 20% or lower at times, to mid to high 40’s.
Any other suggestions?
I really appreciate you help! Thanks.
07-14-2009 09:17 AM
Go to services.msc and check for the following services:
Norton Ghost Service (automatic and started)
Symantec SymSnap VSS Provider (automatic)
SymSnap Service (automatic and started)
If those are correct, go to a command prompt and type the following:
vssadmin list providers
Confirm that for the following:
Symantec Software VSS Provider
Microsoft Software Shadow Copy Provider 1.0
are both showing:
State:  Stable
If the Symatnec SymSnap VSS Provider is not stable or shows an error (or is missing) go to the steps to re-register the VSS provider. If any other are not stable or show an error contact that provider's manufacturer (MS for example).
How many partitions do you have? You may need to clear some contiguous space. What percentage free do you have on C?
Another option to try is the following (re-register SymSnap VSS Provider steps):
Go to a command prompt
cd "\Program Files\Norton Ghost\Shared\Drivers"
VssProviderInstall.exe -unregister "Symantec SymSnap VSS Provider" "Symatnec SymSnap VSS Provider"
VssProviderInstall.exe -register "Symantec SymSnap VSS Provider" "VSS_2003.dll" "Symatnec SymSnap VSS Provider" "Symatnec SymSnap VSS Provider"
Start the VSS Service in services.msc
Let me know if that works.
07-14-2009 07:59 PM
Thanks Erik, looks like we are getting somewhere.
In services.msc I checked the following services:
Norton Ghost Service (automatic and started)-OK
Symantec SymSnap VSS Provider (automatic)-Not there!
SymSnap Service (automatic and started)- Not there!
In C:\Program Files\Norton Ghost\Shared\Drivers - the file VssProviderInstall.exe is not there!
What does all that mean?