From time to time we are experiencing the "Failed to download page web parts for file" from various customers. Sometimes the issue disappears on its own, and sometimes the problem persists.
Currently we have this exact warning (customer names and site replaced) :
We have raised ticket #07318875 but not getting any real traction on a fix. We have tried allowing custom scripting through PowerShell and Azure GUI as advised by support, but still no luck.
I'm not sure if allowing custom scripting is still an option. Microsoft has started to deprecate that setting in all M365 tenants in early-May 2024. But there is a PowerShell parameter to delay it till November 2024. Have you run that command?
The Custom Script setting in SharePoint and OneDrive will be removed by early-May 2024. A new PowerShell command, DelayDenyAddAndCustomizePagesEnforcement, will allow administrators to delay the change until mid-November 2024. The NoScriptSite setting will be configured to True for all existing sites except for specific site templates. Existing scripts in OneDrive and SharePoint sites will not be affected. Administrators can still permit the execution of custom scripts on specific sites using the Set-SPOSite command or from the Active sites page in the SharePoint Admin Center.
We have raised ticket #07318875 but not getting any real traction on a fix.
Our RnD teams are aware of the deprecation. And we are currently investigating if we have to change something in the product. Please see also this topic and Mikes comment: post511308.html#p511308
Thanks, but allow custom scripting still works for most of our customer, we haven't seen any yet where the normal warning "..... finished with warning: Cannot change web part export mode to ‘All’, because custom scripting is disabled for site: ....." couldn't be fixed by allowing custom scripting during the next backup run.
However we are starting to see lots of "Failed to download page web parts for file" across multiple customers, so really hoping for a fix.
There is an agreement that this isn't going to be changed until the fix is in place (which has to come from MSFT, not from us as we can't do much about it). That fix is in the works by them, but obviously takes a bit of time to make such a web part exportable without the need for scripting.
Please escalate the support ticket so it gets to a higher level and I can start talking to Microsoft
There is indeed a resolution to it, or at least, it is in flight. We have a PoC now with MSFT that allows us to download those without the scripting part. MSFT started to roll it out and expects to have it fully deployed by end of this year. We will change our code, push an update at a certain point in time so you aren't suffering from it anymore. But unfortunately, it will take a few more weeks before the full rollout is done
@mike Any idea if a new patch or if one of the latest is meant to fully resolve this?
Am on the latest patch and still getting the warning on some (and same) SPS online sites
It looks like the deadline has past as a ton of my sharepoint sites are now giving the warning. Would be nice to know when the new method is being deployed