Hello All,
First of all, let me begin by saying that I know I committed an oops. Unfortunately, my attempts to remedy the situation by relying on previous forums, etc., hasn't had a desired effect. So allow me to explain my situation.
We have a WSUS Server with about a hundred clients. Our WSUS Content folder is approximately 9GB. A few weeks ago, we noticed that MS updates across the board were failing with a 80244019 error; it appeared that WSUS was no longer communicating with our clients. Following the recommendation from geeks hangout, (I can't post the URL) I ran a wsusutil /reset.
Big mistake.
This caused sqlservr.exe to hit the server at about 95-100% for over two weeks. Eventually, I gave up on any forward progress on the wsusutil reset and terminated the process. While our CPU usage had returned to normal, I couldn't get any life out of our WSUS service. It continued to report a database error, and clients were unable to pull updates from it. Eventually, I figured out that the original problem was a corruption in our .NET 4 updates on the WSUS server. After repairing them and downloading new .NET 4 updates to the server, clients finally started to pull updates again.
Unfortunately, sqlservr.exe is still poking its head around and refuses to give in. After leaving it alone for the weekend, hoping it would finish up and go away, I found today that it's still running. Thankfully, our clients are at least able to pull updates from the server, but I would like end the sqlservr.exe process since it's taking up a lot of the CPU.
Any suggestions?