uberstein

Aye as it turns out, the issue remains. Still get the 12012,12010 event combos seemingly randomly. 12002,12022,12032,12042 and 12052 also sometimes show up in the same string, but that's far rarer to see all 7 errors in a row, though after 10 minutes you get the corresponding "service is working properly" events. Every time. Mostly it's 12012 (API Remoting Web Service) that is showing up by itself, then 10 minutes later the 12010 event to say it's working. I've thought about completely removing WSUS and IIS, rebooting the server and starting over from scratch, but...that's a lot of work to do to fix errors that don't really have any effect on WSUS---everything works perfectly even with the errors.

Hmmm. mrfac, you may just have earned a great deal of gratitude. I just now tried your eventid link (I went there waaayy back in early 2007 when I first saw this problem and wasn't able to find much) and found something new. Specifically, midway down the page: Quote: Mihai Andrei (Last update 10/22/2007): From a newsgroup post: "Make sure the value for PortNumber under the "HKLM\SOFTWARE\Microsoft\Update Services\Server\Setup" key is set to the correct port (the one your WSUS site is on)". I checked, and the value of PortNumber on my WSUS server was 8530. Well, the WSUS (default as well) website is on port 80, so I changed the PortNumber value to 80 (decimal) and restarted IIS. This didn't seem to clear anything up (I still saw the errors in the logs), but subsequently this past weekend I bounced the server due to some Windows Updates, and I have yet to see any problems so far after the reboot. Still too early to tell, but I'm going on vacation for a week, and if when I get back the logs are still clean, I'll go ahead and say (looong-standing) problem solved! Gonna cross my fingers here. Thanks for the link and suggestion.

Wow. I've been seeing this little issue for months and months, (since WSUS 3 actually) and it's nice to see I'm not alone. I wish I had something constructive to add. I google this every few months just to see if anyone has found anything new about it, but I have yet to find anything that solves the problem. I wonder if there aren't a lot more people experiencing this than this thread would indicate, but it's just that many don't examine their logs too closely so they don't notice, since this doesn't seem to impair WSUS function at all. I am running WSUS 3.1 on Windows Server 2003 Standard R2. Just to confirm, this is what happens: Every 12 hours to 3 or 4 days (although since the last recent WSUS Service Pack it's been at least once a day) I get a string of errors in the Windows Application Event Log: 13042 12002 12012 12032 12022 12042 12052 each corresponding to a service that is "not working." Then, exactly 10 minutes later, events: 13040 12000 12010 12030 12020 12040 12050 corresponding to events telling me each aforementioned service IS "working correctly." I've also seen JUST the 13042/13040 combination a few times instead of all 7 services as well. The only thing I haven't yet tried, and I always thought this might fix it, is to uninstall and reinstall IIS6 out from under WSUS 3, but I've been afraid I'd somehow bork the WSUS database in the process so I've been reluctant to try it. This seems like it's a problem somehow with IIS6, but I honestly have no idea. As has been stated, this is somewhat academic since it doesn't seem to affect WSUS working properly at all. Everything works, all computers get the proper approved updates, synchronizations always work, etc etc. But it still drives me nuts. I like my logs clean, yeah, I'm OCD I know. :-)