SOLVED Reporting view corrupted after in-place upgrade

[avi_ei]

Hi,

I've done an in-place upgrade to my WSUS server OS from Server 2012 R2 to Server 2019.

Everything seems OK by now except the reports that are corrupted (I see the headers but not the actual list of computers or updates)

When I've exported the report to Excel format and made the rows wider i saw the following message "Error: Subreport could not be shown"

I haven't found any solutions on the net.

My WSUS is running on the internal WID database.

Any suggestions ?
Has anyone made a WSUS Server OS in-place upgrade from 2012R2 to 2016/2019 and it's working OK ?

Thanks,

 

[Garth]

I don't believe that it is supported to do an inplace upgrade of WSUS like that. I think that you need to remove wsus, reboot and install WSUS again.

 

[avi_ei]

Thanks,
I've removed the SQL CLR Types & ReportViewer and installed them again and the issue was resolved.
But now i have a new issue - today i approved the February patch Tuesday but the download hasn't started.
In the event viewer saw event that the content directory is not ready and that the directory is not accesible.
Looked at the IIS and saw that everything seems OK but testing the folder access gave me an Authorization error - tryed some advices found on the Net but with no success.
eventually i've noticed that the Content disk has a different drive letter the it was before the upgrade - changed the path in the IIS but still no success.

Now I'm trying to make a move content procedure with wsusutil so it will rewrite the files and the new Content location and see if it helps.

If no luck with that i'll restore the server 12 days back to the previous state before the OS in-place upgrade.

Any Suggestions ?
Does the uninstall and re-install of the WSUS (remove WSUS role - Reboot - Install the role again) won't delete all my groups, views, approvals, computers state etc. ?

 

[avi_ei]

Well,
I've rolled back the server from backup to OS version 2012 R2 and everything is working OK.

In the future i'll install a new server (2019) make it a child of the current WSUS until all the settings and definitions will synchronised and then will make it primary by configuring the new server to pull updates from Microsoft instead of the old server.

TNX.