locked
WSUS 2016 - Error: Connect Error RRS feed

  • Question

  • Hello,

    My WSUS 2016 server has started to do this:

    In the event logs I see this, which I have done which hasn't helped, have you seen this before?

    I've pushed up the memory here too which didn't help:

    Can anyone advise on what I can do?

    Thanks

    Monday, June 26, 2017 3:40 PM

All replies

  • Hi TB303,

    1. Please check if click "Reset Server mode" could work;

    2. Please check if you select "Drivers" in "Products and classifications", it's not recommended to select drivers in classifications.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, June 27, 2017 2:35 AM
  • Hello,

    1. Never works
    2. Drivers are never selected.

    Restore server from backup?

    Tuesday, June 27, 2017 8:25 AM
  • Hi TB303,

    Do you patch the Server 2016 with the latest monthly rollup, if not, please install the update on Server 2016.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, June 28, 2017 7:36 AM
  • Yes we do Anne
    Wednesday, June 28, 2017 1:23 PM
  • It seems to crash when ever I select updates and then press approve.
    Wednesday, June 28, 2017 3:57 PM
  • My script will fix this issue.

    Have a peek at my Adamj Clean-WSUS script. It is the last WSUS Script you will ever need.

    http://community.spiceworks.com/scripts/show/2998-adamj-clean-wsus

    What it does:

    1. Remove all Drivers from the WSUS Database.
    2. Shrink your WSUSContent folder's size by declining superseded updates.
    3. Remove declined updates from the WSUS Database.
    4. Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs).
    5. Compress Update Revisions.
    6. Remove Obsolete Updates.
    7. Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days).
    8. Application Pool Memory Configuration to display the current private memory limit and easily increase it by any configurable amount.
    9. Run the Recommended SQL database Maintenance script on the actual SQL database.
    10. Run the Server Cleanup Wizard.

    It will email the report out to you or save it to a file, or both.

    Although the script is lengthy, it has been made to be super easy to setup and use. There are some prerequisites and instructions at the top of the script. After installing the prerequisites and configuring the variables for your environment, simply run:

    .\Clean-WSUS.ps1 -FirstRun

    and then

    .\Clean-WSUS.ps1 -InstallTask

    If you wish to view or increase the Application Pool Memory Configuration, you must run it with the required switch. See Get-Help .\Clean-WSUS.ps1 -Examples

    If you're having trouble, there's also a -HelpMe option that will create a log so you can send it to me for support.


    Adam Marshall, MCSE: Security
    http://www.adamj.org

    Thursday, June 29, 2017 3:02 AM
  • Hi TB303,

    Just to check if the tried Adamj.org's script, could it work? Welcome to feedback.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, July 4, 2017 5:48 AM
  • Missed this reply, I will try over the next day or so and feed back.

    Thanks

    Wednesday, July 5, 2017 9:24 PM
  • Hi TB303,

    Yeah, welcome to feedback.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, July 6, 2017 1:29 AM