Home > Wsus Self > Self Update Not Working 13042

Self Update Not Working 13042

Contents

I am not sure what the message means but it does not seem to stop my client updates from working (possibly apart from my server). Since WSUS installs components to the Default Web Site (always), that v-root must always be running. The DSS Authentication Web Service is not working. Go to the Selfupdate virtual directory Properties, click "Edit" under IP address and domain name restrictions. http://taskflowapp.com/wsus-self/self-update-is-not-working-id-13042.html

Any advice and/or tips would be greatly appreciated! in the event viewer of the Win Server 2008 (64), on which the WSUS version 3.1.6001.65 is installed. 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)Россия (Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 x 43 Christian Jones In my case, it was anonymous permissions in IIS on the selfupdate virtual directory. https://support.microsoft.com/en-us/kb/2000598

Wsus Self Update

Another possibility that I've seen from time to time is that the v-dir isn't pointing to the correct location. Posted by Jeff Guillet at 9:13 AM Labels: troubleshooting, WSUS Newer Post Older Post Home Subscribe to: Post Comments (Atom) Search This Blog Countdown to MVP Global Summit (Redmond, WA) 2016-11-07 I have done research and have not found anything to resolve this.

Related Comments Pramod Kumar says: July 21, 2011 at 10:26 PM I have getting error: "self update is not working" , tried to find resolution, read your article on web. SharePoint is not installed on it. They are both set up identically however the one under DW cannot be browsed and the one under WSUS can be browsed. Remove The Ssl (https) Site Binding For The Default Web Site 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

However there is no SharePoint services involved. Selfupdate Virtual Directory 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 & A further note that might be worth mentioning is that neither certificate services nor Microsoft Server active-sync are working. 0 LVL 4 Overall: Level 4 Message Active 4 days ago http://www.expta.com/2008/06/fix-for-self-update-is-not-working-in.html Resolve performance issues faster by quickly isolating problematic components.

After 10 minutes, the error was corrected automatically and the event log said all websites were working now. Wsus Selfupdate 403 Forbidden Creating your account only takes a few minutes. 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 Make sure that there is an entry for http on Port 80 with * as the IP address.

Selfupdate Virtual Directory

If you got the file not found or similar error, then here is what you should do. The Server Synchronization Web Service is not working. Wsus Self Update {{offlineMessage}} Store Store home Devices Microsoft Surface PCs & tablets Xbox Virtual reality Accessories Windows phone Software & Apps Office Windows Additional software Windows apps Windows phone apps Games & Entertainment Wsus Selfupdate Folder If WSS is installed on an alternate v-root and configured to use port 80, then the Default Web Site is not running.

Windows Update, regardless of WSUS installation or GPO settings, will almost always look for the SelfUpdate site on port 80 of the WSUS server. check my blog 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 I have ran the Solarwinds Diagnostic Tool for the WSUS Agent on both workstations and on the WSUS server itself and the only problem found was the WSUS Server connectivity "content" They simply provide the best products, in my opinion, and I like to work with the best. Wsus Test Selfupdate

To verify, open command prompt as administrator.  Go to c:\Program Files\Update Services\Tools and run this command: wsusutil checkhealth Then open the event viewer, application logs and see if you now get If not, create it with the Local Path pointing to C:\Program Files\Update Services\SelfupdateClick the Directory Security tab and ensure that Anonymous Access is allowedRestart IISVerify that the problem is fixed by Launch with Error and Won't Load SavedFiles Migrating SBS 2011 to Windows 2012R2 Quicken and QuickBooks Stopped Working on Windows 10Computer Why I Love VirtualMachines CategoriesCategories Select Category ADFS(1) proxy server(1) http://taskflowapp.com/wsus-self/self-update-is-not-working-13042.html 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

Once we changed the port on the default website and started it, this problem disappeared. Installselfupdateonport80.vbs Download By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. Restart the services and the problem should be solved.

x 46 Anonymous I was getting a bunch of errors: 12002, 12032, 12022, 12042, 12052 for WSUS 3.0 SP1.

Seems to be an issue when updating from 2.x-3.x. All rights reserved. To force a check to see if it fixes your problem, run "wsusutil.exe checkhealth" from "C:\Program Files\Update Services\Tools". Installselfupdateonport80.vbs Missing In combination with other HMS errors, there are additional possibilities to consider. 1 This discussion has been inactive for over a year.

Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are Connect with top rated Experts 20 Experts available now in Live! I fixed this error by going to Control Panel -> Administrative Tools -> Internet Information Services (IIS) Manager. have a peek at these guys As such the majority of these customers utilize some version of Small Business Server.

Another rather annoying thing is that if I browse any folder under DW, I am constantly prompted for username and password (domain\administrator) but it fails to browse after entering credentials.