WSUS 3 & 13042 Error
I just recently upgraded the WSUS system from version 2 to 3 on a Windows Server 2003 system (all updates/SPs applied). It seems to be working fine, with one exception: the event viewer is repeatedly receiving an error: Event Type: Error Event Source: Windows Server update Services Event Category: Clients Event ID: ...
I just recently upgraded the WSUS system from version 2 to 3 on a Windows Server 2003 system (all updates/SPs applied). It seems to be working fine, with one exception: the event viewer is repeatedly receiving an error:
Event Type: Error
Event Source: Windows Server update Services
Event Category: Clients
Event ID: 13042
Date: [every_day]
Time: [random_times]
User: N/A
Computer: [server_name]
Description:
Self-update is not working.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I've done some research, but I've already performed what was listed as remedies. I made sure that the Default Web and WSUS sites have annoymous login allowed for the SelfUpdate virtual directories via port 80 and to point to the correct directory, but no difference.
Again, WSUS seems to be working just fine, but I try incredibly hard to keep my event viewer free of errors.
Thanks in advance
Event Type: Error
Event Source: Windows Server update Services
Event Category: Clients
Event ID: 13042
Date: [every_day]
Time: [random_times]
User: N/A
Computer: [server_name]
Description:
Self-update is not working.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I've done some research, but I've already performed what was listed as remedies. I made sure that the Default Web and WSUS sites have annoymous login allowed for the SelfUpdate virtual directories via port 80 and to point to the correct directory, but no difference.
Again, WSUS seems to be working just fine, but I try incredibly hard to keep my event viewer free of errors.
Thanks in advance
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Have you looked at the selfupdate virtual directory in your Local website? We had a security (ssl) certificate installed for our company.. and that was our "problem" for this error message. I am now blessed with:
Event Type: Information
Event Source: Windows Server Update Services
Event Category: Clients
Event ID: 13040
Date: 28-3-2009
Time: 10:31:00
User: N/A
Computer: SERVERNAME
Description:
Self-update is working.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
What i did was at the properties tab of the virtual directory called "selfupdate", i went to directory security, then to edit and disabled the Require secure channel (SSL)!
Good luck, you could also review your IIS log (located by default in C:\WINDOWS\system32\LogFiles\W3SVC1) and your windowsupdate.log in C:\WINDOWS\
Event Type: Information
Event Source: Windows Server Update Services
Event Category: Clients
Event ID: 13040
Date: 28-3-2009
Time: 10:31:00
User: N/A
Computer: SERVERNAME
Description:
Self-update is working.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
What i did was at the properties tab of the virtual directory called "selfupdate", i went to directory security, then to edit and disabled the Require secure channel (SSL)!
Good luck, you could also review your IIS log (located by default in C:\WINDOWS\system32\LogFiles\W3SVC1) and your windowsupdate.log in C:\WINDOWS\
A lot of the "resolutions" (if you want to call them that) have metioned installing from scratch. As that was a bit of an issue before, I tried to avoid that.
I've moved the WSUS over to a completely different system and installed it from scratch. Unfortunately, I'm still getting the error. I've also tried a migration and still get the error. Again, everything works fine; just that pesky error that makes little to no sense, as the system works.
I'll be moving it again within the next month, so if I actually make any progress, I'll throw it in here.
Note: This is not a bump. Just up[censored] the situation.
I've moved the WSUS over to a completely different system and installed it from scratch. Unfortunately, I'm still getting the error. I've also tried a migration and still get the error. Again, everything works fine; just that pesky error that makes little to no sense, as the system works.
I'll be moving it again within the next month, so if I actually make any progress, I'll throw it in here.
Note: This is not a bump. Just up[censored] the situation.
Hi all,
I've been searching for this issue for 3 days !!
It drove me nuts.
Anyway I found a solution that works for me.
All settings looked fine to me :
- Anonymous access for SelfUpdate in Default Web Site
- UpdateServices running under Network account
- WSUS MMC working fine with abiltity to decline or accpet updates
wsusutil checkhealth only returning 13042.
Finally I created a virtual directory in WSUS admin website which is running on 8530 TCP port. I named this Virtual Directory.... SelfUpdate !!
I gave him anonymous access and NTFS full rights for Network Service account.
And Tadam !!! wsusutils checkhealth reports everything is fine !!
Looks like WSUS 3.0 upgrade from 2.0 does not do the job completely...
Hope this will help you.
Regards
PS : Excuse for my poor english, just a frenchy guy here ;-)
I've been searching for this issue for 3 days !!
It drove me nuts.
Anyway I found a solution that works for me.
All settings looked fine to me :
- Anonymous access for SelfUpdate in Default Web Site
- UpdateServices running under Network account
- WSUS MMC working fine with abiltity to decline or accpet updates
wsusutil checkhealth only returning 13042.
Finally I created a virtual directory in WSUS admin website which is running on 8530 TCP port. I named this Virtual Directory.... SelfUpdate !!
I gave him anonymous access and NTFS full rights for Network Service account.
And Tadam !!! wsusutils checkhealth reports everything is fine !!
Looks like WSUS 3.0 upgrade from 2.0 does not do the job completely...
Hope this will help you.
Regards
PS : Excuse for my poor english, just a frenchy guy here ;-)
