SOLVED

Problems displaying site content

%3CLINGO-SUB%20id%3D%22lingo-sub-2552967%22%20slang%3D%22en-US%22%3EProblems%20displaying%20site%20content%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2552967%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20day%20everyone.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20was%20a%20display%20issue%20after%20the%20last%20update.%3C%2FP%3E%3CP%3Ethat%20is%2C%20upon%20opening%2C%20for%20example%3A%3C%2FP%3E%3CP%3ESitePages%2FForms%2FByAuthor.aspx%3C%2FP%3E%3CP%3EShared%2520Documents%2FForms%2FAllItems.aspx%3C%2FP%3E%3CP%3E_layouts%2F15%2Fviewlsts.aspx%3C%2FP%3E%3CP%3Ethe%20opened%20page%20is%20empty%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPerhaps%20someone%20faced%20a%20similar%20situation%20and%20can%20tell%20what%20caused%20it%20and%20how%20to%20fix%20it%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2552967%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2553995%22%20slang%3D%22en-US%22%3ERe%3A%20Problems%20displaying%20site%20content%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2553995%22%20slang%3D%22en-US%22%3E%3CP%3EI%20will%20add%20screenshots%3A%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%2211.jpg%22%20style%3D%22width%3A%20994px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F296217iA3A87611ABE47C52%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2211.jpg%22%20alt%3D%2211.jpg%22%20%2F%3E%3C%2FSPAN%3E%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%22333.jpg%22%20style%3D%22width%3A%20994px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F296219i9BEC2A2A588B648E%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22333.jpg%22%20alt%3D%22333.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EThe%20content%20and%20structure%20of%20the%20site%20contains%20the%20%22Documents%22%20directory%2C%20but%20when%20you%20try%20to%20open%20the%20link%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fmy_domain.com%2Fpurchasing%2FShared%2520Documents%2FForms%2FAllItems.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fmy_domain.com%2Fpurchasing%2FShared%2520Documents%2FForms%2FAllItems.aspx%3C%2FA%3E%26nbsp%3Ba%20blank%20page%20is%20displayed.%26nbsp%3B%3C%2FP%3E%3CP%3EA%20blank%20page%20is%20also%20displayed%20when%20clicking%20on%20the%20%22site%20content%22%20link%3C%2FP%3E%3CP%3Ehttps%3A%2F%2F%3CA%20href%3D%22https%3A%2F%2Fmy_domain.com%2Fpurchasing%2FShared%2520Documents%2FForms%2FAllItems.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Emy_domain.com%3C%2FA%3E%2Fpurchasing%2F_layouts%2F15%2Fviewlsts.aspx%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESharepoint%20server%202019.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2554918%22%20slang%3D%22en-US%22%3ERe%3A%20Problems%20displaying%20site%20content%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2554918%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1104522%22%20target%3D%22_blank%22%3E%40Sergey_Lelekov%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eafter%20the%20installtion%20of%20cu%2007-2021%20KB%205001975%20-%20Sharepoint%202019%20on%20prem%20I%20have%20also%20the%20same%20problem%3C%2FP%3E%3CP%3ESharePoint%202019%20July%202021%20CU%20Build%20Number%3A%3C%2FP%3E%3CP%3ELanguage%20independent%20fix%3A%2016.0.10376.20001%3CBR%20%2F%3ELanguage%20dependent%20fix%3A%2016.0.10376.20001%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2559708%22%20slang%3D%22en-US%22%3ERe%3A%20Problems%20displaying%20site%20content%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2559708%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1104522%22%20target%3D%22_blank%22%3E%40Sergey_Lelekov%3C%2FA%3E%26nbsp%3B%2C%20even%20i%20am%20also%20facing%20the%20same%20issue%2C%20is%20there%20a%20way%20to%20uninstall%20the%20Security%20Patch%20update%20KB5001975%2C%20i%20think%20that%20is%20causing%20the%20problem%2C%20please%20suggest.%3C%2FP%3E%3CP%3Ei%20posted%20the%20same%20here%26nbsp%3B%3CA%20title%3D%22SharePoint2019%20Blank%20White%20Screen%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fanswers%2Fquestions%2F479825%2Fsharepoint-2019-on-premise-server-farm-broken-blan.html%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3ESharePoint2019%20Blank%20White%20Screen%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2560007%22%20slang%3D%22en-US%22%3ERe%3A%20Problems%20displaying%20site%20content%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2560007%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1104522%22%20target%3D%22_blank%22%3E%40Sergey_Lelekov%3C%2FA%3E%26nbsp%3B%2C%26nbsp%3BI%20fixed%20by%20installing%20the%20patch%20KB5001974%20need%20to%20be%20installed%20along%20with%20the%20KB5001975%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2561405%22%20slang%3D%22en-US%22%3ERe%3A%20Problems%20displaying%20site%20content%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2561405%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1106334%22%20target%3D%22_blank%22%3E%40anandpeculiar%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you.%20The%20problem%20is%20resolved.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2569329%22%20slang%3D%22en-US%22%3ERe%3A%20Problems%20displaying%20site%20content%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2569329%22%20slang%3D%22en-US%22%3EThanks%3C%2FLINGO-BODY%3E
New Contributor

