Vista Backup Error 0x81000010

[Guest]

Hi, when I try to do SET UP AUTOMATIC FILE BACKUP, I get this error
0x81000010 - I am almost sure, that there is some problem with rights. I have
this Vista in domain and there are some restrictions - if I log-in as user
without these restriction (but it means domain admin), backup is working
without any problem. I would like to know what right user needs to do backup.
Now he is local administrator, but with some restriction in GP. I didn't find
any page on internet about it, so if you know some, please, let me know.

Regards Michal

 

[Jill Zoeller [MSFT]]

This is an unusual error--I searched my archives and cannot find any
reference to this code.

If you can send me the following information, I can investigate this
further.

1. A description of the problem, including the exact error message and error
code (a screenshot will work)
2. A screenshot of your Disk Management screen showing disks and volumes.
3. Zipped contents of C:\logs\WindowsBackup\
4. Generate a log file using the instructions below and email it to me:

Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Asr,
create a new key called LogFileSetting

Under LogFileSetting, create a new DWORD value called EnableLogging.
Right-click that value, click Modify, and then enter 00000001 (hexadecimal)
or 1 (decimal)

Under LogFileSetting, create a new String value called LogPathName.
Right-click that value, click Modify, and then enter C:\asr.log.

Next, reproduce the error. You should have a file called asr.log under c:\.
You can delete the registry key when you are done.

Use my email address, minus "online."

 

[Guest]

Hi, I found the solution - it was problem with rights. User didn't have right
"overtake files" - in Czech version it is (sorry, I have only Czech version):


Konfigurace poÄítaÄe - Nastavení systému Windows - Nastavení zabezpeÄení -
Místní zásady - Přiřazení uživatelských práv - Převzít soubory nebo jiné
objekty

(only domain admins could), so I gave to him same right - in GP (I did ONLY
this) and now it is working. I am not sure, if it is good solution, but it
seems to be only way to solve this "error". But if you still want anything to
send, let me know.