mikkydoos Posted May 24, 2016 Posted May 24, 2016 (edited) Hi all, Go and check your WSUS console. Its most likely broken or your client aren't receiving updates. I doscovered mine wasn't working after trying to do a forced update from a client to my WSUS server and it kept bugging out. If you dare, disconnect from the server in MMC and try to reconnect (at your peril) The error I was getting was "Cannot connect to server. SQL is not running." There is another post on here from @robsonma but I found a few more steps to get WSUS running after update KB3148812 breaks it. Read these: https://blogs.technet.microsoft.com/wsus/2016/04/22/what-you-need-to-know-about-kb3148812-part-two/ https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/ The fix: A manual operation... https://support.microsoft.com/en-us/kb/3159706 Worked for me. Hope this helps. Edited May 24, 2016 by mikkydoos 4
mikes Posted June 7, 2016 Posted June 7, 2016 My WSUS broke too with a similar SQL error - I couldn't get the WID to work, it didn't like the NETWORK USER account or something I ended up comissioning a new server VM and re-installing it from scratch... and afer the latest batch of Windows Updates, it promptly stopped working again damn MS software is garbage... don't they test this stuff? (to them that's the end user's job) I have 706, going to hope the manual fix works...
dapaulio Posted June 7, 2016 Posted June 7, 2016 I had this and fixed it by removing both KB's The symptoms will be WSUS Error: Connection Error when loading the console The event viewer will log an WSUS error with a load of SQL related information events KB3148812 was the original "fix" that broke wsus and was later pulled from wsus. KB3159706 was released to fix KB3148812 however if you are unlucky enough to deploy KB3159706 after KB3148812 was pulled from WSUS this also breaks wsus in the same way The Solution is to remove and decline both KB3148812 and KB3159706 then restart your server.
mikes Posted June 7, 2016 Posted June 7, 2016 I ran the manual fix as described above and it has fixed it luckily.. My WSUS server (the server OS itself) updates directly over the Internet from MS, perhaps I should change it to update from its own WSUS, I am guessing that is how most people have theirs? I can hold off a week or so then and let other people beta test MS's updates for them
dapaulio Posted June 7, 2016 Posted June 7, 2016 I ran the manual fix as described above and it has fixed it luckily.. My WSUS server (the server OS itself) updates directly over the Internet from MS, perhaps I should change it to update from its own WSUS, I am guessing that is how most people have theirs? I can hold off a week or so then and let other people beta test MS's updates for them that may be a wise idea. my wsus server updates from its own database rather than internet.
mikkydoos Posted June 9, 2016 Author Posted June 9, 2016 So after further investigating.... My WSUS server is up and running but not distributing updates to most of my network. New clients are reporting but not updating. Anyone else got this?
dapaulio Posted June 9, 2016 Posted June 9, 2016 When you say most... any similarities between the computers that are affected? Firewall port?
mikkydoos Posted June 9, 2016 Author Posted June 9, 2016 When you say most... any similarities between the computers that are affected? Firewall port? Nope. All the same. Was working 'perfectly' until the prob of this thread
garethEds Posted October 3, 2016 Posted October 3, 2016 Hi all, Go and check your WSUS console. Its most likely broken or your client aren't receiving updates. I doscovered mine wasn't working after trying to do a forced update from a client to my WSUS server and it kept bugging out. If you dare, disconnect from the server in MMC and try to reconnect (at your peril) The error I was getting was "Cannot connect to server. SQL is not running." There is another post on here from @robsonma but I found a few more steps to get WSUS running after update KB3148812 breaks it. Read these: https://blogs.technet.microsoft.com/wsus/2016/04/22/what-you-need-to-know-about-kb3148812-part-two/ https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/ The fix: A manual operation... https://support.microsoft.com/en-us/kb/3159706 Worked for me. Hope this helps. You might just have saved my WSUS server here. I noticed it last week and even re-installed my WSUS installation. It still wasn't working properly - Googling found some issues but only today am I remembering to search Edugeek. Thank you - will try things tomorrow or maybe VPN in later.
garethEds Posted October 4, 2016 Posted October 4, 2016 Right, well I'm a bit stuck. Those updates are not on my WSUS server - so they cannot be removed. However if I run the "C:\Program Files\Update Services\Tools\wsusutil.exe" postinstall /servicing - command and it fixes it for a while but then it dies again. Sigh. Gareth
garethEds Posted October 4, 2016 Posted October 4, 2016 That command seemed to fix it - but when I run a manual sync I am losing connection and am asked to 'Reset Server Node'. Running that command fixes it. Tearing my hair a bit now. GJE
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now