Home > Wsus Self > Self Update Is Not Working Event Id 13042

Self Update Is Not Working Event Id 13042

Contents

They are both set up identically however the one under DW cannot be browsed and the one under WSUS can be browsed. Check that UsingSSL is set to 0 (if you are not using SSL). 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? If so, how was the challenge overcome in your experience? check over here

Reply ↓ Leave a Reply Cancel reply Your email address will not be published. An example of English, please! Required fields are marked *Comment Name * Email * Website Search for: Recent Posts [Tutorial] Using Fiddler to debug SAML tokens issued from ADFS [How-To] Deploy HUB Licensed VMs in Azure Do the following to fix the problem: Open IIS Manager, right click the Default Web Site, and look at the properties tab. https://support.microsoft.com/en-us/kb/2000598

Wsus Self Update

Server 2008 R2 Reply ↓ Rick September 19, 2016 at 3:32 pm This results in removing all SSL requirements for the WSUS server's IIS web site. Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? Join the community Back I agree Powerful tools you need, all for free. Social Media Icons Proudly powered by WordPress

Our WSUS server has two network cards (LAN, WAN). Windows Update, regardless of WSUS installation or GPO settings, will almost always look for the SelfUpdate site on port 80 of the WSUS server. Privacy statement  © 2016 Microsoft. Wsus Selfupdate Folder If something else has been installed to the DWS, it might have disabled anonymous access to the site.

These articles are provided as-is and should be used at your own discretion. Selfupdate Virtual Directory 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 To force a check to see if it fixes your problem, run "wsusutil.exe checkhealth" from "C:\Program Files\Update Services\Tools". http://www.expta.com/2008/06/fix-for-self-update-is-not-working-in.html Any advice and/or tips would be greatly appreciated!

Did this article help? Wsus Selfupdate 403 Forbidden the clients can get update and can connect to server... I was forced to unistall everything and start from scratch. Click on bindings in the action pane.

Selfupdate Virtual Directory

x 43 Christian Jones In my case, it was anonymous permissions in IIS on the selfupdate virtual directory. Read More Here SharePoint does not exist anywhere on our network. 0 Thai Pepper OP a2e Feb 25, 2014 at 9:39 UTC I don't believe it's specific to share point. Wsus Self Update The co-existence requirements of Windows Sharepoint Services and Windows Server Update Services have been discussed incessantly over the past five years and a simple web search on "WSUS" and "Sharepoint" should Wsus Test Selfupdate 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.

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)Россия (Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 http://taskflowapp.com/wsus-self/self-update-not-working-13042.html 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 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. 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 Remove The Ssl (https) Site Binding For The Default Web Site

I get that message every now and then, even after what I suggested, and clients update fine. See example of private comment Links: WSUS: SelfUpdate Tree is not working Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links... thanks for posting it Reply ↓ Jimmy Wang January 12, 2016 at 10:54 pm Thanks, it has been fixed. this content The DSS Authentication Web Service is not working.

Join the community Back I agree Powerful tools you need, all for free. Installselfupdateonport80.vbs Download The WSUS clientdiag.exe tool said everything was fine from the client end, but there were no updates to see. Expand the tree for the SBS Server then for Sites.

Restart the services and the problem should be solved.

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 you do - remove the IUSR_xxxxx account from the guests group on the local machine and restart IIS (iisreset). Help Desk » Inventory » Monitor » Community » home| search| account| evlog| eventreader| it admin tasks| tcp/ip ports| documents | contributors| about us Event ID/Source search Event ID: Installselfupdateonport80.vbs Missing Log Name: Application Source: Windows Server Update Services Date: 10/3/2013 4:53:26 AM Event ID: 12042 Task Category: 9 Level: Error Description: The SimpleAuth Web Service is not working.

Tags: Microsoft Windows Server Update Services (WSUS) Review it: (76) Solarwinds® Diagnostic Tool for the WSUS AgentReview it: (3) Reply Subscribe RELATED TOPICS: WSUS 3.0 and Existing Web Sites- Self-Update Not x 46 Anonymous I was getting a bunch of errors: 12002, 12032, 12022, 12042, 12052 for WSUS 3.0 SP1. In combination with other HMS errors, there are additional possibilities to consider. 1 This discussion has been inactive for over a year. have a peek at these guys Check the application logs afterwards.

You may get a better answer to your question by starting a new discussion. 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). Also, another possible resolution - remove the GUESTS account from the USER RIGHTS ASSIGNMENT:DENY ACCESS TO THIS COMPUTER FROM THE NETWORK. Permissions must be the same.

TECHNOLOGY IN THIS DISCUSSION IIS Join the Community! The WSUS Administration site was set up on 8350, as per usual and all settings (security and registry) looked correct. Click the Directory Security tab -> click Edit under Secure Communications and uncheck Require Secured Communications.