OOB JS errors since August CU - SharePoint 2019

%3CLINGO-SUB%20id%3D%22lingo-sub-1747840%22%20slang%3D%22en-US%22%3EOOB%20JS%20errors%20since%20August%20CU%20-%20SharePoint%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1747840%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20in%20the%20process%20of%20migrating%20our%20organisation%20from%20SP2013%20to%20SP2019.%20We%20have%203%20environments%20setup%2C%20with%202%20Web%20Applications%20in%20each.%20DEV%20is%20a%202%20server%20farm%2C%20UAT%20and%20PROD%20are%20both%208%20server%20farms.%20Since%20the%20August%20CU%2FLanguage%20Pack%20we%20have%20been%20unable%20to%20use%20any%20of%20the%20existing%20modern%20site%20collections%20due%20to%20JS%20errors.%20The%20errors%20cause%20certain%20links%20in%20the%20site%20settings%20menu%20to%20not%20work%2C%20and%20the%20Edit%20page%20buttons%20are%20not%20rendered%2C%20basically%20mean%20users%20have%20no%20means%20for%20editing%20pages.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20I%20have%20been%20able%20to%20determine%20is%20that%20if%20I%20create%20a%20brand%20new%20web%20application%20and%20create%20an%20OOB%20Communications%20site%2C%20there%20are%20now%20issues.%20It%20only%20appears%20to%20affect%20modern%20site%20collection%20in%20the%20existing%20Web%20Applications.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20are%20no%20customisations%20present%20in%20these%20farms.%20No%20web%20parts%20or%20app%20customisers.%20They%20are%20basically%20new%20unmodified%20farms%2C%20so%20we%20are%20at%20a%20loss%20as%20to%20what%20may%20be%20the%20cause.%20As%20I%20mentioned%20the%20sites%20were%20perfectly%20fine%20up%20until%20the%20August%20CU%2C%20where%20we%20noticed%20after%20patching%20the%20severity%20of%20the%20issues.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20even%20tried%20deleting%20completely%20the%20existing%20web%20applications%20(in%20DEV)%20and%20recreating%20them%20with%20the%20same%20names%2C%20however%20this%20still%20results%20in%20the%20same%20console%20errors%20and%20unusable%20Modern%20sites.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20posted%20this%20issue%20in%20stack%20exchange%20without%20any%20success%2C%20would%20love%20any%20insights%20into%20what%20the%20issue%20could%20be.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20is%20the%20console%20error%20message.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22console-errors1.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F224335i9257D48C4AF7D3FF%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22console-errors1.png%22%20alt%3D%22console-errors1.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%E2%80%83%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1747840%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor

We are in the process of migrating our organisation from SP2013 to SP2019. We have 3 environments setup, with 2 Web Applications in each. DEV is a 2 server farm, UAT and PROD are both 8 server farms. Since the August CU/Language Pack we have been unable to use any of the existing modern site collections due to JS errors. The errors cause certain links in the site settings menu to not work, and the Edit page buttons are not rendered, basically mean users have no means for editing pages. 

 

What I have been able to determine is that if I create a brand new web application and create an OOB Communications site, there are now issues. It only appears to affect modern site collection in the existing Web Applications.

 

There are no customisations present in these farms. No web parts or app customisers. They are basically new unmodified farms, so we are at a loss as to what may be the cause. As I mentioned the sites were perfectly fine up until the August CU, where we noticed after patching the severity of the issues.

 

I have even tried deleting completely the existing web applications (in DEV) and recreating them with the same names, however this still results in the same console errors and unusable Modern sites.

 

I've posted this issue in stack exchange without any success, would love any insights into what the issue could be.

 

Here is the console error message. 

 

console-errors1.png

0 Replies