asked on

Event ID 13042: Self-Update is not working

I get this error code on my SBS 2008 server every 6 hours. My PCs are updating, but they're all doing it individually once a week at a time set by a GPO. I'd prefer to get updates only once a week, but is there a way to get the WSUS service working & to be able to set a schedule to it? What is likely to be stopping the WSUS service?

Don

Go over....

http://support.microsoft.com/kb/920659

http://blogs.technet.com/b/asksbs/archive/2008/06/02/troubleshooting-multiple-errors-on-wsus-13042-13051-and-12032.aspx

matavai

ASKER

Hi dstewartjr, the second link there could definitely be a possibility, the first one is pre-SBS 2008 & the instructions don't work. I do change my administrator password occasionally, but hadn't done it for several weeks prior to the Event ID 13042 errors started on June 9th. The second link gives instructions for how to reset the IUSR user password, but I can't find anything that refers to a username beginning IUSR, is this something that has also changed with SBS 2008?

Looking back at what I was doing on June 9th, I was going through the GPO setup trying to solve a remote desktop problem, & possibly at the same time, I changed the timing of the Windows updates running on the user computers. Is it possible that by setting up the GPO to do the updates, it messed with the WSUS?

ASKER CERTIFIED SOLUTION

Don

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

matavai

ASKER

Thanks, that looks promising, and for the correct version of SBS too, always a bonus. All the services are running, but I do have a WSUS directory on my server, though its not what I'd call a subdirectory because its straight on the C:\ drive, so I haven't started on the fix instructions yet. At the start of that link, they're refering to the Home tab & the Security tab, any idea what function/report it is they're referring to?

Don

Very familiar with WSUS, not as much with SBS 2008.... Those just appear to be some of the symptoms. I would ignore and continue with the solution :^)

matavai

ASKER

I don't know how to close this thread without a solution. Its likely the technet article was the solution, but the instructions for resolving the problem were too daunting for my technical skills, so I decided instead to live with the error message. Thanks to dstewartjr for the assistance though & at least I understand a bit more about the error now.