Forum Discussion
SP2019 Server Quick Launch Nav missing on Modern sites after Aug CU patch install
Installed KB4484472 yesterday on SP2019 Server. Users today started to complain that the Quick Launch navigation on Modern sites is no longer visible. Is anyone else experiencing the same issue and have you been able to resolve the issue? It appears that Chrome and IE browsers are only affected. Using Edge browser seems to display the navigation.
This is the expected look:
This is the current look:
Thanks in advance for any insight into this matter.
- After updates KB5002212 (SharePoint Server) and KB5002108 (Language Pack) I stared having the same problem. My farm have 2 Front End: only one is affected by the problem (401 on _layouts/15/SPAndroidAppManifest.aspx). Does anyone found a solution?
David Graham The issue is resolved in the October 2020 patch so you can install that. Also observed the same behavior after installing the Jan 2021 Security update for SP2019 good news is that it is also fixed in the later patch.
Read the full article here : Quick navigation missing on modern sites
I may have a slightly different issue now that I look at the screen shots in this thread.
For me the left navigation is still there, it's the top bar that is blank.
So I have no access to the management tools and settings.
David Graham We have also been affected by this issue for months! I finally got fed up and did some sleuthing in the code. It seems that the sp-pages-assembly.js file got replaced by a newer version which is creating most of these issues.
I will preface this by saying, always make backups before you try unverified solutions such as this one. I did such by copying the files I would be replacing in a backup directory, in the case that I need to revert back later.
In this directory:
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\16\TEMPLATE\LAYOUTS\Next\spclient
There are some layout folders. One labeled 'default' and one as 'en-us'. 'en-us' in the URL pointed me to that folder as holding the offending file. In the console, it kept saying 'cannot read property 'call' of undefined' stemming from this file:
https://river.nflibrary.ca/_layouts/15/next/spclient/en-us/sp-pages-assembly.js?uniqueId=madS1
So I replaced the sp-pages-assembly.js file in the 'en-us' folder with the older file in the 'defaults' folder. (After backing it up)
After this, the navigation came back. There are some things that still don't look right as labels aren't being updated from machine labels for example. but the navigation is back and we can edit modern pages again.
You may also need to open a CMD as Admin and run IIS reset as well as doing a hard reload on the site to get the updates to appear as caching can keep you from seeing the changes until then.
It seems that the navigation missing could be stemming from an issue with the publishing bar on modern sites as the navigation would appear again if I was in a list, that uses the modern layout but has a list bar instead of a publishing bar.
It's not perfect, but it's at least usable again.
Tried replacing the requested JS file but no luck , wondering if there is proper fix from Microsoft , its being couple of months now .
Thanks,
Nalin
cburton228
I just installed a new SharePoint 2019 Farm with the Dec 2020 CU using the AutoSPInstaller.com powershell installer and I am seeing the same thing.
The powershell installer choked and I had to setup the Default Site from the SharePoint Central Administration site. Any site I create has the same issue.
Installing KB4486675 did not fix it.
Oddly enough, the MySites web application work fine.
This week I decide to stand up a brand new farm, 5 new Windows 2019 Servers and SQL 2019.
Installed the farm using the SharePoint 2019 installer with no updates.
I did not use AutoSPInstaller since that was creating errors and crashes.
I still get the same problems. Then I ran the updates that Windows Update gave me until they were all done and then ran the Configuration Wizard on all the Servers and still no change.
I HAVE A WORKAROUND
It seems that if I create a new Web Application/site Collection NOT on port 80 everything is fine.
So I just made my Web Application/site Collection on port 2021 and it looks fine.
I decided to live on the edge and create a Web Application/site Collection on port 443 separate from my broken port 80 site and that one works too, so I think I will go with that one, better to turn on SSL anyway. Note: On my old Farm, creating my site on port 2021 worked, but 443 did not.
Tip: If creating a new Web Application on port 443 works for you, don't forget to use the FQDN and bind a SSL certificate to port 443 in IIS. If you created it without the FQDN, then add an Alternate access mapping for the FQDN for intranet.
Hi jobshopr,
Thank you for your workaround.
But it is not possible to change it in production in a big company because we use port 443.
We encountered the same problem and we saw if you logged in to the server with another account, the problem was resolved.
Also if you logged in to another server, with the account having the issue on the first server, the problem was resolved.
No display problems with IE11.
Hope Microsoft will provide an update.
Thank you.
Today I tried installing the January 2021 CU on all my SharePoint 2019 Servers and the problem still exits.
It will not let me install the October or November 2020 CU updates. I'll guess it's because these are Cumulative Updates and you should not need to install anything but the latest update.
Installing KB4486675 did the trick for me!
https://www.microsoft.com/en-us/download/details.aspx?id=102240.. and remember PSConfig 🙂
- Same here after installation of Dec CU. Microsoft please fix, thanks!
December update applied. No fix still.
- I have same issue after installing KB4486676. Anyone have solution?
Hello,
I have the same issue with our SharePoint 2019 environment after installing kb4486676 October CU.
Anyone else found a solution? Our workaround is to change the default navigation from Home.aspx to Documents.aspx
This affected the whole farm (thousands of sites)
I found others with similar issues
https://docs.microsoft.com/en-us/answers/questions/80671/shareppoint-2019-modern-team-site-template-issue.html?childToView=163899#answer-163899https://techcommunity.microsoft.com/t5/sharepoint/sp2019-server-quick-launch-nav-missing-on-modern-sites-after-aug/m-p/1710029
but no solution
Missing left navigation in 3 consecutive patches. You would think MS devs and testers would have noticed this by now. Real slack units.
Can anyone confirm if the Nov patch fixes this ?
David Graham Hi, we're also experiencing this issue. Does anyone know if this gets resolved in the Sep update ?
- I believe I have read somewhere there was a problem with the CU released in September
