locked
Wsus errors 12002, 12012, 12032, 12022, 12032, 12042, 12052 RRS feed

  • Question

  • I am trying to run WSUS 3 SP2, but am having problems.  I have clean loaded both 2003 Standard, as well as enterprise 2003 with all the latest service packs.  I load WSUS SP2, and get everything working through the console.  Everything works fine, until I reboot the server, as which time I get the 12002, 12012, 12032, 12022, 12042, and 12052 errors.  Once I get those errors, I can't get into the admin console, althought the update services service is running.  I can still see the the proper folder structure in IIS, and I have verified the IIS permissions on the folders. Any ideas?
    Tuesday, September 29, 2009 8:18 PM

Answers

  • Since you manually created %windir%\TEMP, did you confirm that the permissions were properly set on that resource?


    From Step 1: Confirm WSUS 3.0 SP2 Installation Requirements of the Step By Step Guide:


    The NT Authority\Network Service account must have Full Control permission for the following folders so that the WSUS Administration snap-in displays correctly:

    • %windir%\Microsoft .NET\Framework\v2.0.50727\Temporary ASP.NET Files
    • %windir%\Temp

    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    • Marked as answer by Eric Zhang CHN Thursday, October 8, 2009 7:35 AM
    Thursday, October 1, 2009 8:33 PM

All replies

  • I'm hoping there is more detail to this story that you've not shared. These errors generally occur because something in the WSUS environment has been RE-configured after installation has successfully completed, or something in the installation of IIS and/or WSUS was not successfully completed.

    If this is a clean Windows Server 2003 operating system, and no other installed applications, and WSUS is the only installed application, then:
    [a] WSUS should have been installed to the Default Web Site, and
    [b] The WSUS Health Monitoring service (which is what generates these errors) should be working perfectly and talking to WSUS on the Default Web Service.

    In addition, the fact that you cannot connect via the WSUS Admin console, combined with these errors, suggests that the WSUS Server is not where it was originally installed to.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Wednesday, September 30, 2009 4:54 PM
  • Hi,

    I'm not 100% sure what is happening, as I have installed this many times with no problems.  The only thing that I can think of, is that I'm installing in a EsX3.5 Environment.  I installed windows, did all the patches, installed IIS, and then WSUS.  I did a basic install taking all the defaults through the install, which completed fine.  The only that appears out of the ordinary is that I have to create c:\windows\TEMP folder manually in order for the wizard to start at the end of the WSUS install.  I can however still load up the admin utility if I don't create that folder.  I then went into the admin console, and configured everything up.  After I was done I rebooted, and the errors started coming up.  I have reloaded many times with standard windows, enterprise windows, 2008, and I always seem to end up with the same errors.  I don't however have a WSUS Health Monitoring Service listed under services.  Not sure if that is a problem or not.  Is there anything else I should be checking?
    Thursday, October 1, 2009 7:09 PM
  • Since you manually created %windir%\TEMP, did you confirm that the permissions were properly set on that resource?


    From Step 1: Confirm WSUS 3.0 SP2 Installation Requirements of the Step By Step Guide:


    The NT Authority\Network Service account must have Full Control permission for the following folders so that the WSUS Administration snap-in displays correctly:

    • %windir%\Microsoft .NET\Framework\v2.0.50727\Temporary ASP.NET Files
    • %windir%\Temp

    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    • Marked as answer by Eric Zhang CHN Thursday, October 8, 2009 7:35 AM
    Thursday, October 1, 2009 8:33 PM
  • Hi,
    I have got a similar issue:
    I am installing Wsus 3.0 SP2 on a new Virtual Win2003 R2 Sp2.
    I followed the guide and gave the permissions "The NT Authority\Network Service account must have Full Control permission for the following folders so that the WSUS Administration snap-in displays correctly:

    • %windir%\Microsoft .NET\Framework\v2.0.50727\Temporary ASP.NET Files
    • %windir%\Temp"
    The installation ends corretly but when I press finish I got an error " An unexpected error occurs ..."
    In the event viewer I have the errors

    12002, 12012, 12032, 12022, 12042, 12052 and 7053

    So something with IIS I guess.
    What can I check?
    Thank u.
    Tuesday, November 24, 2009 11:33 AM
  • In the event viewer I have the errors

    12002, 12012, 12032, 12022, 12042, 12052 and 7053

    So something with IIS I guess.

    The answer to this post is provided in my response to the original question posted in this thread:
    I'm hoping there is more detail to this story that you've not shared. These errors generally occur because something in the WSUS environment has been RE-configured after installation has successfully completed, or something in the installation of IIS and/or WSUS was not successfully completed.

    If this is a clean Windows Server 2003 operating system, and no other installed applications, and WSUS is the only installed application, then:
    [a] WSUS should have been installed to the Default Web Site, and
    [b] The WSUS Health Monitoring service (which is what generates these errors) should be working perfectly and talking to WSUS on the Default Web Service.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Tuesday, November 24, 2009 5:40 PM
  • I have my WSUS  installed in a Certificate Authority server, thus, in IIS I can see two websites: "Default Site" and "WSUS" . Is that valid?

    I am having this same issue and the solution related to granting permissions to "C:\Windows\Temp" and "%windir%\Microsoft.NET\Framework\v2.0.50727" did not work.

    I wonder if in the GPO I should place: "https://server.domain.com/WSUS:8531" instead of "https://server.domain.com:8531."

    Thanks.


    Luis Olías Técnico/Admon Sistemas . Sevilla (España - Spain)

    Monday, September 28, 2015 8:28 AM
  • Thanks a lot Lawrence.

    I don't see the user 'NT Authority\Network Service' in the security tab. I found "Network service" . 

    In my event log, I see:

    Warning. Event 1309. Source: ASP.NET 2.0.50727.0 

    I see this warning after applying your above recommendation in these two folders:

    • %windir%\Microsoft .NET\Framework\v2.0.50727\Temporary ASP.NET Files
    • %windir%\Temp


    Luis Olías Técnico/Admon Sistemas . Sevilla (España - Spain)


    • Edited by Luis Olias Monday, September 28, 2015 10:55 AM
    Monday, September 28, 2015 10:55 AM
  • Thanks, and IISRESET
    Friday, July 21, 2017 3:42 AM
  • I had a similar issue .Running IISreset temporarily solving it but problem happens again.

    This solution solved mine.

    Wednesday, October 18, 2017 8:23 AM