Error: E0BB001B: Cannot lock volume \\?\Volumevolume name\ because it contains the OS or has an active paging file. This operation cannot be performed while Windows is running" "Error E0BB0147: The operation 'Snap Volume' is not currently enabled"

Article:TECH85088  |  Created: 2008-01-21  |  Updated: 2009-01-18  |  Article URL http://www.symantec.com/docs/TECH85088
Article Type
Technical Solution

Environment

Issue



Error: E0BB001B: Cannot lock volume \\?\Volumevolume name\ because it contains the OS or has an active paging file. This operation cannot be performed while Windows is running" "Error E0BB0147: The operation 'Snap Volume' is not currently enabled"

Error



Error "E0BB001B: Cannot lock volume \\?\Volumevolume name\ because it contains the OS or has an active paging file"
"This operation cannot be performed while Windows is running" "
Error EBAB03F1: Access is denied.
Error E0BB0147: The operation 'Snap Volume' is not currently enabled

Solution



This issue is resolved in BESR 8.03. Please update BESR to this version.  If the error is actively occurring on the system, it is recommended that the previous version of BESR be uninstalled, the system rebooted, and 8.03 installed. This ensures that any affected files that may have been 'locked' by the non-BESR application(s) accessing them are properly installed.

Please use the feedback section of this article to report the outcome of upgrading to 8.03.

***The following information is for versions previous to 8.03 and should be used when it is not possible to upgrade to 8.03.***

3rd party backup software may be conflicting with the Symantec VSS Provider to create a snapshot. To test this, remove all 3rd party backup software from the system and reboot. Although this is the primary reason for this error, the methods below are all inclusive for all possible causes. If the error occurs during a restore, it's possible that the image itself is corrupt. Create a new image file by editing the job and putting a check in 'Verify Image File After Creation' to ensure a valid image.  

This may also occur only after upgrading to version 8.x or later. To  repair BESR, run \Program Files\Symantec\Backup Exec System Recovery\FIXINSTALL.BAT from Windows. (reboot required)


Method 1 (preferred):
  • If the solution is not below, contact the 3rd party backup software company for instructions on how to use only the Microsoft VSS Provider.
  • TIVOLI TSM: 1) Upgrade to TSM version 5.5.1 or later (uninstall previous versions and reboot before installing 5.5.1). 2) After installing 5.5.1, append the .opt file with the line testflags vsssystemprovider and save the file. 3) Remove all previous images and reboot server to reset services. 4) Create BESR backups.
  • ULTRABAC: Upgrade to the latest version and follow the instructions on using the Microsoft VSS Provider.
  • BACKUPEXEC FOR WINDOWS SERVERS: Go to Settings-->Advance Open File. Select 'Use Advanced Open File Option'. Enable 'Microsoft Volume Shadow Copy Service (Windows 2003 and later') and 'System - Use Microsoft Software Shadow Copy Provider' as the snapshot provider.

Method 2:
  • In BESR, create a second backup job that is identical to the job that is failing.
  • Schedule that backup to run 30 minutes after the original job.
  • Ensure that both jobs are outside of the window when 3rd party backup software may run. Do NOT allow any other backup software to run or be scheduled to run within that 30 minute window.
  • If the second job is successful, the first failure caused the Symantec VSS Provider to "unsnap" and become available for the second job. This can also be tested by manually running a failed job after that job has failed but before any 3rd party backups are creative.

Method 3:
  • Check the properties of the SymSnapService.exe in the services console. Ensure that the path in the property page is \Program Files\Symantec\Backup Exec System Recovery\Shared\Drivers\SymSnapService.EXE. If a change is required, reboot to ensure that the service is started properly.
  • Ensure that the two VSS services "MS Software Shadow Copy Provider" and "Volume Shadow Copy" are set to automatic and started in the services console. If the status is changed, run \Program Files\Symantec\Backup Exec System Recovery\FIXINSTALL.BAT from within windows after the required reboot.

Method 4:
  • Browse to C:\Program Files\Symantec\Backup Exec System Recovery\Shared\drivers\win32\win32\ and copy Symsnap.sys, V2iMount.sys, VProEventMonitor.sys and wimfltr.sys from that location to C:\Windows\system32\drivers\
  • Double-click on C:\Program Files\Symantec\Backup Exec System Recovery\FIXINSTALL.BAT file.
  • Reboot and retest.

Method 5:
  • Open a command prompt (Start > Run > 'CMD')
  • From the command prompt, navigate to the \Program Files\Symantec\Backup Exec System Recovery\Shared\Drivers directory.
  • Type "SymSnapService.exe /service"
  • Run backup.

This is an ongoing issue that Symantec Corporation is currently investigating. Please subscribe to this article to receive any updates, patch, or hotfix notifications on this issue. Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests. Symantec's plans are subject to change and any action taken by the customer based on the above information or the customers' reliance upon the above information is made at their own risk.

Customers can refer to this Tech Note article which discusses this issue. A link to a patch or hotfix download, if applicable, will be added to this document when it becomes available.  Please be sure to refer back to this Tech Note periodically as any changes to the status of the issue will be reflected here.

Supplemental Materials

SourceETrack
Value1280949
Descriptionerror "E0BB001B: Cannot lock volume \\? \Volumevolume name\ because it contains the OS or has an active paging file".

SourceUMI
ValueV-281-187-27
DescriptionError: E0BB001B \\?\ Cannot lock volume and\or Error E0BB0147: The operation 'Snap Volume' is not currently enabled" when attempting to backup or restore.


Legacy ID



304128


Article URL http://www.symantec.com/docs/TECH85088


Terms of use for this information are found in Legal Notices