WSUS Issues

[yhttech]

I had a WSUS server on one of my servers and it was working normally for about 2 years. All of a sudden when I try to manage it, it tells me that it couldn't connect to the server to reset the node. I reset the node, restarted IIS and WSUS services, still no luck. So I tried to remove it from my management console and re-add the connection. When I try to re-add the connection, it tells me that SQL is not running on the server, I never removed it. There are no other admins. Is it as simple as just re-installing SQL server express?

[LeMarchand]

I had a WSUS server on one of my servers and it was working normally for about 2 years. All of a sudden when I try to manage it, it tells me that it couldn't connect to the server to reset the node. I reset the node, restarted IIS and WSUS services, still no luck. So I tried to remove it from my management console and re-add the connection. When I try to re-add the connection, it tells me that SQL is not running on the server, I never removed it. There are no other admins. Is it as simple as just re-installing SQL server express?

 

In case you don't get a reply from someone who knows more about this than me: whenever I've had the "reset node" problem restarting the server has generally fixed it. If that's not feasible are relevant sql services running? I have also inadvertently deleted WSUS before and just followed a "first time setup" guide without a problem(!). If you get it up and running without razing it to the ground first, you might want to run the WSUS Server Cleanup Wizard.

[yhttech]

I don't see SQL server services at all in the services console. I guess I need to re-install them.

[LeMarchand]

I don't see SQL server services at all in the services console. I guess I need to re-install them.

 

IIRC when I had to start from scratch, I just installed the basic option offered by the WSUS wizard.

[RobD]

This any good:

Linky

[Simcfc73]

Mine did the exact same thing, I ended up reinstalling it on another server and pointing to the old files so they didn't download again, sorry not much help.

[ADMaster]

There is also the internal database as an option depending on how you installed it. I believe the internal database is default, so you may have never had SQL setup.

Also look at the IIS application pool for wsus make sure it is running. I have had that issue in the past.

Increase its memory and adjust timeout are the changes I made.

[computer_expert]

Do you have KB3148812 or KB3159706 installed on your WSUS server?

 

If you do, then you need to do some manual tweaks as detailed here: https://support.microsoft.com/en-gb/help/3159706/update-enables-esd-decryption-provision-in-wsus-in-windows-server-2012-and-windows-server-2012-r2

 

https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/

[Achandler]

Microsoft released an update that compeltely borked it up is most likely your problem.

 

Happened to me with the first one, I fixed it and then the 2nd one ruined it after! The manual intervention isn't 100% either which is what is even more bizarre, quality assurance at its finest! You can uninstall the updates to fix it, but then there is a requirement on for oen of them to be installed for a later update. It's a vicious circle and a complete mess if your effected, as some people's WSUS works fine with no intervention, some works with the intervention and others report the fixes don't work.

[Davit2005]

In built database seems to be the one that threw that problem at me as well. Didn't matter how many times I restarted the server. Not having the time to sit down and fix the issue I jus blew the server away and setup another Virtual.

[sultan966]

Hi, I Just had the same problem. I have solved it. It was crashing.

 

I have done the following:

 

1. Update Windows server by doing Windows update. -- Did not help.

 

2. Updated SCCM 2012R2 to the latest version. - Did not help.

 

3. Restarted the server - Did not help.

 

4. Used the following command - Did not help. (KB3159706 breaks WSUS)

 

“C:\Program Files\Update Services\Tools\wsusutil.exe” postinstall /servicing

 

The link for the article:

 

ESD Decryption Update KB3159706 Breaks WSUS on Server 2012 R2 - MrChiyo.com

 

5. Increase IIS Private Memory limit - Has helped - WSUS Not crashing : The article link:

 

https://www.404techsupport.com/2016/03/iis-wsus-private-memory/

 

6. Used WSUS Server cleanup wizard - Probably has helped.

Open WSUS Console - Click on Options - Server Cleanup Wizard

 

 

 

Points 5 and 6 did the trick.

 

Cleaning WSUS took two days. I thought it is hung. But by reading some articles I found it may take time - sometimes a week. So, I was just patient and let it run for two days. It cleaned the mess. Postinstall servicing command is a good idea as well. It does not do any harm.

 

After doing everything: Use the iisreset command in command prompt. It will start working.

Edited January 20, 2017 by sultan966

[mikes]

I have this too since a recent WSUS update... I remember an update broke it last year, now I am getting:

 

 

System.IO.IOException -- The handshake failed due to an unexpected packet format.

 

going to try WSUSUTIL... it seems after every update now you have to check everything to make sure MS haven't broken something (like when they randomly changed GPOs without notifying anyone)