Processing OneDrive finished with warning: Cannot complete this action

[AlexLeadingEdge]

Case # 07871930

I've been seeing this for about a week now. The warning message isn't all that helpful. Any ideas how to fix this?

30/10/2025 9:07:21 a.m. :: Processing OneDrive [REDACTED] (https://[REDACTED].sharepoint.com/personal/[REDACTED]) finished with warning: Cannot complete this action. Please try again. :: 0:00:32

[track1044]

We are seeing it across multiple clients, across OneDrive, Teams and SharePoint. We've seen it rise in frequency for about 3 weeks.
It can be resolved by finding and deleting the file, but we just had a team with 160+k item failures, so that's not really viable.

Support has told me RnD is looking into it.
Case # 07854931

[matthew_st]

Hello,

we have the same error only with one user. Anyone has a solution for this?

[Polina]

Hi All,

Thanks for bringing this to our attention. There's no ready solution yet - troubleshooting is in progress.
@matthew_st Please provide your case ID as well.

[Boesboes]

Hi All,

@Polina Is there any update on this? Have it to with 1 user.
@track1044 in our case it does not error on a specific file but only gives the root folder of the personal onedrive.

Also checked that user's onedrive and no strange things going on. (no sync errors)

[track1044]

@Boesboes
In the logs you can find the specific item, list and site ID for the item, this you can then use with graph api to see the file.
Sometimes there is no file, which we have had issues with as well, so we are still waiting for a fix.

[Polina]

@Boesboes

Our RND has opened a case with Microsoft and we're now expecting their input.

Thanks!

[tm67]

Are there any news on this? Do we have to create a Veeam support case for each tenant that we see this error? Or will there be a fix available soon?

[Polina]

Kindly, see https://www.veeam.com/kb4793

[AlexLeadingEdge]

Thanks Polina.

I'm now seeing this across all of my clients, hopefully Microsoft will fix this soon.

[JTT]

Are there any know changes from Microsoft again, because we are seeing multiple different tentants having one or two Onedrive backups feiling.

[TeflonDon]

Case # 07871930
Been seeing this also in one of our tenants, anyone know of a fix yet?

[c.guerin]

Hello,
I can confirm that this error has reappeared and that its frequency is increasing day by day.

[JTT]

I created a support Case # 08169572, but yes more tentants started failing and currentyl we have 20+ that has issues

Some job fail with
23.07.2026 00:34:13 :: Processing of all objects failed

Some give
22.07.2026 21:35:17 :: Processing site: https://xxx completed with warning: Failed to backup list: Documents. Cannot complete this action. Please try again. (ErrorCode: 0x80004005) Total count of failed items: 1 :: 0:00:05

[spritchard81]

Seeing the ErrorCode 0x80004005 over the past two days.

[dkuhl]

I'm seeing the same thing.

Veeam Support - Case # 08170887 - Cannot complete this action. Please try again. :: 0:00:05

[FCU_JE]

Joining the chorus of the last couple comments.

Job runs were fine and not presenting the below warning/error until job runs that started 2026-07-22 00:00 UTC. Job runs before that didn't have this issue.

Code: Select all

Failed to backup list: <Name of List>. Cannot complete this action. Please try again. (ErrorCode: 0x80004005) Total count of failed items: <int>

<Name of List> and <int> above are placeholders.

Impacting two sites in a small tenant. Retries do not help. Same two sites show up in the output of all warning jobs. The list showing up in the "Details" output for one of the sites just changed on the last job run, but the other site is still on the same failed list.

I assume "list" is Veeam-speak for "Document Library" but I'm not sure.

[FrancWest]

Same here. Both with OneDrive (case # 08171141) and SharePoint (case # 08171167). Happening since Tuesday.

[AlexLeadingEdge]

I'm seeing this issue again too. Veeam Support says they're aware of this issue and pointed me to this:

https://www.veeam.com/kb4793

//Edit: The Veeam KB article is now saying Microsoft says this has been fixed, but I'm still seeing the error.

Case #08171590