Company about
Home > Wsus Self > Self Update Is Not Working 13042

Self Update Is Not Working 13042

Contents

After this, I ran wsusutil.exe checkhealth and all of the errors disappeared. x 49 Alexey Alexandrov This error occurred when I upgraded WSUS from WSUS 2 to WSUS 3. x 45 Peter Van Gils I saw these errors on a DC that had just been upgraded to Win2003 SP2. Custom search for *****: Google - Bing - Microsoft - Yahoo Feedback: Send comments or solutions - Notify me when updated Printer friendly Subscribe Subscribe to EventID.Net now!Already a subscriber? check over here

Shame Microsoft!!!! It appears Sharepoint was installed and the "Default Web Site" in Internet Information Servers (IIS) was stopped and Sharepoint Web site was using port 80 All I needed to do to It's more of something conflicting on that port. In IIS Manager, go to Default website > Selfupdate > Right-click Properties > Directory Security tab > IP addres and Domain restriction EDIT > and check "by default all computers will https://support.microsoft.com/en-us/kb/2000598

Wsus Self Update

Comments: EventID.Net EV100621 (Windows Update Services Multiple Errors in Event Viewer) provides a solution for this type of problem (the steps the reconfigure WSUS). Our WSUS server is currently running on ports 8530(http) and 8531(https). Suggested Solutions Title # Comments Views Activity SBS Certificate Error 7 45 84d 1 CPU vs 2CPU in Hyper-V 9 84 81d SYSVOL and NETLOGON affected by crypto virus 7 62

Join the community Back I agree Powerful tools you need, all for free. Help Desk » Inventory » Monitor » Community » Home WSUS 3.0 and Existing Web Sites- Self-Update Not Working by Symph0ny on Jun 10, 2011 at 12:43 UTC | WSUS 0Spice Edit: On a ghetto configuration. Remove The Ssl (https) Site Binding For The Default Web Site I am running WSUS 3.0 SP2.

Notify me of new posts via email. Selfupdate Virtual Directory If the entry points to another port or isn't there, you probably have to make some other adjustments in IIS.  Here is what I think you may find. And checked my wsus health status. Thanks for the comment.

Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We Wsus Selfupdate 403 Forbidden x 46 Anonymous I was getting a bunch of errors: 12002, 12032, 12022, 12042, 12052 for WSUS 3.0 SP1. Make sure that there is an entry for http on Port 80 with * as the IP address. SharePoint is not installed on it.

Selfupdate Virtual Directory

Exchange How to Monitor Bandwidth using PRTG (very basic intro, 3:04) Video by: Kimberley Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to https://community.spiceworks.com/topic/143171-wsus-3-0-and-existing-web-sites-self-update-not-working Connect with top rated Experts 20 Experts available now in Live! Wsus Self Update Thanks! 0 Back to top of the page up there ^ MultiQuote Reply Search Topic Forum Home WSUS & Patch Management |-- WSUS 3 Server |-- Client issues |-- Utilities & Wsus Test Selfupdate The Client Web Service is not working.

Do the following to fix the problem: Open IIS Manager, right click the Default Web Site, and look at the properties tab. check my blog The WSUS clientdiag.exe tool said everything was fine from the client end, but there were no updates to see. x 46 Eric Barb WSUS requires that a "SelfUpdate" virtual directory exist on the website that is hosted on port 80. i still get Error messages, but clients can download and install updates here is screenshots from IIS 7 what to do next? Wsus Selfupdate Folder

In the example in this thread, the fundamental problem is that Sharepoint was installed on port 80 in an alternate v-root, effectively rendering the Default Web Site dead -- the real Login here! When those resources are unavailable (because a Sharepoint - 80 v-root exists), the noted errors are recorded in the Application Event Log.Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA Principal/CTO, Onsite Technology Solutions, this content Join the community of 500,000 technology professionals and ask your questions.

If you do - remove the IUSR_xxxxx account from the guests group on the local machine and restart IIS (iisreset). Installselfupdateonport80.vbs Download The fundamental issue here is that you appear to have installed Windows Sharepoint Services on PORT 80, which is blocking the ability of the WSUS Health Monitoring service to access the x 37 Vitaliy The following fixed the problem in my case.

Our WSUS server has two network cards (LAN, WAN).

I get that message every now and then, even after what I suggested, and clients update fine. it simply # make spiceworks fill in the hole that WSUS still checks for # on port 80 since spiceworks is already on port 80. # (keeps errors out of error Bottom line, the 13042 is the HMS saying "I cannot find the /selfupdate stuff." It might also be useful to verify in the Application Event Log that you are getting only Installselfupdateonport80.vbs Missing Finally, if there's a mismatch between the SSL configuration of the IIS Default Web Site, and what WSUS thinks the state of SSL is, that could also produce this error.

All clients are indeed getting update offers, and the server itself that has WSUS installed on it is also getting the updates offered. See example of private comment Links: WSUS: SelfUpdate Tree is not working Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links... I also work with various other platforms and products, usually in the form of migrations.Microsoft is not a "religion" for me. have a peek at these guys The WSUS Administration site was set up on 8350, as per usual and all settings (security and registry) looked correct.

If it can't find it (Default Website not installed), or can't access it (SSL enabled, Anonymous Authentication denied), you get the "Self-update is not working error" (Event ID 13042). Perhaps you have added a new site that you want to host and have given it Port 80, changing the default web site to another port, like 8080.  This would would By creating an account, you're agreeing to our Terms of Use and our Privacy Policy Not a member? Once [::1] was bound to the website the error when away.

Proposed as answer by Marco Shaw Thursday, January 21, 2010 4:26 PM Unproposed as answer by Arash Nabi Friday, January 22, 2010 9:24 AM Thursday, January 21, 2010 4:26 PM Reply http://eventid.net/display.asp?eventid=13042&eventno=8857&source=Windows Server Update Services&phase=1 0 LVL 47 Overall: Level 47 SBS 14 Microsoft IIS Web Server 8 Message Active today Expert Comment by:dstewartjr2011-04-04 Comment Utility Permalink(# a35316590) This may help