Error validation task - 0x00DA0002+0x0040005B
Hello,
we have a Problem with the validation task on one of our Servers.
OS on all Servers: MS Server 2003 R2 SP2 (patchlevel may 2010)
Acronis: Backup & Recovery Adv Server 10 build 11639
While trying to validate a Archive on a Networkshare the Validation task failed with following error:
-------------
Log Entry Details
-----------
Type: Error
Date and time: 6/8/2010 8:01:02 AM
Backup plan: Backup SERVERNAME
Task: Validation task
Code: 11,863,304(0xB50508)
Module: 181
Owner: acronisuser@DOMAIN
Message:
Task 'Validation task' failed: 'Error occurred while running the backup and recovery engine.
Additional info:
--------------------
Error code: 2
Module: 218
LineInfo: 600f7166ce397e28
Fields: IsReturnCode : 1, $module : C:\Program Files\Acronis\BackupAndRecovery\mms.exe
Message: Error occurred while running the backup and recovery engine.
--------------------
Error code: 91
Module: 64
LineInfo: d143f4885f91eeaa
Fields: code : 8, $module : C:\Program Files\Common Files\Acronis\BackupAndRecoveryAgent\BackupAndRecoveryService.exe
Message: Failed to validate backup archive 'SERVERNAME_2010_05_18_09_46_39_360D1' from the location with ID 'file://FILERNAME\w$\acronis\SERVERNAME'.
--------------------'.
Acronis Knowledge Base: http://kb.acronis.com/errorcode/
Event code: 0x00DA0002+0x0040005B
---------------------
There are two other machines that also backup to the same targetserver and they don't have problems.
the other machines have build 11345 and 11133
they are all running under the same domainaccount and backup to subfolders of the same share
With kind regard
Oliver
Hello all,
Thank you for your posts. I will do my best to assist you.
I am terribly sorry for the inconvenience, but at the moment it is difficult to understand why this issue occurs. Each problem requires additional investigation.
Please submit a support request with the following description:
1. AcronisInfo report from the machines.
2. Wireshark logs. Please launch the utility prior to validation failure, so that it can capture network packets.
3. To localize the issue, please try creating a backup to another location and see if validation fails.
Please let me know if you have additional questions.
Thank you.
Same error, nice to see they have fixed it??????
0x00DA0002+0x0040005B
This has been happening since 5/1/2010 for me (on a brand spanky new out of the box machine), and no solution.
Time to get new imaging software.....
Hello Scott,
Welcome to Acronis Forum, we're glad to greet you here.
Unfortunately this issue is not a common one and can be caused by different reasons. We will be happy to help you with it. Could you please follow the instructions mentioned by Anton and let us know the case number?
Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!
Thank you.
Just hit the same bug validating a backup on MY wizzy new machine too :(
failing module was 181 and this message was after a 0x000101F6+0x00070020 and two 0x0040005B's. I guess it retried and then gave up.
Acronis are VERY good at solving problems for customers (they put an immense amount of effort into solving a Linux/Marvell Raid controller restore disk issue for me on version 8 (though it took over 6 months :( )
My failing archive is on an external eSata drive and is the first error I've had in the month since I installed Acronis Advanced Workstation on the new machine. The machine itself is an I7-930 2.8GHz O/C'd to 4.2GHz on water cooling but is TOTALLY stable so I'm sure that it isn't the problem.
I'm going to retry the validate, and, if it still fails, delete and recreate the archive.
If it gets too bad and frequent then I'll start the bug report process (but I'm not sure I'll have the will to live if I go through that again :) )
Again, Acronis support are very good and very thorough, but you're going to have to work for your fix!
I just wish Acronis would send an automatic error report complete with sysinfo when these errors occur (with a user being able to disable it of course). The tools to do that are readily available.
Colin
Hello. I have installed the latest version of backup and recovery 10 WS 12457. Ran a backup with version 11639. I then tried to put the image on a usb hard drive so that I could replace the smaller C drive. That failed, so I thought maybe I should validate it, that failed. This is all local storage, except the USB, which should be treated that way. I have the following error:
------------------
Log Entry Details
-----------------------------
Type: Error
Date and time: 9/25/2010 7:10:38 PM
Backup plan: [None]
Task: MyValidation_1
Code: 11,863,304(0xB50508)
Module: 181
Owner: Dark Angel@Deathwing
Message:
Task 'MyValidation_1' failed: 'Error occurred while running the backup and recovery engine.
Additional info:
--------------------
Error code: 2
Module: 218
LineInfo: 600f7166ce397df5
Fields: IsReturnCode : 1, $module : C:\Program Files\Acronis\BackupAndRecovery\mms.exe
Message: Error occurred while running the backup and recovery engine.
--------------------
Error code: 91
Module: 64
LineInfo: d143f4885f91eea4
Fields: code : 8, $module : C:\Program Files\Common Files\Acronis\BackupAndRecoveryAgent\BackupAndRecoveryService.exe
Message: Failed to validate backup archive '7-C-Arch-9-22-2010_2010_09_22_23_37_30_839D' from the location with ID 'file:D:\Acronis\'.
--------------------'.
Acronis Knowledge Base: http://kb.acronis.com/errorcode/
Event code: 0x00DA0002+0x0040005B
-----------------------
So I'm getting a bit frustrated trying to figure this one out. I had errors regarding the fact that it could not access the file, so I took ownership of it and the directories above it for good measure. This was a misleading error, because when I looked at the setting in Acronis, it was not set by default to look for an archive. Once I set that it was able to see the file again. I was thinking it was a problem with permissions in Windows 7, however I was able to write to the directory to create the backup. I'm not going to run a wireshark for local storage, however I may start looking at the file when running validation with perfmon or filemon. I'm starting to not like the fact that this is becoming a more complex process to accomplish what I find to be a simple task. I am sure I have Microsoft to tank for that in some way. I also cannot save a log file, due to another error. Either I or the service account running with my information or the local system doesn't seem to have access to write to the C drive. So as it turns out with have windows to blame for that, they've made it so secure you cannot accomplish a simple save file task to the root of C (ok mimic Linux, I like it better.) I was able to save the file to the desktop in my profile ;o). So I am thinking that this is the fundamental problem that it is the way windows 7 handles access to folders, drives, etc. If anyone has any suggestions let me know. I'm starting to think about going back to the version that worked for me.
I found the problem on this verify error in my case: The backup that I was verifying had failed 'silently' with no errror messages in the log!!! I noticed because the backup was smaller than a previous one by 50GB despite me copying a lot more files from the old machine)
I deleted the backup, created a new one, and could then validate OK.
Obviously a backup issue (and I can't help because I've deleted the backup image (670GB) using shift-delete! ). Maybe if someone still has a reasonable size image that fails verfication then they could send to Acronis for fault finding.
Colin
Well, maybe I'll keep the image on another USB drive, but then try to delete it and then try another image, about an 8-10 hour process. The image files is 416 GB, which is a heck of a large file to FTP, even with multiple sessions, I suppose I could break it down into smaller chunks with archive software, but it's still huge and going to take a long time.
When the product first came it it was great with its feature set etc. I think with the move from MS to put security in place that's created the challenge.
The other thing I was going to try was to change the classification from ARCHIVE to BACKUP and see if I get different results. I know when you choose the default it will not find the backup file. Doesn't matter which one you choose it still fails with the same error.
Thanks for the info, that was going to be my last ditch effort to diagnose the issue, another thing someone pointed out was the VSS service not running and causing a problem.
Tim,
Out of interest, I was originally backing up to an eSata external drive using eSata ports on the non-X58 controllers on my Gigabyte X58A-UD7 M/B. I kept getting disk 'errrors' in the MFT copy where, I guess, the drive had powered down, and didn't spin up quickly enough for Windows liking. Chkdsk generally sorted things out, but I did lose 3 files once.
This is a pure guess, but I've temporarily ditched my 4 drive eSata external backplane in favour of a Startech USB3.0 to eSATA2 dock. This has worked flawlessly. OFF TOPIC - MAYBE: If anyone can shed any light on the eSATA external drive issue (don't know if this is affecting any of the above posters), then we might have an possible solution
Colin
I could look at the drive type which is internal sata, not sure which version, but just to test out access to the files I had Acronis mount the drive and that worked. Wonder if there is a way to validate a mounted drive? The drive is a 1 TB at 3 GB/sec. So I am guessing it a ver. 3. Certainly isn't a file access issue at all, unless a different service is accessing it. If your drive was cutting out could have been the housing that was having an issue. I know the old version used to not fail if the drive was removed while backing up and then added back. Tried it once while testing to see if it would fail and was surprised that it didn't.
I'd guess that the mount will work fine, but you'd have to (say) run Norton on every file on the mounted volume to check if all files were accessible, and you might still not see the missing ones.
I'm as near certain as I can be that my problem with the eSata drives has nothing to do with the backplane which is literally just a straight-through power and eSata structure. As far as I can tell, I have absolutely no problems as long as the drives are kept spinning up, but if they power down, then Windows 7 (and I had same problem on XPSP3 on a previous machine) doesn't wait long enough for them to spin up again when something like Diskeeper does an access, and I get a corrupted secondary MFT, and sometiimes lost files.
I've run endless file copies and compares using BeyondCompare3 (GREAT program) without a single error. It's only if I leave a backup overnight and the drive powers down when finished. I've also disabled all write caching even though that really slows the eSata down. Having done the same last night on a backup to the USB3 I had no problems.
That's the last problem I have to solve on what is otherwise a superb new machine (930 O/C from 2.8 to 4.2GHz on water and die temps never exceed 70C even on 8 thread torture test).
Hope you solve your problem. I'm getting around mine with the USB3 to eSata units from Startech until I resolve the native eSata issue
Colin
May be this post helps...
I have backup server with windows 2003 r2 x64, source server with same OS and Acronis Server 10 build 11639.
On backup server i have share folder for backups.
Today i found that one of my server failed regular backup.
--------------------
Код ошибки: 2
Модуль: 218
LineInfo: 600f7166ce397e28
Поля: $module : C:\Program Files (x86)\Acronis\BackupAndRecovery\mms.exe
Сообщение: Ошибка во время работы ядра резервного копирования и восстановления.
--------------------
I found regular error in NT security log on backup server:
Logon Failure:
Reason: Unknown user name or bad password
User Name: @
Domain:
Logon Type: 3
Logon Process: NtLmSsp
Authentication Package: NTLM
This is not normal because user name is not correct and LH hash is disabled on backup server.
And user name in job is stored 100% correctly.
I found, that LM hash is enabled on source server. So i disable it on source server, but still don`t know is it helps or not because to apply LmHash setting needs to restart OS (this is production server, i can`t restart it this time)
I delete all backups and recreate Acronis Job. Job is now working, but i still see Security errors in NT log on backup server.
=======
sorry for my english
we have the same problem, although the Image is located on the same machine of a backup-partition!
Fehler während Ausführung der Backup- und Recovery-Engine aufgetreten.
Zusätzliche Info:
--------------------
Fehlercode: 2
Module: 218
LineInfo: 600f7166ce397e28
Felder: IsReturnCode : 1, $module : E:\Programme\Acronis\BackupAndRecovery\mms.exe
Nachricht: Fehler während Ausführung der Backup- und Recovery-Engine aufgetreten.
--------------------
Fehlercode: 91
Module: 64
LineInfo: d143f4885f91eeaa
Felder: code : 8, $module : C:\Programme\Gemeinsame Dateien\Acronis\BackupAndRecoveryAgent\BackupAndRecoveryService.exe
Nachricht: Validieren von Backup-Archiv Server-Vollsicherung_2011_03_13_16_00_36_445D9' vom Speicherort mit ID 'file:F:\backup-Server\aktuell\' fehlgeschlagen.
--------------------
Hello all,
Thank you for posting.
I will do my best to help you.
Considering the complexity of this issue I would recommend to contact our Support team with this report so that we can promptly investigate and resolve it. I apologize for any inconvenience.
Please let me know if you have additional questions.
Thank you.