broonster Posted July 19, 2017 Report post Posted July 19, 2017 Hi There, I have a single site server (v1702) with WSUS and SUP role on the same box. Everything has been running fine (mostly) for years but all of a sudden my client machines can no longer get updates. When syncing with the ClientWebService in IIS I get errors like these. The 0x80072ee2 error is a timeout i believe I tried tweaking some IIS settings and increasing the RAM for the WSUS application pool thinking IIS was struggling with but that hasn't helped. Looking at the logs I see stuff like this syncmgr.log wcm.log I also tried running the WSUS clean-up wizard thinking the DB has got out of hand but I can't even use that as I keep getting the reset node error as below every few minutes. I was considering uninstalling the SUP role and re-installing it but I'm not 100% sure how to go about that. I have SCUP running on the same server and it has added a few products like Adobe Flas/Reader/Acrorobat that I'm concerned I'll lose if in re-install. Anyone got any ideas as I've been at this for days now? Quote Share this post Link to post Share on other sites More sharing options...
Apexes Posted July 20, 2017 Report post Posted July 20, 2017 Not a useful reply, but just an FYI - i was on the same boat for months. My SUP and WSUS was hosted on the same site as my primary being destroyed by CPU, thought it was the IIS app pools, but was not. I ended up moving it to its own standalone server and installed the SUP on that as a brand new install on a new DB.Runs so much smoother since i've done that.I inherited the WSUS environment by somebody else who hadn't kept it indexed or run regular maintenance on it. it was at least 3 years old and had ran itself into the ground. Also running on 1702 Quote Share this post Link to post Share on other sites More sharing options...
Apexes Posted July 20, 2017 Report post Posted July 20, 2017 btw, your wsus server name isn't censored on 3rd screenshot Quote Share this post Link to post Share on other sites More sharing options...
broonster Posted July 21, 2017 Report post Posted July 21, 2017 6 hours ago, Apexes said: Not a useful reply, but just an FYI - i was on the same boat for months. My SUP and WSUS was hosted on the same site as my primary being destroyed by CPU, thought it was the IIS app pools, but was not. I ended up moving it to its own standalone server and installed the SUP on that as a brand new install on a new DB.Runs so much smoother since i've done that.I inherited the WSUS environment by somebody else who hadn't kept it indexed or run regular maintenance on it. it was at least 3 years old and had ran itself into the ground. Also running on 1702 I just moved my SUP and WSUS server to a new host but now I'm having issue with the new WSUS server access the old content from the old SUP/WSUS server. My WSUS DB is also in need to maintenance. I'll be honest I didn't realise it need to be regularly maintained but I've learnt my lesson now. Quote Share this post Link to post Share on other sites More sharing options...
broonster Posted July 21, 2017 Report post Posted July 21, 2017 6 hours ago, Apexes said: btw, your wsus server name isn't censored on 3rd screenshot Quote Share this post Link to post Share on other sites More sharing options...
Apexes Posted July 21, 2017 Report post Posted July 21, 2017 I'd suggest creating a whole new DB, let it sync over the weekend and get brand new content. sorry, meant your last screenshot! Quote Share this post Link to post Share on other sites More sharing options...
