Fatal Internal Error: Cannot Recover
When U-Move clones Active Directory to the destination computer, it may encounter an unexpected error. If U-Move encounters an unexpected error it will automatically roll back all changes. This will restore the destination computer back to its original state.
In rare cases the roll back may fail. You may see the error message “Cannot Recover From Error,” “U-Tools Fatal Error,” or “A fatal internal error occurred.” These messages mean that a serious error occurred as U-Move tried to roll back the changes to your computer.
Causes for fatal or internal errors can include computer viruses, anti-virus software, disk bad-block errors, memory bad-bit errors, BIOS configuration errors, or other low-level system malfunctions.
How To Manually Recover a Failed Clone Operation
During cloning, if the roll back fails unexpectedly due a fatal or internal error, you can attempt to manually recover the destination computer using the following procedure.
Caution: Use this manual procedure only if both of the following conditions are true:
- You clicked the Finish button on the destination computer.
- U-Move displayed the message “Cannot recover from error,” “U-Tools Fatal Error,” or “A second error has occurred,” or “A fatal error has occurred.”
Make sure that the failure happened after you clicked the Finish button. U-Move makes no changes to the destination computer until you click the Finish button.
|Caution: If U-Move completed normally you should not use this manual procedure. If U-Move completed normally, select the Undo tab (at top) to undo the clone operation.|
Step 1: Write Down the Error Message and Exit
Write down the text of fatal error message, if any. Then exit U-Move. (If U-Move is hung press the keys Ctl+Alt+Del simultaneously. Click on U-Move and then click on End Process.) Please send the text of the error message along with a copy of the trace log file to U-Tools technical support.
Step 2: Find the most recent backup of the System State
Locate the most recent backup of the System State created by Windows Server Backup (wbadmin.exe).
Windows Server 2003: Find the most recent .BKF file that contains a backup copy of the System State from before you ran U-Move.
Step 3: Restore the System State
- Open an administrative command console.
- Type wbadmin start systemstaterecovery -backupTarget:E:
Substitute E: with the drive letter containing the Windows Server Backup of the System State.
Windows Server 2003
- Run NTBACKUP. Turn off wizard mode. Click the tab Restore and Manage Media. In the left panel expand and locate the .BKF file. (If not found right-click on File and select Catalog file.)
- Click on the menu Tools -> Options. Click on the tab Restore. Select Always replace the file on my computer. Click OK.
- Expand the file tree and locate System State. Click on it so that the checkmark box is checked.
- Click the button Start Restore. Click OK.
Finally, reboot the computer when prompted.
If followed correctly this procedure should restore your computer back to its original state.
Reporting an Internal Error
A support plan is not required to report a fatal or internal error. When reporting the fatal or internal error to U-Tools you may be asked to send via e-mail a copy of the trace log file and the dump file (if present).
The trace log file is
C:\Program Files\UMove\TraceLogs\UMoveTrace.txt. If the program encountered a fatal error there will also
be a dump file,
Please send these two files as attachments in your e-mail message to U-Tools technical support.
Enterprise License: 24/7 Support
Standard support is via e-mail to U-Tools technical support. Standard support will respond to your query within one business day.
The U-Move Enterprise license is a premium license that provides 24/7 technical support. If you have an Enterprise license please send an e-mail message with your Enterprise license code and state in your message that you are requesting Enterprise telephone support. Please include a call-back telephone number where we can contact you.
|U-Move for Active Directory|