SSR 2013 SRD Fails Boot on system with PERC H310 Raid Controller
I'm running SSR 2013 on a Dell 64 bit Precision T3600 independent workstation with a Xeon ES-1650.0 CPU, 16 GB of RAM and containing a PERC H310 Raid adapter that controlls two 1 TB HDs currently running as independant C: and D: drives (i.e., in non-RAID configuration). 2013 succdessfully backs up the C: (boot) drive to D: in weekly sets with offsite copy. However, attempting to restore C: from image using the 2013 SRD runs into an immediate probllem. When attempting to boot from the CD/DVD drive (preceded by the H310 boot from bios), even before the Windows logo appears, I get a blue screen stating: "Your PC needs to be repaired. There isn't enough memory available to create a ramdisk device. Error Code 0xC00000017." Attempting to use Lights Out produces the same result.. I attempted to customize the SRD with the H310 driver (percsas2.sys), but the SRD Wizard would not accept the .sys file. So I have two questions: 1. Could the problem be caused by something other than the H310? 2. If the probllem is the H310 controller (none of my other systems without controllers have SRD recovery problems), is there a fix short of removing the H310? -- Jim
Issues With Symantec Recovery Disk
Hi, I'm having serious problems with the symantec recovery disk. We are using Symantec System Recovery R2 Management Solution. PRevious to the R2 upgrade restores were tested using the downloaded recovery disk and everything worked fine now however I cant seem to get a test restore working. I'm trying to a test restore on a Dell Poweredge 2850 which is running Server 2008 R2. I've created so many recovery disks I'm going insane. The first issue I experienced was that the 64bit recovery disk would not boot this server after testing this disk on other servers I logged a call with Symantec who got me to test the disk on a PC and it worked... So I tried the 32bit disk and it boots properly andf I am able to get to the recovery utility. So now the main issue I am experiencing is that when I try to do the restore the target drive is always coming us as Invalid. At first I assumed thta this was because I had created the recovery disk on our management solution server which is a VM so the disk didnt contain the relevant drivers for the server so I went to the server and tried to edit the ISO, but because the server is running a 64 bit OS I cant edit the 32bit recovery disk ISO... I tried editing the 64bit ISO, but that still wont boot. So next I installed a full version of Symantec system recovery on a Windows 8.1 PC with a different license meaning I didnt have to create the recover disk through the management solution. Once again only the 32bit disk would boot the server and once again the target drive location comes up as invalid when I try to do the restore. This time I ran the driver validation tool on the server and it came back as all drivers installed, but I still cant do a restore. I still cant edit the iso because its a 64 bit server and 32bit ISO. I've tried adding in the perc 4 raid driver once in the restore environment and that doesnt work. So now I'm stuck, I cant work out if the problem is driver related, or because the server is built using MBR, but the restore file location is saved on a volume that is GPT.
the 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?
Can't selected drives on selected computers
Hello everybody, I use product Symantec System Recovery 2013 Management Solution installed on server 2008 R2 SP1. I have several backups policy configured which run well.I didn't have this error before. But, I can not select the desired drived when I create a new backup policy. When I click on All drives on selected computers, It appears a blank page with error : ################################################################################ Symantec™ System Recovery 2013Management Solution An unexpected error has occurred in the application. Forfurtherdetails, see Altiris Log Viewer. ################################################################################ Thanks for your response Samir
First Backup image to external HDD getting Error ED800012 SSR 2013
Hello All i have a problem with one home user using SSR 2013.We have a policy for home users to execute a backup job at 12:45 each day to an external HDD. it works fine except for one user that is getting the bellow error each time. Error EC8F17B7: Cannot create recovery points for job: LOCAL USB. Error ED800012: The internal structure of the recovery point file (CRC Validation) is invalid, damaged or unsupported. any ideas?Symantec System Recovery 2011: Error EC8F17B7: Error EC8F03ED: Error E7D10041: Error EBAB03F1
I have a problem with my SSR 2011 server/client setup. I have a total of 12 computers that are supposed to be backing up to my SSR server. At the moment only two of them are backing up. Yet the SSR server is reporting that3 are backed up. One of the 12 computers, I know for a fact that the SSR 2011 Client and the Altiris Agent installed on it, the server is reporting that the SSR 2011 client is not installed and is also not backing up. The remaining computers are all sending errors back to the server every night. Here is one of the emails I get every night when the backup job kicks off. Date: 4/2/2014 23:37:32 PM Notification Type: Error Priority: High Description: Error EC8F17B7: Cannot create recovery points for job: Backup of All Drives. Error EC8F03ED: Cannot create the recovery point. Error E7D10041: Unable to establish a network connection to \\txossr\backups. Error EBAB03F1: You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the computer name and try again. Details: 0xE7D10041 I really need to get this problem fixed so these machines are being backed up.