SreEula.exe - System Error when booting 2013 R2 SRD
Hi all. I have had a support ticket open on this now for almost two weeks, with no luck. I have 2 issues. Dell Poweredge T420. Intel Xeon E5-2450 2.1. 16GB RAM. Windows Server 2012 R2 Std. System Recover 2013 R2 w/ current MS ADK installed. All Windows updates installed, and Live update ran. 1. When trying to create a "Typical" SRD, I am only offered "German" as a language selection. 2. More imporant issue: I cannot boot the Advanced 64-bit SRD after seemingly successfully creating it in English. Booting starts out fine. Blue Windows logo...white spinning in process icon. I get the symantec boxes for loading drivers, checking system requirements, network confguration, but then I get an error box titled: "SreEula.exe - System Error" . The message is: "The program can't start because oledlg.dll is missing from your computer. Try reinstalling the program to fix this problem". I have tried repairing, uninstallling and re-installing the software multiple times, but always get the same error. I haven't gotten anywhere with tech support. Anyone with any ideas?? Thanks Mike
SSR 2013 Trial - VSS_E_INSUFFICIENT_STORAGE error
Just downloaded SSR 2013 trial. (I was a Ghost 15 user, but upgraded to Windows 8 so can no longer use Ghost.) On my first attempt to do a backup of my drive, I got a VSS_E_INSUFFICIENT_STORAGE error. A bit of online research made me think I had to go to System Properties|System Protection and increase the amount of disk space available for system protection, which I did. I increased it from about 9GB to about 100GB. That did not help. FWIW, my hard drive is about 923GB, with about 760GB free. Any guidance? Many thanks. KenWindows Server 2012 R2 UEFI Restore Impossible?
I'm trying to do something that is dead simple, but frustratingly it's killing me... One little thing, just trying to backup and restore Windows Server 2012 R2 on an Intel i7 PC that's in UEFI mode with GPT partitions on a SATA SSD drive. Symantec System Recovery 2013 SP2 x64 v11.0.2.49853 has no problem going through the paces of restoring the backup, but afterward Windows fails to boot. I even went to the extent of wiping the C drive (and all the partitions), reinstalled WS2012 R2 Data Center GUI (nothing else except a network driver and SSR), backed up freshly installed WS2012 R2 to an external USB drive using SSR installed inside Windows, wiped the C drive (and all the partitions) and restored the backup, but all that effort didn't matter. PC still won't boot Windows. I also tried restoring the 100MB EFI Partition first, followed by the operating system and Recovery partitions, still no help. The only odd thing I see is inside the WinPE SRD, About - Symantec System Recovery Disk shows versions that seem old even though it was just extracted from the latest v11.0.2.49853 download zip file (although the SRD .iso file date of 12/15/13 is older than the SSR SP2 11.0.2 update that supposedly fixed UEFI problems). Symantec System Recovery Disk Symantec Recovery Toolkit 11.0.0 Version 11.0.0.49496 Copyright 1994-2012 Please scroll down to access my troubleshooting documentation "Symantec System Recovery 2013 x64 SP2 v11.0.2.49853 UEFI Restore Problem.pdf" with a detailed collection of photos showing the entire backup and restore process. Do you see anything usual or something that I'm doing wrong?Please help because obviously I am unhealthily obsessed with this problem! ;-) Thanks! FWIW, I have reviewed these articles, comments and tips about SSR and restoring UEFI partitions: http://www.symantec.com/business/support/index?page=content&id=HOWTO84141 http://www.symantec.com/business/support/index?page=content&id=TECH177792 http://www.symantec.com/business/support/index?page=content&id=TECH128386 http://www.symantec.com/business/support/index?page=content&id=TECH207176 http://www.symantec.com/business/support/index?page=content&id=TECH200291 http://www.symantec.com/business/support/index?page=content&id=TECH200293 https://www-secure.symantec.com/connect/forums/ssr-201020112013-and-restore-anyware-uefi And, tried these suggestions too: https://neosmart.net/wiki/0xc0000225/
Database named "RollbackSnapshotTempDB" left after System Recovery 2013 backup
We have a Windows Server 2008 R2 server with SQL Server 2008 R2 x64 installed. We have been using Backup Exec 2010 to perform Full and Transaction log backups of the databases in our SQL server, and System Recovery 2010 to backup the entire server. A couple weeks ago we upgraded System Recovery 2010 to 2013 and we noticed our Backup Exec 2010 jobs started failing. After investigating we discovered several databases named "RollbackSnapshotTempDB" were piling up. We tried to right-click the DB and go to properties but received an error message. The SQL logs showed a lot of errors related to those "RollbackSnapshotTempDB" databases, such as: Date7/2/2013 6:07:37 AM LogSQL Server (Current - 7/16/2013 8:38:00 AM) Sourcespid400 Message The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x00000053fc2000 in file '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy11\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\XXXXXX.MDF'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. And: Date7/2/2013 6:07:37 AM LogSQL Server (Current - 7/16/2013 8:38:00 AM) Sourcespid400 Message Error: 823, Severity: 24, State: 2. If I go into the SQL Server Management Studio and and try to delete the "RollbackSnapshotTempDB" databse I receive an error that says "Cannot drop the database because it is being used for replication". However if I take the "RollbackSnapshotTempDB" database offline then I can delete it, and the next Backup Exec 2010 SQL backup job will complete successfully. These errors seem to indicate a file system problem, however a CHKDSK shows no problems. We have rebooted the server as well with no change. I have googled this issue until I'm blue in the face and have not found any solutions. Does anyone have any ideas? Here are more details on the server: Virtual Server running on ESXi 5.1 Update 1 Physical host is HP Proliant DL380 G6 Storage provided by HP LeftHand iSCSI SAN Server 2008 R2 with all Windows Updates applied SQL Server 2008 R2 with all Windows Updates applied Server has two vCPU's and 12GB of RAM C: drive has 21GB free D: drive has 88GB free (D: is where all the SQL data files are stored)
Restore UEFI based sever
Hi Forum I have a Windows 2008 R2server with UEFI . The server has 2 partitions - one system EFI partition and one partition with OS. Im using SSR 2103 to make an image and tries to restore this to another server with UEFI. Restores with no error , but OS never starts up Any ideas ? regards Peter
Backup/Restore Dell Optiplex 390
I created a backup of my Dell Optiplex 390 and there are 3 total files. A Dell File, A Recovery File, and the C Drive. When I boot into the SSR 2011 I am clicking Backup Recovery then clicking next and I am loading the files in this order. (I am deleting the c drive partition before laying down the images) 1.Dell File 2.C Drive 3.System Recovery (making it bootable option checked) Am I doing this wrong? Does anyone know the correct order to lay down the images, and what options I need to have checked when doing a recovery on this machine? So far I have gotten a missing boot file error then telling me to ctrl+alt+delete+, The error I have gotten the most is a black screen with a blinking cursor...... I am stumped on what options may need to be checked within the 3 different files and which order to lay them down. Any and all support is much appreciated, if you need more details please let me know what you need. Thanks, Joshua
Backup failing. "Process cannot access the file because another process has locked a portion of the file"
I have one PC that fails it's backup every now and then with this particular error: Error EBAB03F1: The process cannot access the file because another process has locked a portion of the file. This PC is backing up to an external drive, G:, and it runs successfully some of the times. Here's the latest series of entries in the Backup Exec System Recovery.log file: 12/3/2012 23:00:10 PM High Priority Info: Info 6C8F1F65: The drive-based backup job, * - Backup to G:, has been started automatically. 0x00 (Backup Exec System Recovery) 12/4/2012 0:47:38 AM High Priority Warning: 0x800706BA (Backup Exec System Recovery) 12/4/2012 0:47:38 AM High Priority Error: Error EC8F17B7: Cannot create recovery points for job: * - Backup to G:. Error E7D1001F: Unable to write to file. Error EBAB03F1: The process cannot access the file because another process has locked a portion of the file. 0xE7D1001F (Backup Exec System Recovery) (UMI:V-281-3215-6071) I cannot figure out what is locking the file and I don't know what file is actually locked. I've been using a program called Processlock: (http://windowsxp.mvps.org/processlock.htm) to try to figure out what has the file locked, but I need to provide the exact file name in order to do so. I've found a few Symantec knowledge base documents about this error, but they always reference backing up to a network share/admin share as the issue and this isn't the case here as this is a local external drive. Is there anywhere where I can find more detailed logging to see what file actually is being locked and therefore cannot be accessed? Thanks