Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

E0BB001B: Cannot lock volume C

Updated: 21 May 2010 | 5 comments
Basin's picture
0 0 Votes
Login to vote

I have been making backups with version 8.5 for about two weeks on my Windows Server 2003 server with out any problems.  This weekend we started recieving the message E0BB001B: Cannot lock volume C: because it contains the OS or has an active paging file.  What does this mean?

Thanks

Comments

Jacob A's picture
10
Nov
2008
0 Votes 0
Login to vote

That error typically means that another backup solution on the server is using the Symantec VSS Provider installed with 8.X.

 

Was this an upgrade from a previous version of Backup Exec System Recovery?

Basin's picture
12
Nov
2008
0 Votes 0
Login to vote

Thanks for responding!  The installation was new however one of my techs decided to istall a version of Ghost which caused some conflicts.  I deleted Ghost and rebooted the server however problems persist.  My plan is to delete and reinstall Backup Exec.

Yoann's picture
11
Feb
2009
0 Votes 0
Login to vote

I was using BESR 7 on XP SP2 since one year without any problem

I uninstalled it and then upgraded ti 8.52,

since this I have errors and cannot use BESR on system drive. ....  didnt found any fix to make it work and symantec support is useless ......

As usual, poor quality support for end users ...

 

 

Erreur EC8F17B7 : Impossible de créer des points de récupération pour l'opération : Sauvegarde du lecteur de Barracuda 1 (C:\). Erreur E0BB001B : Impossible de verrouiller le volume C:\, car il contient le système d'exploitation ou car il comporte un fichier de pagination actif. Erreur EBAB03F1 : Le volume contient des fichiers système ou des fichiers d'échange.
Détails :
Source : Backup Exec System Recovery

Jon_R's picture
23
Feb
2009
0 Votes 0
Login to vote

After you run a backup which gets this error, please run the following command from the command line in Windows and post the results;

 

vssadmin list writers

Yoann's picture
24
Feb
2009
0 Votes 0
Login to vote

Hello

 

Meanwhile, I unsinstall BESR, Live update, cleaned the registry, and whiped out all folders related to symantec and BESR

I did a new install of BESR 8.52, and now  it's working ok....  except, I can't use my upgraded Licence with it .... It stays in demo mode

my BESR is valid to Expiration Date: 8/27/2009

and I got a ID de notification: BESR8WIN-770098xx-N-24547xx to upgrade

but BESR 8.0 licence key not compatible with 8.5x,

and i didn't find any link related to upgrade from 8.x to 8.5x

Thanks for help

 

 

 

vssadmin list writers
Vssadmin 1.0 - Outil de ligne de commande d'administration du service
de cliché instantané de volumes
(C) Copyright 2000 Microsoft Corp.

Nom de l'enregistreur : 'Microsoft Writer (Service State)'
ID de l'enregistreur : {e38c2e3c-d4fb-4f4d-9550-fcafda8aae9a}
ID d'instance de l'enregistreur : {aaca7c08-c6cc-47b9-b3f5-a6dbb9594b2f}
État : [1] Stable

Nom de l'enregistreur : 'MSDEWriter'
ID de l'enregistreur : {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
ID d'instance de l'enregistreur : {56fe8b95-72f8-4234-9c5c-f431dbbacc47}
État : [1] Stable

Nom de l'enregistreur : 'Microsoft Writer (Bootable State)'
ID de l'enregistreur : {f2436e37-09f5-41af-9b2a-4ca2435dbfd5}
ID d'instance de l'enregistreur : {c0e27903-a8fd-447f-84d9-9a2edf054f43}
État : [1] Stable

Nom de l'enregistreur : 'WMI Writer'
ID de l'enregistreur : {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
ID d'instance de l'enregistreur : {3858fa86-13d5-4b58-a554-29ccd2ac2bf5}
État : [1] Stable