Error EC8F17B7 along with Error ED800012: (CRC Validation) is invalid & Error E4F3000E: Snapshot failure while using Volume Shadow Copy Service
Hi I am trying to backup a PC using SSR2013 (Desktop ed). I have created a custom backup job to run on schedule but the backup continuously fails. I find the following error in the event log afterwards: Error EC8F17B7: Cannot create recovery points for job: Drive Backup of (C:\), (D:\). Error E4F3000E: Snapshot failure while using Volume Shadow Copy Service. Please check application event log for VSS errors. Error code: VSS_E_OBJECT_NOT_FOUND (-2147212536). (UMI:V-281-3215-6071) After running the job manually, I find the following in the event log: Error EC8F17B7: Cannot create recovery points for job: Drive Backup of (C:\). Error ED800012: The internal structure of the recovery point file (CRC Validation) is invalid, damaged or unsupported. (UMI:V-281-3215-6071) I have been trying a few solutions found on the Symantec website regarding these errors, but have not received any good results. I have also not found a solution that relates to SSR2013... Thanks Zaid3.7KViews0likes16CommentsHelp booting Symantec Rescue Disk - not enough memory to create ramdisk device
I use Ghost 15 and it usually works great (I run Ghost recovery off a bootable grub4dos usb stick). I recently performed a cold backup of a PC using the Ghost 15 recovery environment. When restoring the backup from the Ghost recovery environment to the same PC, as the restore was 99% completed, I was prompted to enter an additional disk. Of course, I didn't have the disk the restore process was looking for and the restore process returned an error and did not successfully complete. I understand that this is a bug in Ghost 15 and that the restore process somehow thinks I'm restoring to a different machine and is looking for files from Symantec's PC Anywhere. So I did as has been suggested in this forum and downloaded the Symantec Rescue Disk that comes with Symantec System Restore 2013. I copied the 32-bit ISO to my USB stick and created the following entry in menu.lst: # Symantec System Recovery - Symantec Recovery Disk title Symantec Recovery Disk find --set-root /ISO/SSR11.0.1.47662_AllWin_English_SrdOnly.iso map /ISO/SSR11.0.1.47662_AllWin_English_SrdOnly.iso (hd32) map --hook root (hd32) chainloader (hd32) The iso is contiguous on the USB stick. When launching, I immediately receive the following error message: "There isn't enough memory available to create a ramdisk device." Error code is 0xc0000017 The system in question has 512MB of memory. I am able to boot the Ghost 15 ISO from the same USB stick and it's larger at 394MB while the SRD ISO is 381MB. Any suggestions?Solved3KViews2likes16Commentsthe same GUID on two computers
I have two computers with the same GUID in Altiris Agent. So I deleted them from SSR-MS, then reset Guid (AeXAgentUtil.exe /resetguid), and then restart agent. But when I checked them it had again the same new GUID. So I've found on Altiris KB some script: 'vbscript Change GUID then force client to update configuratin and send basic inventory Dim WshShell Set WshShell = WScript.CreateObject("WScript.Shell" ) Dim TypeLib, sNewGuid Set TypeLib = CreateObject("Scriptlet.TypeLib" ) sNewGUID = TypeLib.Guid Set TypeLib = Nothing sNewGuid = left(sNewGUID, len(sNewGUID)-2) ' wscript.echo " # Guid Generated " + sNewGuid WshShell.RegWrite "HKLM\Software\Altiris\Altiris Agent\MachineGuid" ,sNewGuid, "REG_SZ" WshShell.RegWrite "HKLM\SOFTWARE\Altiris\Client Service\NSMachineGuid" ,sNewGuid, "REG_SZ" WshShell.RegWrite "HKLM\SOFTWARE\Altiris\eXpress\MachineGuid" ,sNewGuid, "REG_SZ" WshShell.RegWrite "HKLM\SOFTWARE\Altiris\eXpress\NS Client\MachineGuid" ,sNewGuid, "REG_SZ" WshShell.RegWrite "HKLM\SOFTWARE\Computing Edge\Notification Server\MachineGuid" ,sNewGuid, "REG_SZ" Dim client Set client=WScript.CreateObject ("Altiris.AeXNSClient" ) ignoreBlockouts=1 sendIfUnchanged = 1 client.SendBasicInventory sendIfUnchanged, ignoreBlockouts client.UpdatePolicies ignoreBlockouts Probably it works well/better. Now in Resource Manager I see both computers. But when I click "Symantec System Recovery Details" in SSR-MS I have information that "The Symantec System Recovery configuration data is not available" What to do with this?2KViews1like13CommentsSystem Recovery 2013 error on scheduled job
Hi there. I have a huge problem on a windows XP workstation running a small "server" application. Every time the scheduled job starts, it quits with the following error: Description: Error EC8F17B7: Cannot create recovery points for job: Drive Backup of (C:\). Error EC8F03ED: Cannot create the recovery point. Error E7D1000B: Unable to make directory '//ucserver1/backup/'. Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'The requested file was not found(translated from danish)' Details: 0xE7D1000B The problem doesn't occur if I run the backup job manual. Setup: The backup job runs a backup on a USB attached drive on another server. There is full access permissions to "everyone" There is full share permissions to "everyone" Symantec System Recovery 2013 fully patched. Windows XP fully patched. What I've done so far: chkdsk /f /r Uninstalled SSR 2013 Removed all folders remotely assembling "symantec" on the computer. Also searched the hidden folders. Reinstalled SSR 2013 and created a new job. Tried the following -http://www.symantec.com/business/support/index?page=content&id=TECH179596&actp=search&viewlocale=en_US&searchid=1390506048474 Problem still occurs. The error doesn't appear after a reboot of the computer. But after a few days, it occurs again.. Funny thing is that the problem only occurs, when the job runs automatic. If I run it manually, there is no problem :-/ Plz help :-)Solved1.4KViews0likes8CommentsSSR 2013 Recovery Disk Does Not Boot
I have the SSR 2013 Recovery Disk and Have also downloaded the SSR 2013 SP2 Recovery Disk and neither will boot for over 30-45 minutes. What has gone wrong with this product. SSR 2011 works fine and boots up in a couple of minutes. With SSR 2013 it just sits at the Black Screen with theBlue Windows Logo does not show any activity until over 30-45 minutes. This is with various hardwaremostly x64based but some 32-bit also. I have also tried running it in a VM but that crashes also. Am I missing something? I having to look at another product now due to the issues with the 2013 Recovery Disk. I have a support call open with Symantec on this issue but they don't understand the issue, fob off after fob off. They have just askedme to download a tool onto the desktop!!! I don't have a desktop, the os haqs corrupted hencewhy I need the recovery disk to restore it. Sadly I'm going to have to look at another product unless this is resolved, it's a shame as I've been using it since v7.5 but this version is a disaster.915Views1like8CommentsSSR 2013 - Using command line to run a remote backup
Hello, We are migrating to Win7 from XP we can use the backup policies to run backups at scheduled times though what we would like to do is create a job in Deployment Consoleto run a script immediately on the PC's we plan to migrate that day. Has anyone tried this or know if using command line is possible to run a remote backup?874Views0likes6CommentsSymantec SSR Backup by IP address instead of Hostname
I have several Windows systems in two floors interconnected, both floors are in the same vlan, unique IP addresses but unfortunately there are a few duplicate hostnames. Can I have a centralized SSR solution in this scenario?Solved855Views0likes5Comments