Solving “Sorry, your files couldn’t be uploaded. The upload might be too large or the server might be experiencing high network traffic.” in SharePoint

SharePoint cat fixing them errors

This is one of the kind of weird issues that you don’t really run into in your own development environments, but that you more often run into when you actually have non-godlike permissions. Oh, the woes of trying to use SharePoint with anything less than farm/global administrator… 🙂 Anyway, in this post I’ll describe a couple of solutions to an error: “Sorry, your files couldn’t be uploaded. The upload might be too large or the server might be experiencing high network traffic”.

You might encounter this issue, when uploading pretty much any files in any SharePoint document library. Typically, I run into this when trying to update a file in a library (in my case, the only times I’ve ever seen this, have been the Style Library of a SharePoint site). You can apparently encounter it with any file type, in this example below, it happened with a JavaScript (.js) file.

Style Library throwing an error: "Sorry, your files couldn't be uploaded. The upload might be too large or the server might be experiencing high network traffic."

Style Library throws an error:
“Sorry, your files couldn’t be uploaded. The upload might be too large or the server might be experiencing high network traffic.”

Funnily enough, I usually encounter this issue with a following set-up:

  • On-premises SharePoint server (2013 or 2016 – occasionally also SharePoint Online, but that’s less typical!)
  • Small files (of 1-200kb)
  • The server has been experiencing very low network traffic.

The error really doesn’t seem to describe the issue at all – so what’s actually causing this?

Solution(s)

Quick googling didn’t give any actual reasons or fixes for the issue. A lot of people online seem to suggest changing your browser to something else from Internet Explorer… While it might not be a bad idea in itself, it does seem like a ridiculous fix – and also didn’t work for me 🙂

However, every single time so far, going through this checklist has helped me solve the issue and get rid of the error: Continue reading