locked
The WSUS content directory is not accessible. RRS feed

  • Question

  • I'm getting the following error from my WSUS server when trying to download content:

    - System

      - Provider

       [ Name]  Windows Server Update Services

     

      - EventID 12072

       [ Qualifiers]  0

     

       Level 2

     

       Task 9

     

       Keywords 0x80000000000000

     

      - TimeCreated

       [ SystemTime]  2017-02-21T18:45:04.000000000Z

     

       EventRecordID 51580

     

       Channel Application

     

       Computer amc-wsus02.amcfirst.com

     

       Security

     

    - EventData

       The WSUS content directory is not accessible. System.Net.WebException: The remote server returned an error: (404) Not Found. at System.Net.HttpWebRequest.GetResponse() at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckContentDirWebAccess(EventLoggingType type, HealthEventLogger logger)

    I gave the WSUS content share permissions and is accessible by domain users:

    everyone = Full Control

    Network Service = Full Control

    WSUS Administrators = Full Control

    Domain Users = Full Control

    I'm at my wits end with this.


    Tuesday, February 21, 2017 7:26 PM

Answers

  • The issue was in IIS. I reconfigured the Physical path to the content directory, using the drive letter and path instead of unc path.
    • Marked as answer by Kulibaboo Tuesday, April 18, 2017 12:54 PM
    Tuesday, April 18, 2017 12:54 PM

All replies

  • Hi Kulibaboo,

    1. What is the version of your WSUS server?

    2. Where do you store the WSUS content folder, it's not recommended to store the WSUS Content folder in a network path;

    3. Please check the permission of the WSUS Content folder, check if NETWORK SERVICE has full permission.

    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, February 22, 2017 6:19 AM
  • The WSUS server is Server 2012 R2 standard.

    The content folder is located on the D:\ of the same server.

    Network Service has full control.

    I was able to fix that issue by changing the physical path to the the content folder in IIS fro UNC path to D:\WSUS\WSUSContent.

    I have a new error in the event logs now.  As you can see below its not very helpful of whats going on.

    - System
    - Provider
    [ Name] Windows Server Update Services
    - EventID 10032
    [ Qualifiers] 0
    Level 2
    Task 7
    Keywords 0x80000000000000
    - TimeCreated
    [ SystemTime] 2017-02-22T10:17:39.000000000Z
    EventRecordID 51744
    Channel Application
    Computer amc-wsus02.amcfirst.com
    Security
    - EventData

    The server is failing to download some updates.


    Wednesday, February 22, 2017 4:13 PM
  • Hi Kulibaboo,

    Please reset the WSUS to re-download the update files to WSUS Content folder:

    C:\program files\update services\tools>wsusutil reset

    Check if after the reset, WSUS server could download the files, if not, check the event log again, especially check if there are event 364.

    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.

    Friday, February 24, 2017 3:14 AM
  • The issue was in IIS. I reconfigured the Physical path to the content directory, using the drive letter and path instead of unc path.
    • Marked as answer by Kulibaboo Tuesday, April 18, 2017 12:54 PM
    Tuesday, April 18, 2017 12:54 PM
  • How did you do it?
    Monday, February 5, 2018 4:46 PM
  • How did you do it? thanks.
    Tuesday, February 6, 2018 8:15 AM
  • Preferred IPV4 over six, rebooted server and WSUS working again. Server 2012 R2.
    Thursday, April 19, 2018 7:55 AM
  • You can change it in the IIS console.

    Under the Advanced settings of the Content folder.

    
    Cheer,

    Ramon


    Cheer,

    Ramon

    Monday, June 11, 2018 1:15 PM
  • Had the same issue.... Physical path to the content directory was configured with drive letter already... changed it to UNC path...and voila.... updates started downloading
    Wednesday, October 30, 2019 2:14 PM