Windows 2003 SP1 and error afterwards

Discussion in 'Windows Update' started by MikeD, Apr 13, 2005.

  1. MikeD

    MikeD Guest

    0x80244016 Error in the Windows Update after I installed SP1 on Windows
    2003. I installed SP1 on all Windows 2003 SP1 Servers at the same time,
    then I ran the Windows Update a few days later (Tuesday Updates) and
    received the error on the last server with SQL/SPS/ProjectServer.

    I have an automated build of Windows 2003 on my DC, SPS/Project Server and
    this error is only exhibited on the SQL/SPS/PS (same machine) - they were
    all built at the same time.

    Again, No problem on any of the 2 DC and File Server - only the
    SPS/SQL/Project Server (the one Windows Update does not run on -
    MikeD, Apr 13, 2005
    1. Advertisements

  2. MikeD

    Macsarang Guest

    I have the same problem on Windows 2003 with SQL/Project Server.
    The other 2003 servers do not show this problem.
    Macsarang, Apr 14, 2005
    1. Advertisements

  3. MikeD

    Peter Foldes Guest

    Courtesy of Pat Walters [MSFT]

    While this solution can sometimes work using the procedures you mention
    here, this is a step missing. The proxy configuration is an unknown
    quantity when someone wants to change it. The best thing to do, if you are
    going to change the proxy, is to clear the proxy cache, before applying the
    new proxy. For example:

    1. Click Start
    2. Click Run
    3. Type: cmd <Enter>
    4. In the Command Prompt, type: proxycfg <Enter> <-- To display proxy
    5. Type: proxycfg -d <-- To clear the proxy cache, and to set the proxy
    on direct access.
    6. Type: proxycfg -p prxyname:0000 <Enter> <-- Where prxyname is the
    NETBIOS name of your proxy server, and 0000 is replaced with the port your
    proxy server settings use to access the Internet over HTTP. As an example,
    if I had a proxy server with the name golf1 and I used port 80 to access the
    Internet over HTTP, then the command would be:
    proxycfg -p golf1:80 <Enter>


    Pat Walters [MSFT]
    Peter Foldes, Apr 14, 2005
  4. This is unacceptable modification to our production Project Server -
    Microsft needs to escalate this issue immediately.

    ~Jeffrey Smith, Apr 15, 2005
  5. MikeD

    Junglelasers Guest

    I too am experiencing this same error and when I submitted it to windows
    update was told that it was a server issue and I needed to call for tech
    support. Pay for a service that was caused by installing hotfixes from
    Microsoft. I do not think so. Microsoft needs to fix this error 0x80244016
    ASAP. Our problem started after hotfix 835732 was installed and we have not
    been able to get to windows update since.

    Junglelasers, Apr 18, 2005
    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.