Forum Discussion
- JWKLevel 4I found this in the Ghost 10 documentation.When trying to perform a backup operation, Norton Ghost reports, "Error E0BB0147: The operation 'Snap Volume' is not currently enabled for this Volume." One of the following may cause this error message with the SymSnap.sys driver:- The driver does not load properly during the Windows startup process.- The driver is not properly registered in the Windows registry.- The driver does not exist in the %SystemRoot%\System32\Drivers folder To resolve the problem, check the following:- Confirm that SymSnap.sys exists in the %SystemRoot%\System32\Drivers folder.- Confirm that SymSnap appears in System Information > Software Environment > System Drivers.
- JWKLevel 4Has anyone else seen this?This is still a problem.
- TMurfetLevel 3Yes I am seeing this with a default install of BESR 7.0. on a Dell 2650 Server with Win 2003 R2 SP2. As far as I can see the symsnap.sys driver is not installing or being registered at all. The only Symantec document I can find only states what I have stated here. No help on how to fix this.Since we rely on this product for all our servers it looks like version 6.52 will be the last version we use. Unless Symantec steps forward and provides me with a solution.Cheers, Anthony Murfet.
Message Edited by TMurfet on 06-07-200701:00 PM
- TMurfetLevel 3OK I have an answer for this problem. I cannot believe the solution though. There is a batch file located at "systemdrive\Program Files\Symantec\Backup Exec System Recovery" called "Fixinstall.bat" that registers "SymSnap.sys" and after a server re-start the problem is gone.Why is this not mentioned in the readme file?Anthony Murfet
- JWKLevel 4My problem is that the install seems to hang and it never installs all of the files correctly. I am waiting for support to get back to me.
- Did you ever get an answer as to why it hangs? It does for me, too. If I kill it, it seems like it has completed because the program comes up but I get the same error you've mentioned in an earlier post.
- Aimee_BarborkaLevel 3Linda,I'm not sure what would cause it to hang. If it's towards the end of the install it's attempting to register the services. If you run the fixinstall.bat does it fix the problem?Thanks,Aimee
- Cookie_2Level 2Anyone got a solution to this yet? I've just uninstalled Live State v6 and put BESR v7 on a W2K3sp1 box and it won't install properly. The symsnap.sys install fails everytime.
- I can across the same error and I copied all of the .sys files from:C:\Program Files\Symantec\Backup Exec System Recovery\Shared\Drivers\win32\win32 andC:\Program Files\Symantec\Backup Exec System Recovery\Shared\Drivers\win32\x86\x86to C:\WINNT\system32\drivers, restarted the computer and the error no longer comes up.
Message Edited by AJ on 07-14-200701:04 PM
- Cookie_2Level 2Cheers. That's similar to how it's now (hopefully) been fixed.I raised an incident with Symantec and the advice received was...1. Uninstall2. Run a remove batch script to expunge all traces of BESR v73. Run a utility to remove any remainders of Live State Recovery v64. Reinstall(script & utils supplied by them)This still failed on the symsnap.sys install. Killed the msiexec, logged out and back in, and "completed" install.Symantec then advised this:1. Copy Symsnap.sys, V2iMount.sys, VProEventMonitor.sys and wimfltr.sys from C:\Program Files\Symantec\Backup Exec System Recovery\Shared\drivers\win32\win32\ to C:\Windows\system32\drivers\
2. Run FIXINSTALL.BAT from C:\Program Files\Symantec\Backup Exec System Recovery\
3. Reboot the systemAfter doing this, I've successfully taken an image.For info, when I was installing on this server, I didn't uninstall LSR first. The BESR installer detected it and did the uninstall, rebooted, then carried on. I had another server to upgrade and on that one I uninstalled LSR first, rebooted and then installed BESR and it worked with no problems.
Related Content
- 14 years ago