Video Screencast Help

Physical to Virtual (P2V) conversion of recovery point fails ('EBAB03EE: Operating System API..').

Created: 26 Mar 2012 • Updated: 25 Apr 2012
Chris Riley's picture
0
Votes
Login to vote
Me Too!I have the same issue
Product(s): Symantec System Recovery (formerly Backup Exec System Recovery) - SSR 2011, Symantec System Recovery (formerly Backup Exec System Recovery)
Severity: Non-data threatening / major functionality
Status: Public fix available
Tech Note: More Information

Problem

Physical to Virtual (P2V) conversion to VMDK (version 6) format of a Windows SBS 2011 server fails with the errors listed below.

A Restore Anyware (RAO of the same recovery point fails with a similar error.
 
 
Error

High Priority Error: Error EC8F1F48: The 'VMware VMDK' conversion process Could not be completed.
EC8F1F45 Error: Can not convert image file.
Error EBAB03EE: Operating System API [Registry Operations :: SaveKeyAsHive] RegSaveKeyExW (TARGET_HIVE_SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion, Y: \ VProRecovery \ TargetWinNtCurrVer.hiv) failed.
EBAB03F1 Error: Insufficient system resources exist to complete the requested service. 0xEBAB03EE (Symantec System Recovery)
 
 
Environment

Windows SBS 2011 Standard
 
 
 
 
Solution

At the time of writing, there is no workaround. This article will be updated when a solution/workaround is available.

Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
 
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns.  For information on how to contact Symantec Sales, please see http://www.symantec.com

Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.