Welcome to deBUG.to Community where you can ask questions and receive answers from Microsoft MVPs and other experts in our community.
1 like 0 dislike
369 views
in SharePoint Server by 16 25 33
edited by

Recently, we have applied SharePoint 2019 Cumulative January 2020 CU (KB 4493162, KB 4493161) in our SharePoint 2019 farm, the new Cumulative update is installed successfully, but I had noted that the RSS Web Part is broken although it was worked before!

An unexpected error occurred processing your request. Check the logs for details and correct the problem

I have checked the logs and I have found the RssWebPart Exception

RssWebPart: Exception handed to HandleRuntimeException.HandleException System.ArgumentNullException: Value cannot be null.

I am not sure if the RSS Web Part is broken due to the new cumulative update. but it's the last action we have did! Also, we have checked another farm that not updated yet, and the RSS web is working!

How I fix this RSS web part exception? Can I rollback the newly installed SharePoint cumulative update?


1 Answer

1 like 0 dislike
by 54 119 241
selected by
 
Best answer

RSS Webpart is broken in SharePoint 2019/2016/2013

It's a known issue that occurs if you have patched your farm with SharePoint Cumulative Update December 2020 or SharePoint Cumulative Update January 2020.

As per Stefan blog (Escalation engineer in Microsoft), this issue SharePoint RSS web part is broken is planned to be solved in the coming SharePoint February 2021 Cumulative Update.

So If you already installed SharePoint Cumulative Update December 2020 or SharePoint Cumulative Update January 2020, you will encounter this issue, and you have to wait for SharePoint February 2021 Cumulative Update to fix it.

Note: You can't roll back the installed SharePoint Cumulative update, Check How to apply a new SharePoint patch best practices.


Update: RSS Webpart broken issue has been solved

RSS Web part broken issue was fixed in SharePoint February 2021 Cumulative Update

Check Also

If you don’t ask, the answer is always NO!
...