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

Self Update Not Working 13042


Privacy statement  © 2016 Microsoft. I hold multiple certifications including MCITP:Enterprise Administrator and MCITP:Enterprise Messaging Administrator, MCSE:Messaging and CISSP.I am the author of The EXPTA {blog}, as well as a published author, contributing writer, and technical WSUS was installed on a machine that also had Exchange installed and was using the default website (on port 80) for web mail. Just an fyi for those who are still having the issue. check over here

x 51 Markus Mix In my case I found the sollution here: EV100327 (Event Viewer Errors 13042 13002 12002 12042 12052). For more information, see Help and Support Center at x 37 Vitaliy The following fixed the problem in my case. Click the Directory Security tab -> click Edit under Secure Communications and uncheck Require Secured Communications.

Wsus Self Update

Troubleshooting this problem over the last few days on and off has revealed an onslaught of potential causes; all of which I have tried and my WSUS symptoms are still the x 41 Anonymous I had the same problem with WSUS reporting a string of errors as shown below: Self-update is not working. Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL Join Now For the last couple months, I have been getting several times per day an error message recorded by the server running IIS with WSUS installed.

English: This information is only available to subscribers. Microsoft Customer Support Microsoft Community Forums TechCenter   Sign in United States (English) Brasil (Português)Česká republika (Čeština)Deutschland (Deutsch)España (Español)France (Français)Indonesia (Bahasa)Italia (Italiano)România (Română)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 Marked as answer by Arash Nabi Thursday, January 28, 2010 8:58 AM Unmarked as answer by Lawrence GarvinModerator Thursday, January 28, 2010 6:30 PM Thursday, January 28, 2010 8:58 AM Reply Remove The Ssl (https) Site Binding For The Default Web Site Once we changed the port on the default website and started it, this problem disappeared.

If something else has been installed to the DWS, it might have disabled anonymous access to the site. Selfupdate Virtual Directory The IIS was only bound to the internal IP and localhost address ( to allow internal access and avoid access from WAN. I don't think it has anything to do with other programs installed or using the same port but I haven't tracked the cause down yet. 0 Mace OP 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.

Join our community for more solutions or to ask questions. Wsus Selfupdate 403 Forbidden x 46 Anonymous I was getting a bunch of errors: 12002, 12032, 12022, 12042, 12052 for WSUS 3.0 SP1. Since WSUS installs components to the Default Web Site (always), that v-root must always be running. 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

Selfupdate Virtual Directory

Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? First Name Please enter a first name Last Name Please enter a last name Email We will never share this with anyone. Wsus Self Update So, if Spiceworks is installed, and listening on port 80, you have a problem. Wsus Selfupdate Folder They are both set up identically however the one under DW cannot be browsed and the one under WSUS can be browsed.

Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA Principal/CTO, Onsite Technology Solutions, Houston, Texas Microsoft MVP - Software Distribution (2005-2012) My MVP Profile: I'm experiencing a similar problem but I'm not sure check my blog All rights reserved. Shame Microsoft!!!! Share Point just happens to be a common cause. 0 Cayenne OP Lawrence (SolarWinds) Feb 26, 2014 at 5:37 UTC The EventID 13042 is caused when the /selfupdate Wsus Test Selfupdate

Windows Update, regardless of WSUS installation or GPO settings, will almost always look for the SelfUpdate site on port 80 of the WSUS server. If so, how was the challenge overcome in your experience? In combination with other HMS errors, there are additional possibilities to consider. 1 This discussion has been inactive for over a year. this content x 37 Anonymous ME920659 has information that may prove helpful for this problem.

The Client Web Service is not working. Installselfupdateonport80.vbs Download Thanks for the comment. Any one have any ideas?

x 45 Peter Van Gils I saw these errors on a DC that had just been upgraded to Win2003 SP2.

Permissions must be the same. Join & Write a Comment Already a member? Worked really well once i changed the alias and directory paths to match my system "C:/Program Files/Update Services/Selfupdate" this is on a Server 2008 R2 box with WSUS 3.0 SP2 on Installselfupdateonport80.vbs Missing They simply provide the best products, in my opinion, and I like to work with the best.

Join the community of 500,000 technology professionals and ask your questions. This got mine working. 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 have a peek at these guys I've resolved this by modifying the apache conf so that the spiceworks apache server services the /selfupdate resource (%ProgramFiles%\\Spiceworks\\httpd\\httpd.conf) by adding the following to the very end: # WSUS SelfUpdate Alias

Go to Solution 5 3 3 Participants fuzzyfreak(5 comments) LVL 4 dstewartjr(3 comments) LVL 47 SBS14 Microsoft IIS Web Server8 Larry Struckmeyer MVP LVL 21 SBS18 Microsoft IIS Web Server2 9 I fixed this error by going to Control Panel -> Administrative Tools -> Internet Information Services (IIS) Manager.