Good day everyone.

 

There was a display issue after the last update.

that is, upon opening, for example:

SitePages/Forms/ByAuthor.aspx

Shared%20Documents/Forms/AllItems.aspx

_layouts/15/viewlsts.aspx

the opened page is empty

 

Perhaps someone faced a similar situation and can tell what caused it and how to fix it?

 

14 Replies

I will add screenshots:

 

11.jpg

 

333.jpg

The content and structure of the site contains the "Documents" directory, but when you try to open the link https://my_domain.com/purchasing/Shared%20Documents/Forms/AllItems.aspx a blank page is displayed. 

A blank page is also displayed when clicking on the "site content" link

https://my_domain.com/purchasing/_layouts/15/viewlsts.aspx

 

Sharepoint server 2019.

@Sergey_Lelekov 

 

after the installtion of cu 07-2021 KB 5001975 - Sharepoint 2019 on prem I have also the same problem

SharePoint 2019 July 2021 CU Build Number:

Language independent fix: 16.0.10376.20001
Language dependent fix: 16.0.10376.20001

@Sergey_Lelekov , even i am also facing the same issue, is there a way to uninstall the Security Patch update KB5001975, i think that is causing the problem, please suggest.

i posted the same here SharePoint2019 Blank White Screen 

best response confirmed by Sergey_Lelekov (New Contributor)
Solution

@Sergey_Lelekov , I fixed by installing the patch KB5001974 need to be installed along with the KB5001975 

@anandpeculiar 

 

Thank you. The problem is resolved.

Thanks
Thank you
I have this problem too after automatically installing July update for SharePoint 2019 core.

@Sergey_Lelekov - A big thank you for your post.  While the problem resolved by @anandpeculiar also solved my issue, the problem first manifested in a different way in our SharePoint Farm. 

 

Please forgive the length of the reply but I'm hoping it may further help others encountering the same problem.

 

In our environment the problem first appeared with a variety of Display Template related error messages similar to these two samples:

 

"The display template had an error. You can correct it by fixing the template or by changing the display template used in either the Web Part properties or Result Types. Cannot read property 'indexOf' of undefined (CoreRender: ~sitecollection/_catalogs/masterpage/Display Templates/Search/Item_CommonItem_Body.js)"

 

"The display template had an error. You can correct it by fixing the template or by changing the display template used in either the Web Part properties or Result Types. No included language files were loaded for locale (en-us) or the site's default language (en-us) for string ID (rf_RefinementAriaLabel_More). Please make sure you include the string IDs required by this Web Part in a language file that your Display Template references in the Site Collection Master Page Gallery. (LoadResource: )"

 

I eventually stumbled on to your post because I happened to notice the same occurrence of blank site management pages in our SharePoint Farm, too. @anandpeculiar's advice to install KB5001974 was the fix we needed.

 

Further digging led me to this blog announcing the July 2021 CU for SharePoint Server 2019. The blog states "Important: It is required to install both fixes [KB5001974 & KB5001975] (language dependent and independent) to fully patch a SharePoint server. This applies also to servers which do not have language packs installed. The reason is that each SharePoint installation includes a language dependent component together with a language independent component. If additional language packs are added later (only) the language dependent fix has to be applied again."

In our environment, the update service only applied KB5001975 but ignored the critical fact that KB5001974 should have been installed too!

 

Hope this helps others!!

Thanks! Installing KB5001974 resolved my issues as well!

I am having this problem but the above KB's are no longer relevant on our box. We only installed two KB's and it is now a blank site.

KB5003279 SP3 SQL Server Browser

KB5002028 Sec update for Sharepoint 2019 core.

 

Server is a 2016 Datacenter box. 

@ruttrowg, if you read the full text describing KB5002028 that you installed, which I highly recommend when you install any KB update for SharePoint, you may find you also have to install another KB to fully complete the update.  I've kindly copied the text I found in the KB link above so you can see it has a requirement in your KB similar to the requirement from my original situation.  Namely, the following excerpt:

This update also contains fixes for the following issues. To fix these issues completely, you have to install KB 5002034 together with this update [KB5002028]. [Issues fixed by installing BOTH KB's include:]

  • Fixes an issue in which a "No UI" error message is displayed if SharePoint group members can't share a modern team site.

  • Fixes an issue in which creating an office file in the root folder doesn't start the client application even if the document library is set to OpenInClient. 

  • Fixes an issue in which you can't access the News.aspx page after you install the August update for SharePoint Server. 

  • Fixes an issue in which the modified timestamp doesn't refresh after you upload a duplicate file and select to overwrite an existing file in the modern UI. 

  • Fixes an issue in which the uploaded messages are not correct when you upload duplicate files in the modern UI. 

  • Fixes an issue in which the elements that have an Aria role that require parent roles aren’t contained by them if the document library view is set to Tiles view. 

 

The thing I learned from my situation that you must check if issues arise after installing a SharePoint update is this...does the text of the KB require you to install OTHER KB's for the update to be fully completed?

 

If installing KB5002034 doesn't resolve the issue you'll need to keep digging.

 

Hope that Helps,

Ron

@Martinro73 Thanks for the information. That looks like the case we are having. I will try it once I get a window to work on server, and report back.

This worked great. Thanks!