Update Services not working anymore on SBS 2011.

Hello, I have a problem with a Windows SBS 2011.
I have always used this server to deploy Windows updates to a network of about 20 clients.

Now Windows Update Services have just stopped working, I get an 80072EE2 error on any machine I try to update (the server or the clients).

It looks like the Services have totally gone bonkers. If I try to open the relative mmc from Server Manager, mmc crashes. So I can't even collect info from the console.

The Windows Update engine version should be 3.0 SP2.

Do you have any suggestions on how to tackle this? Never happened before. Thanks.
Daniele BrunengoIT Consultant, Web DesignerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

The DB option set for the wsus is internal, or sql server is being used? The initial setup had growth rates too low that are insufficient meaning to get a single update the sql server has to frequently allocate an additional meg of space each time. adjust to use percent growth for the data file.


Running cleanup wizard might be helpful to purge unneeded/expired data consuming space unnecessarily.
Daniele BrunengoIT Consultant, Web DesignerAuthor Commented:
I think the script you linked to only runs on Windows Server 2016. It gives me a command not found error on SBS 2011.

Which db option does your wsus use? MS## or you have it setup to write to an SQL server?

please post the output from
net start | find /i "SQL"

the wsusutil is the tool to use c:\program files\update services\....
it includes checkhealth, etc..

Does the system have enough space ? checking the log of the update service may shed light what might be going on......
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

Daniele BrunengoIT Consultant, Web DesignerAuthor Commented:
If I remember correctly, I never changed anything in the initial configuration.
This is the output of the command.
 SQL Full-text Filter Daemon Launcher (SBSMONITORING)
   SQL Full-text Filter Daemon Launcher (SHAREPOINT)
   SQL Server VSS Writer

Open in new window

The cleanup tool starts but it stops after a couple of minutes with this error:
Errore imprevisto nella console di amministrazione di WSUS. Potrebbe trattarsi di un errore temporaneo. Provare a riavviare la console di amministrazione. Se il problema persiste, 

Provare a rimuovere le preferenze persistenti relative alla console eliminando il file wsus in %appdata%\Microsoft\MMC\.

System.ComponentModel.Win32Exception -- Il servizio non ha risposto alla richiesta di avvio o controllo nel tempo previsto


Stack Trace:
   in System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
   in System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
   in Microsoft.UpdateServices.UI.SnapIn.Wizards.ServerCleanup.ServerCleanupWizard.OnCleanupComplete(Object sender, PerformCleanupCompletedEventArgs e)

Open in new window

I have not run into this error before, so not sure whether a .NET Framework update led to this issue....

c:\program files\update services\tools
there is the wsusutil
running it get a report on the health of the setup.
See if you have windows updates errors in the eventvwr application log.

check space.

If you have another system where you can install the wsus MMC console only to access the server to eliminate the possibility that the SBS .net framework is messed, profile corrupt (using another login into the system to access the WSUS MMC)
Daniele BrunengoIT Consultant, Web DesignerAuthor Commented:
The disk is half empty.  The script you linked above gives a timeout error after a while too.

wsusutil didn't generate anything in sys events, but there are 3 recurring errors:

Livello	Data e ora	Origine	ID evento	Categoria attività
Errore	24/03/2018 22:17:00	Windows Server Update Services	12032	(9)	Il servizio Web di sincronizzazione server non funziona.
Errore	24/03/2018 22:17:00	Windows Server Update Services	10022	(7)	L'ultimo tentativo di sincronizzazione catalogo ha avuto esito negativo.
Errore	24/03/2018 22:17:00	Windows Server Update Services	13032	(6)	Molti computer client non hanno inviato segnalazioni al server negli ultimi 30 giorni. Fino a ora ne sono stati rilevati 28 con tale comportamento.

Open in new window

Not sure to wici script..

the other option is to issue the reset to wsusutil.

As noted, I've not run into this issue.

does the SUSD reside on the sql server that sharepoint and SBSmonitoring
if so, check the database properties, options and see at what rate is the data file permitted to grow.
Change from meg to 5%-10% and see if that fixes the issue.

