Search This Blog

Monday, January 18, 2021

OneDrive Error message 0x80071129

clip_image008

Introduction

When we buy license to use office365 services we have lots of collaboration possibilities. One of the great features is OneDrive. OneDrive gives us the possibilities to backup folders like desktop, documents and pictures what makes the life of working on multiple devices much easier. (e.g., some of this content was written on my iPhone while my device was rebooting and checking my disk)

Sometimes files lock and OneDrive cannot sync or work with the document. What can we do to solve that?

In this example NTFS permissions blew up and I had to fix it to delete the file.

 

Requirements

  • Onedrive KFM configured
  • Reboot
  • Patience

 

Error message 

clip_image002

Your document is stuck. It cannot open, you cannot delete it, it cannot be renamed. Just stuck!

 

To fix the issue

clip_image004

clip_image006

Let’s have a good old CMD

 

clip_image008

chkdsk c: /F /R

 

Warning: before restarting your device consider if you have the time to wait, as it can take very long time depending on various parameters.

clip_image010
Reboot your device

 

clip_image012

And with that trick our file(s) are back online and ready to work with again.

To fix the issue using Endpoint Manager

Go to https://endpoint.microsoft.com/

Devices -> Windows -> PowerShell Scripts -> Add

clip_image002

Give it a documenting naming standard

clip_image004

Script can be downloaded here:

Build upon Ben Whitmore’s notification script but with some change in code, as I don’t want attachment to external files. Pictures are encoded.

Also borrowed code from Damien Van Robaeys which encode ServiceUI.exe for breaking out of system context, which was needed in this scenario.

 

clip_image006

Select a test group.

Click Add

If users have trouble syncing files as specified, add them to the assigned group and save time for your helpdesk by automating it.

 

User experience

clip_image008

Summary

Using OneDrive as backup and collaboration tool is superb. Sometimes things can go wrong, and we need to know how it can be solved.

Happy testing!

4 comments:

  1. Great script, however I'm having issues when running it from either SCCM scripts or even just the system context using psexec.
    I'm getting an 'Access is denied' error on line 80 of the toast_notifications.ps1 when it goes to invoke the toast notification. It seems this is a common issue with toast (e.g. https://www.reddit.com/r/SCCM/comments/dv8l7i/sctoastnotificationexe_access_denied/)? Or am I missing something

    ReplyDelete
  2. hmm strange! Are you not able to execute the script manually?

    ReplyDelete
  3. First option with scanning and repairing disk works well :D
    Thank you for help, i get rid of this useless folder!

    ReplyDelete
  4. You are most welcome. Glad it helped you :)

    ReplyDelete