WSUS on web server breaks No Touch Deployment application

After installing WSUS on a web server, our No Touch Deployment application quit working.  We started getting a System.IO.FileNotFoundException exception when trying to retrieve an exe file from the web server.

After weeks and weeks of working with Microsoft on this they finally figured out why.

"the problem is WSUS turns on compression on the web server. There is a known bug with VS.NET Framework that dependent assemblies fail to download when compression is enabled on the server. This bug with compression has been fixed in the beta of next version of VS.NET.

The workaround is to turn off the compression. Greg might be able to provide more insight on if we can turn off compression with WSUS and what happens if we do that.

The other option is on the client machines you can go to IE->Tools->Internet Options->Advanced->Uncheck Use HTTP 1.1 and Use HTTP 1.1 through proxy connections.

This works as HTTP 1.0 doesn't support compression. "

 

 

1 Comment

  • I had a similar problem adn followed your instructions but with no results, error is listed below. Answer listed at bottom

    Server Error in '/WusAdmin' Application.
    --------------------------------------------------------------------------------

    File or assembly name System.Web.RegularExpressions, or one of its dependencies, was not found.
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.IO.FileNotFoundException: File or assembly name System.Web.RegularExpressions, or one of its dependencies, was not found.

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Assembly Load Trace: The following information can be helpful to determine why the assembly 'System.Web.RegularExpressions' could not be loaded.


    === Pre-bind state information ===
    LOG: DisplayName = System.Web.RegularExpressions, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    (Fully-specified)
    LOG: Appbase = file:///C:/Program Files/Microsoft Windows Update Services/Administration
    LOG: Initial PrivatePath = bin
    Calling assembly : (Unknown).
    ===

    LOG: Publisher policy file is not found.
    LOG: No redirect found in host configuration file (c:\windows\microsoft.net\framework\v1.1.4322\aspnet.config).
    LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\config\machine.config.
    LOG: Post-policy reference: System.Web.RegularExpressions, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    LOG: Attempting download of new URL file:///C:/Program Files/Microsoft Windows Update Services/Administration/bin/System.Web.RegularExpressions.DLL.
    LOG: Attempting download of new URL file:///C:/Program Files/Microsoft Windows Update Services/Administration/bin/System.Web.RegularExpressions/System.Web.RegularExpressions.DLL.
    LOG: Attempting download of new URL file:///C:/Program Files/Microsoft Windows Update Services/Administration/bin/System.Web.RegularExpressions.EXE.
    LOG: Attempting download of new URL file:///C:/Program Files/Microsoft Windows Update Services/Administration/bin/System.Web.RegularExpressions/System.Web.RegularExpressions.EXE.



    Stack Trace:


    [FileNotFoundException: File or assembly name System.Web.RegularExpressions, or one of its dependencies, was not found.]
    System.Web.UI.BaseParser..cctor() +0

    [TypeInitializationException: The type initializer for "System.Web.UI.BaseParser" threw an exception.]
    System.Web.UI.BaseParser.set_CurrentVirtualPath(String value) +0
    System.Web.UI.ApplicationFileParser.GetCompiledApplicationType(String inputFile, HttpContext context, ApplicationFileParser& parser) +132
    System.Web.HttpApplicationFactory.CompileApplication(HttpContext context) +43
    System.Web.HttpApplicationFactory.Init(HttpContext context) +485
    System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +170
    System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +414


    I did however manage to work around this by upgrading to . net 2.0 (dontnetfx.exe) and changing what ASP.NET Wsus uses in IIS.

    Install .net 2.0, Open IIS, locate WSUS Administration ( i do not have Wsus installed under the defualt web site), right click on WSUS Administration, click the tab ASP.NET, change the ASP.Net version to 2.0.

    I uninstalled WSUS, removed all .net packages and left over files on hard drive before finding that all that is needed was to change the ASP version is IIS

    hope this helps some one else.

Comments have been disabled for this content.