It sounds as though your situation fits the above, i.e. the wsus process tries to load data but has to wait every few seconds for the server to allocate an additional meg of space in the db which lasts only for mere seconds and the cycle begins anew.

you do not seem to have the MS## type formated internal DB the WSUS would be installed with......
Daniele BrunengoIT Consultant, Web DesignerAuthor Commented:
The used space is huge, but the database is on a 4TB drive which has more than 2TB free. I tried some steps from a MS forum post by someone who had almost exactly my same problem, but still the cleanup script fails with a timeout. I'll try a reset in a few days.
The space on the filesystem is less of an importance than the settings on the database server for the database and the rte of growth set.
The WSUs when installed sets a low growth rate on the database and log files, if not mistaken both default to being set to 2M this means if you are downloading 20 update metadata, the process will sequentially request the allocation of additional space in the database, the repeated nature of these requests would result in the different functions of failing, raising the rate of growth to be 15% will resolve this issue. As the requests for additional space in the db will be less frequent on a per retrieval session.
Daniele BrunengoIT Consultant, Web DesignerAuthor Commented:
So, I tried to reset the whole service but I still get the connection problem. It looks like the server can't connect to Microsoft servers for some reason.
do you have a proxy in the environment, or a restriction on the external firewall as a means to limit exposure did not grant this system direct access....
Daniele BrunengoIT Consultant, Web DesignerAuthor Commented:
No, there's no actual block on the network. I'll double-check, but there's never been one and nobody has ever touched these devices but me.
Daniele BrunengoIT Consultant, Web DesignerAuthor Commented:
So I fixed this by completely uninstalling and re-installing Wsus. Nothing else seemed to work.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Hi Daniele,

For those that follow, what steps did you take to uninstall and reinstall WSUS?


Daniele BrunengoIT Consultant, Web DesignerAuthor Commented:
I followed the steps you can find here: https://glennopedia.com/2016/02/25/wsus-and-sbs/comment-page-1/

I'll paste them here so they are available through Experts Exchange too:

Remove WSUS.
Go to Control Panel then Programs and Features.
Highlight Windows Server Update Service 3.0 SP2 and choose Uninstall.
Check all three boxes to remove the database, logs and downloaded updates.
Complete the uninstall wizard.

Reinstall WSUS.
Open an administrative command prompt
Change directories to C:\Program Files\Windows Small Business Server\Bin\CMPNENTS\WSUS_SP2
The install will take anywhere from 2-10 minutes depending on hardware.  To verify the install is complete look for an event ID 1042 in the application event log.  If the install crashes, just rerun the above command again.

Perform the SBS customizations.
Click Start, click Administrative Tools, and then click Microsoft Windows Server Update Services
In Update Services, expand the name of the server, and then click Options.
Click Products and Classifications, and then on the Products tab, verify that all check boxes are selected.
In the Products and Classifications dialog box, click the Classifications tab, and then check the following boxes:
Critical Updates
Definition Updates
Security Updates
Service Packs
Update Rollups
In Options, click Update Files and Languages, click the Update Languages tab, choose the option Download updates only in these languages, and then verify that English is selected.
In Options, click Synchronization Schedule, click Synchronize automatically, and then, in First synchronization, change the time to 10:00:00 P.M.  Click OK.
In Update Services, expand Computers, click All Computers, and then in Actions, click Add Computer Group.  Add the following computer groups:
Update Service Excluded Computers
Update Services Client Computers
Update Services Server Computers

Update WSUS so that it will work with Windows 8 and higher clients.
Download the Microsoft update KB2734608.
Install the update.
Reboot the server.  The server must be rebooted before the first synchronization with Microsoft update servers.  If it is not, then WSUS and clients may require additional steps to repair.

On top of these steps, I also had to install KB2720211, which should be supposedly contained within the aforementioned update but it somehow wasn't or wasn't working.

Anyway, that was it. Everything started working again on all clients and the server. I switched all clients on via wake-on-lan on saturday night and let them update, since they had been stuck for at least a month or two. Nobody was the wiser on monday morning.
Great - thanks for that:-)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Updates

From novice to tech pro — start learning today.