WSUS downstream replicas high CPU after deleting content folder and running wsusutil.exe reset

We noticed that our WSUS content folder was growing out of control on the master and downstream replicas.  The decision was made to delete everything in the content folders on all WSUS servers and issue a wsusutil.exe RESET command on all WSUS servers as well as change every patch to UNAPPROVED on the master server.

Everything worked great and very quickly on the master which appears to be functioning fine but the downstream replicas are stuck.  The CPU is maxed on a core and WSUS is running queries indefinately.  There is absolutely nothing in the wsus content folder on these replica servers now and we have not approved a single patch after setting them all back to unapproved.  What is going on and how do I fix this?

Here is what is running in SQL on SUSDB:

SUSDB.dbo.spResetStateMachineAndReEvaluate;1  This query is running

SUSDB.dbo.spGetRevisionInfo;1 This query is blocked by the first one

SUSDB.dbo.spGetRevisionIdListForCache;1 This query is blocked by the first one

The downstream replicas are also not able to sync with the master while this is going on now.

How do I fix the downstream replicas so they start syncing again and stop with the maxxed CPU and SUSDB queries running with all the locking?

We are running WSUS fully patched on 2008 R2 for both master and downstream servers.  The SUSDB is running on SQL 2008 R2 fully up to date not sql express or windows database.
Edited by davidb1234 2 hours 50 minutes ago
Who is Participating?
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.

James HaywoodCommented:
The content folders will not fill up untill there are approved updates to download. In my experience once WSUS goes wrong its impossible to properly fix. Its much quicker to uninstall and reinstall.

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
NBFAuthor Commented:
That is what I did.  I uninstalled and reinstalled.  It still wouldn't sync. it had an error about a dependent update.  I repointed the replicas to Microsoft and did a manual sync and then back to the master server and now it is working.
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 Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.