Home AOMEI Products Support

Backupper will not run - INVALID_FILE_ATTRIBUTES

Have been using AOMEI Backupper for a long time and suddenly it refuses to run with an error "INVALID_FILE_ATTRIBUTES.

Uninstalled and installed the latest version v7.2.3.  It installs successfully but the Backupper Scheduler immediately starts to run and a log file appears repeatedly every 4 seconds:

AOMEI Backupper 7.2.3 log is as follows:

====================== System Information ======================
Module Path: C:\Program Files (x86)\AOMEI\AOMEI Backupper\7.2.3\ABService.exe
Product Name: Windows 10 Home (10.0.9200.2)
OS Build Name: 19044.1826
Service Package: 
OS Version: 10.0.9200.1826
BuildLabEx: 19041.1.amd64fre.vb_release.191206-1406
Total Memory: 32688 MB
Available Memory: 27659 MB
System Root: C:\WINDOWS
Processor Architecture: AMD64
Processor Number: 16
Current Time: 2023-6-18 13:34:24
================================================================

[2023-06-18 13:34:24] [0       ]UiRecord.cpp(544): CUiRecord:C:\ProgramData\AomeiBR\tasks2.2.xml
[2023-06-18 13:34:24] ::GetFileAttributesA(sCurPath)!=INVALID_FILE_ATTRIBUTES return code: 0x013E100B, .
[2023-06-18 13:34:25] [1008    ]UiRecord.cpp(544): CUiRecord:C:\ProgramData\AomeiBR\tasks2.2.xml
[2023-06-18 13:34:25] [1008    ]UiRecord.cpp(544): CUiRecord:C:\ProgramData\AomeiBR\tasks2.2.xml

The only way I can stop the scheduler autorunning is to disable the scheduler task in Windows Services.  If I now try to run Backupper manually it will not run but the scheduler restarts and new log messages appear every 4 seconds and I have to disable the service.

When I try to drop the tasks2.2.xml file into this post it says "File format is not allowed".  I have not changed the paths of any of my scheduled tasks recently and Backupper initially failed on the second file of a series of backups.
Tagged:

Comments

  • I tried deleting the file tasks22.xml after having made a copy and started Backupper manually thinking the problem was to do with this scheduler file.  Results unfortunately the same:

    AOMEI Backupper 7.2.3 log is as follows:

    ====================== System Information ======================
    Module Path: C:\Program Files (x86)\AOMEI\AOMEI Backupper\7.2.3\ABService.exe
    Product Name: Windows 10 Home (10.0.9200.2)
    OS Build Name: 19044.1826
    Service Package: 
    OS Version: 10.0.9200.1826
    BuildLabEx: 19041.1.amd64fre.vb_release.191206-1406
    Total Memory: 32688 MB
    Available Memory: 25340 MB
    System Root: C:\WINDOWS
    Processor Architecture: AMD64
    Processor Number: 16
    Current Time: 2023-6-18 14:31:54
    ================================================================

    [2023-06-18 14:31:54] [0       ]UiRecord.cpp(544): CUiRecord:C:\ProgramData\AomeiBR\tasks2.2.xml
    [2023-06-18 14:31:54] ::GetFileAttributesA(sCurPath)!=INVALID_FILE_ATTRIBUTES return code: 0x013E100B, .
    [2023-06-18 14:31:55] [1008    ]UiRecord.cpp(544): CUiRecord:C:\ProgramData\AomeiBR\tasks2.2.xml
    [2023-06-18 14:31:55] [1008    ]UiRecord.cpp(544): CUiRecord:C:\ProgramData\AomeiBR\tasks2.2.xml

    This time tasks2.2.xml is only 4 lines long since the original file is no longer there

    <?xml version="1.0" encoding="UTF-8" ?>
    <BackupRecoveryTasks version="3">
        <BackupTasks />
    </BackupRecoveryTasks>

  • @RobH, Please open Windows Task Scheduler and check if there is an AOMEI Task. If yes, please delete it.
    And, could you also send us the log folder so that we check the problem further?
  • Thanks for your response.  There is no AOMEI Task in Windows Task Scheduler.  I guess this is because for all my backups I have said to install the AOMEI Service to run the backups.

    What is the meaning of the return code  0x013E100B I am receiving in the log please?  I have searched but cannot find any reference to it.

    The log folder attached is only relevant to v7.2.3 as installing this latest version appears to have deleted the previous log folder.

    Thanks, Rob
  • Thanks for your ongoing helpful comments - not!

    I have finally managed to resolve the issue myself.  Uninstalling and re-installing using the AOMEI uninstaller did not resolve the issue as I stated above.  So I performed a complete and thorough uninstall with Revo uninstaller and then deleted the folder AomeiBR, although I took a copy first.  Then I performed a completely fresh install and AOMEI BackUpper is now working.  Since I have many backup tasks scheduled, I copied my old tasks2.2.xml back into the new AomeiiBR folder and all my backups are now working thankfully.
  • @RobH, Thanks for your feedback. We have submitted the problem situation to our dev team.
Sign In or Register to comment.