Error description class no registered. You can run into this problem if you change the server's ip address after the initial installation. Event ID: 13042 - Self-update is not working Event ID: 12002 - The Reporting Web Service is not working Event ID: 12032 - The server synchronization Web Service is not working x 37 Vitaliy The following fixed the problem in my case. check over here
The content is "Cannot connect to 'HTTP://SERVERNAME'. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking Extracted from: http://www.eventid.net/display.asp?eventid=13042&eventno=8857&source=Windows%20Server%20Update%20Services&phase=1 0 LVL 47 Overall: Level 47 Windows Server 2003 26 Microsoft IIS Web Server 8 Anti-Virus Apps 6 Message Active 1 day ago Expert Comment by:dstewartjr2010-04-05 Use If the server's IP is not listed under the exceptions, self update will fail.
Event ID: 12042 The SimpleAuth Web Service is not working. To dstewartjr: I've gone through the WSUS config checklist, without making any changes. I recommend very highly that you read through Kent Agerlund's postand take proactive steps to ensure that the app pool does not hit the upper memory limit and that WSUS is 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).
So after performing a lot of troubleshooting and also using WSUS health check I just cannot figure out how to get rid of these following event ID errors. Click the Directory Security tab -> click Edit under Secure Communications and uncheck Require Secured Communications. So let's check the WSUS Admin Console: Well, it's definitely not just ConfigMgr having trouble connecting. Event Id 12072 Wsus x 27 EventID.Net See EV100404 (WSUS KB2720211 : Common issues encountered and how to fix them) on suggestions about troubleshooting WSUS.
Event ID: 12002 Source: Windows Server Update Services Source: Windows Server Update Services Type: Error Description:The Reporting Web Service is not working. Event Id 12022 If the problem persists, try restarting IIS, SQL, and the Update Services Service." I suspect that the error in point #1 is quite significant. 0 LVL 47 Overall: Level 47 Event ID 12042 description: The SimpleAuth Web Service is not working. http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=.NET%20Framework&ProdVer=2.0.50727&EvtID=12022&EvtSrc=Windows%20Server%20Update%20Services&LCID=1033 Deny write permissions.
Login here! The Dss Authentication Web Service Is Not Working. All and all good experience and something to keep my busy. This got mine working. x 44 Ajay Kulshreshtha Event though this is the first error to show up in Event Viewer, the root cause in our case was that the default website could not start
x 20 EventID.Net From a newsgroup post: "Make sure the value for PortNumber under the key HKLM\SOFTWARE\Microsoft\Update Services\Server\Setup is set to the correct port (the one your WSUS site is on)". http://www.eventid.net/display-eventid-12002-source-Windows%20Server%20Update%20Services-eventno-9383-phase-1.htm Register Help Remember Me? Event Id 12032 yes 2. Wsus Error 12022 English: Request a translation of the event description in plain English.
The errors were gone. Now on to the next issue :0 Quote + Reply to Thread « Previous Thread | Next Thread » Social Networking & Bookmarks Bookmarks Digg del.icio.us StumbleUpon Google Tweet CompTIA First, Just open a new email message. You'll want to go over the settings in this KB article: The Microsoft Windows Server Update Services (WSUS) SelfUpdate service does not send automatic updates Quote higherho Senior Member Join Wsus The Client Web Service Is Not Working 12022
Cisco, Cisco Systems, CCDA™, CCNA™, CCDP™, CCNP™, CCIE™, CCSI™; the Cisco Systems logo and the CCIE logo are trademarks or registered trademarks of Cisco Systems, Inc. This breaks stuff, so a manually repair of .NET2 should get you up and going in no time 0 Back to top of the page up there ^ MultiQuote Reply #18 Also, another possible resolution - remove the GUESTS account from the USER RIGHTS ASSIGNMENT:DENY ACCESS TO THIS COMPUTER FROM THE NETWORK. x 49 Alexey Alexandrov This error occurred when I upgraded WSUS from WSUS 2 to WSUS 3.
Microsoft Customer Support Microsoft Community Forums Details Event ID: Source: We're sorry There is no additional information about this issue in the Error and Event Log Messages or Knowledge The Api Remoting Web Service Is Not Working. If you have any questions, then please Write a Comment below! WSUS 3 used MMC console and not HTTP ( like WSUS 2) IN the connect server type your computer name if is not working check your security DB, IIS, Folder Sam
See the link to “WSUS: SelfUpdate Tree is not working” for the full article. Event ID 13051 description: No client computers have ever contacted the server. 0 Back to top of the page up there ^ MultiQuote Reply #5 Bumpy Member Group: Regular Members I'm currently running Windows Server 2003 SP2 with all of the latest security updates. Wsus Event Id 12022 Event ID: 12012 The API Remoting Web Service is not working.
Event ID 12032 description: The Server Synchronization Web Service is not working. However, I still blew the whole WSUS away and start from scratch. The API Remoting Web Service is not working. The errors have event IDs of: 12002, 12012, 12022, 12032, 12042, 12052, and 13042.
Log Name: Application Source: Windows Server Update Services Event ID: 12052 Task Category: 9 Level: Error Description:Â The DSS Authentication Web Service is not working. Reply ↓ Horstworst January 26, 2016 at 7:17 am Thanks, this fixed the errors for me! Enter the product name, event source, and event ID.