WSUS is not working and WSUS Server Cleanup Wizard is not working.
Hello,
We have a WSUS server running on a Windows 2016 server. When I run the "Server Cleanup Wizard", I am seeing the attached error.
I found the attached script from the internet for Windows 2012 WSUS. I am not sure if I can run it on a Windows Server 2016 WSUS server.
Someone who know how to fix this please advise.
Many thanks!!!
wsus-database-error.bmp
wsus-cleanup-updates-v4.txt
We have a WSUS server running on a Windows 2016 server. When I run the "Server Cleanup Wizard", I am seeing the attached error.
I found the attached script from the internet for Windows 2012 WSUS. I am not sure if I can run it on a Windows Server 2016 WSUS server.
Someone who know how to fix this please advise.
Many thanks!!!
wsus-database-error.bmp
wsus-cleanup-updates-v4.txt
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
if you are using windows internal database, i'm not surprised; happened frequently when running cleanup wizard or selecting a large amount of updates to accept or decline. switching to sql (even the free express edition) works so much better; haven't had a single database issue since
you could do that. though the issue will happen again at some point
Perhaps I need to initialize the WSUS database.
you could do that. though the issue will happen again at some point
ASKER
How do I uninstall WSUS, remove the current database and setup everything?
Did you try PoshWSUS cleanup? Did you set the IIS pool private memory to 0?
https://github.com/proxb/PoshWSUS
Do not uninstall WSUS
https://github.com/proxb/PoshWSUS
Do not uninstall WSUS
Those MMC errors happen most of the times due to DB or IIS problems.
Before trying to re-build the WSUS entire DB, you can run the cleanup wizard, but instead of selecting all the check-boxes at once, do it one by one, pressing the BACK button each time. This way the cleaning operations will take less time, and you will be able to identify where is(are) the blocking issue(s).
It is also probable that when you finish the cleaning operations the WSUS DB gets "self-fixed" and you will not need to do anything else.
If you are not able to run the cleanup wizard, then proceed to re-build the DB or re-install the WSUS Server role. If I were in your shoes I would re-install entirely the WSUS server role, thus removing all the noise from the past. There are plenty of tutorials on the web on how to do it.
Before trying to re-build the WSUS entire DB, you can run the cleanup wizard, but instead of selecting all the check-boxes at once, do it one by one, pressing the BACK button each time. This way the cleaning operations will take less time, and you will be able to identify where is(are) the blocking issue(s).
It is also probable that when you finish the cleaning operations the WSUS DB gets "self-fixed" and you will not need to do anything else.
If you are not able to run the cleanup wizard, then proceed to re-build the DB or re-install the WSUS Server role. If I were in your shoes I would re-install entirely the WSUS server role, thus removing all the noise from the past. There are plenty of tutorials on the web on how to do it.
ASKER
Thanks.