I have ran into this a couple of times now when moving site roles in Configuration Manager 2012. When uninstalling the WSUS server components from in this case the Primary Site server to move it to a dedicated server instead the Management Point on the Primary Site server started giving HTTP Error 500 Internal Server Error:
This was caused by the removal of the WSUS role on the server which removed almost all the files installed by the Windows Update Services but not the configuration written in the ApplicationHost.config file. The Applicationhost.config file tries to call the .dll installed by the WSUS Server but no longer exists on the system.
From the Applicationhost.config file:
<scheme name=”xpress” doStaticCompression=”false” doDynamicCompression=”true” dll=”C:\Program Files\Update Services\Webservices\suscomp.dll” staticCompressionLevel=”10″ dynamicCompressionLevel=”0″ />
Running the following command will remove all references to the module installed by WSUS.
%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']
After that the Management Point is up and running again.
Thank you. It solved our problem.
Nice post, thank you.
I could uninstall WSUS from Windows Server 2012 R2 Essentials safely.
Made the mistake of fooling around on our production Site Server. Installed WSUS and then removed it. The next day I realized clients weren’t getting their policies. I knew it was the removal of SUS that did it. I was panicking and thought I was going to have to do a restore. Ran this command and it fixed the issue beautifully. Thanks a lot!!
Thank you!!!
It solved our problem.
Windows Server 2012 R2 Essentials
Very very useful post, required to resolve a very critical issue caused by WSUS removal!!!
Thanks for taking the time to help others.
Also worth mentioning that the Application Catalog failed with http 500 due to WSUS removal also. The above fix resolved same.
You saved my day! 🙂 Thanks a lot!
I was facing exactly this issue.
Perfect solution. Thank you!!!
Thank you!
Saved our day.
I installed WSUS on our production 2012r2 Essentials server and thought it was great! But then I could not get reporting to work, and did not like the resources it was consuming on the only server in house that does a few other roles as well (Quickbooks db and Mongo db). Thought it would be smart to uninstall, and was confronted with this lovely 500!
Thanks!
Thank you . It worked for me
Thanks, saved me a load of time working this out.
Brilliant fix. Thanks very much
Had an issue with WSUS uninstall, the install finished fine, I restarted the server and RWA no longer accessible (error 500). The above fixed fantastically well!
MANY MANY THANKS!!!
This fixed us right up, THANK YOU!!!
Thank you for this helpful post! Are there any considerations to be made for deleting SUSDB? In our case, we won’t be migrating it to a different SQL instance. Thanks again!
Thanks, this worked flawlessly to fix a Server Essentials Connector 500 issue.
Great solution, thank you very much! This saved our day(s).
I have been struggling with this problem and just gave up and installed WSUS again.
Now I will try our solution.
Regards Janne
Thank you!
You saved me.
Thanks for this..saved my day!!
when I run the command I get this message
“ERROR ( message:Cannot find requested collection element. )”
please help , thanks
Thank you this was exactly my problem.
For the record, this solution also works with Windows Server 2016! After I uninstalled WSUS, it broke my web server, and it was driving me crazy. Running the appcmd cleared up the error right away. Thanks for the fix!
I recommend fixing this properly otherwise you will see a huge increase in WSUS traffic due to no compression being used. 10:1 difference. I’ll blog it soon. Search for configmgrgeekspeak suscomp.dll in a week or two.
PS disregard my comment above if you’re permanently removing WSUS from the server you run the command on for good.
Thank you!
You saved me.
Perfect solution.
Thank you so much – spent the last 2 days trying to fix this!
Thanks for this, after spending ages Googling, your fix saved the day.
Only worked for me when running it with extra quotes around the name parameter
.\appcmd.exe set config -section:system.webServer/httpCompression “/-[name=’xpress’]”
I Can’t thank you enough for this. I was on the verge to reinstall SCCM (WS 2016), but luckily i have found this.
Thank you very much!!!!
I was unable to install sccm client on devices, in SCCM console, clients showing as active but grayed out…
I owe you one beer if you ever visit Serbia. 🙂
Cheers,
Thank you very much
I’m using SCCM 1810 with my WSUS on a Windows Server 2016 VM. This is what did the trick for me:
cd C:\Windows\System32\inetsrv
.\appcmd.exe set config -section:system.webServer/httpCompression “/-[name=’xpress’]”
I had to ensure the single quotes were correct. Double check them if you are like me and copy and paste them.
I sincerely appreciate everyone who posts these forms of solutions. I have been working on my WSUS issues for over three weeks now and this did the trick for me. Thanks everyone
Another thank you from me. I had removed the SUP and WSUS role, and then started getting Management Point and Multicast Service Point errors. The fix above worked perfectly. SCCM 1810 on Server 2012 R2.
omg you saved me! Thank you!
Hi,
I am getting error same like as image shown at above.
Please help to us.
Thank you so much !! You saved the my time and Work.
This worked like charm
Cmd > Run as admin
and executed the script you mentioned resolved my issue
Thanks a million.. Just work strait!!
Thanks a lot. Your article helped me in fixing the issue.
Unbelievable it’s still not fixed. This is a broken uninstaller. MS should fix it…
And IIS should produce a more helpful error description.
thanks this helped me today, I migrate the wsus role to another server, the original is still holding the management point role and freaked out when I saw that 500 internal error, running this command fixed it. Thanks