Value does not fall within the expected range

Discussion in 'Update Services' started by Dominik.Brosch, May 16, 2007.

  1. Hello Group,

    I just upgraded to WSUS3.0 from the former 2.0 Version.

    Since this update I getting following error at the eventlog:

    Event id: 364

    Content file download failed. Reason: Value does not fall within the
    expected range. Source File:
    /msdownload/update/v3-19990518/cabpool/windows6.0-kb931768-x86_963df6f7ade8fbd016d8d0da636e6577247846b8.cab
    Destination File:
    D:\WSUS\WsusContent\B8\963DF6F7ADE8FBD016D8D0DA636E6577247846B8.cab.

    The WSUS-Server does not download any update.
    I notice that 186,31 MB of files are needed for Updates.

    Pls. help me, because I do not have any idea, how to solve.

    Any help will be appreciated.

    Thanks in advance

    Dominik Brosch
     
    Dominik.Brosch, May 16, 2007
    #1
    1. Advertisements

  2. The most likely issue is the firewall/proxy not properly supporting the HTTP
    v1.1 protocols.

    Upgrading from WSUS2 to WSUS3 would not introduce this error, as it either
    already existed, or somebody concurrently 'reconfigured' your
    firewall/proxy.

    --
    Lawrence Garvin, M.S., MCTS, MCP
    Independent WSUS Evangelist
    MVP-Software Distribution (2005-2007)
    https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E

    Everything you need for WSUS is at
    http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx

    And, almost everything else is at
    http://wsusinfo.onsitechsolutions.com
    .....
     
    Lawrence Garvin \(MVP\), May 18, 2007
    #2
    1. Advertisements

  3. Hello Lawrence,

    We are using ISA2004 as firewall/proxy. As I understood HTTP v1.1 is
    supported. Isn't it? Before upgrading to WSUS3.0 I do not notice any error
    like this.

    Regards

    Dominik
     
    Dominik.Brosch, May 21, 2007
    #3
  4. Correct. ISA2004 is supported.

    The other thing to check is to ensure that the proxy authentication
    configuration on your WSUS server is still valid. There were some issues
    noted with the upgrade process and proxy configurations during the beta, and
    I don't know if those were fully resolved, or not. I had forgotten about
    this particular issue when I offered my comment about the upgrade not
    introducing any such errors. It could be a manifestation of the upgrade if
    your proxy configs have been modified.

    --
    Lawrence Garvin, M.S., MCTS, MCP
    Independent WSUS Evangelist
    MVP-Software Distribution (2005-2007)
    https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E

    Everything you need for WSUS is at
    http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx

    And, almost everything else is at
    http://wsusinfo.onsitechsolutions.com
    .....
     
    Lawrence Garvin \(MVP\), May 21, 2007
    #4
  5. Setting the proxy-settings again, corrects the problem.
    Thanks for your support.

    Dominik
     
    Dominik.Brosch, May 22, 2007
    #5
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.