Event ID: 13042 - Self-update is not working in win2003 for WSUS 3

Hi All,

1) I done the clean installation of WSUS server 3.0 on windows server 2003
Standard edition with SP2. However I am getting Event IDs: 13042, 13031 for
solution, I followed the steps mention on
"http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=.NET+Framework&ProdVer=2.0 .50727&EvtID=13042&EvtSrc=Windows+Server+Update+Se rvices&LCID=1033"
& Done the IISRESET & restarted the "Service:wuauserv". Still I was facing
same issue.
2)I found that the permissions on the WSUS Administration (& Selfupdate
benith it) in IIS had been changed hence, I given "User: IUSR_A0374S01"
permission to Read & Execute, List Folder Contents and Read permissions. Deny
write permissions.
3) I given 'Everyone' windows group read only rights to "Folder: C:\program
files\update services\selfupdate".
4) Everything else was correctly configured as mention in the comments in
this discussion but still I am unable to get rid of this Event ID: 13042,
13031 please help me. I am using windows server 2003 standard edition.

Please help me.


Thanks in Advance

"A-S-I-F" <> wrote in message
news:E1E6A017-A1F8-4ED5-A691-...
> Hi All,
>
> 1) I done the clean installation of WSUS server 3.0 on windows server 2003
> Standard edition with SP2.

Can we clarify this... you did a clean installation of WSUS 3.... was this
on a CLEAN installation of Win2003SP2 and IIS6? If so, there should have
been no requirement to change any permissions anywhere.

> However I am getting Event IDs: 13042, 13031 for solution, I followed the
> steps mention on
> "http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=.NET+Framework&ProdVer=2.0 .50727&EvtID=13042&EvtSrc=Windows+Server+Update+Se rvices&LCID=1033"
> & Done the IISRESET & restarted the "Service:wuauserv". Still I was facing
> same issue.

It's not at all likely that the issue described in this article applied to
your Clean Install, assuming it was a Clean Install.

> 2)I found that the permissions on the WSUS Administration (& Selfupdate
> benith it) in IIS had been changed

Suggesting that perhaps the Win2003SP2/IIS6 installation was not *clean* --
although permissions being changed on the "WSUS Administration" virtual
server could only occur *after* WSUS was installed -- unless WSUS was
previously installed on this machine and not properly/fully uninstalled.

> hence, I given "User: IUSR_A0374S01"
> permission to Read & Execute, List Folder Contents and Read permissions.
> Deny
> write permissions.

Right here's where I would suggest taking the easy road out and uninstall
WSUS, uninstall IIS6, reboot the server, reinstall IIS6, and then reinstall
WSUS. This way you know for certain that IIS6 is properly configred in it's
default installation state.

> 3) I given 'Everyone' windows group read only rights to "Folder:
> C:\program
> files\update services\selfupdate".

Definitely not necessary.The correct permissions for this folder are Full
Control for the Administrators group and the SYSTEM account, and
Read&Execute/ListFolderContents/Read for the BUILTIN\Users group -- which,
btw, is exactly how it's documented in the article you've cited above.

Check permissions on the client Web service directory.
Open a command window.
Type cd <WSUSInstallDir>\SelfUpdate
Type cacls
The following ACEs should be set:
BUILTIN\UsersOI)(CI)R
BUILTIN\AdministratorsOI)(CI)F
NT AUTHORITY\SYSTEMOI)(CI)F

In general, all of the correct NTFS and IIS permissions are documented in
the WSUS Operations Guide.

Also, given that you referenced the above document for the EventID 13042 --
did you also reference this document and/or perform the provided steps for
the EventID 13031?

http://www.microsoft.com/technet/sup...ices&LCID=1033

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Hi Lawrence,

Thanks for ur reply.

1) I have done a clean installation of WSUS on clean installation of windows
2003 SP2 and IIS6.
2) It is a clean install, everthing is working well as all the client pc are
able to connect WSUS and load the update very well so I don't think I need to
reinstall IIS6 or WSUS as it is working. However, I don't know why this error
event id 13042, 13031 are coming up I just wanted to get rid of it. Could you
please suggest me something I can do on this server to resolve this issue
without reinstalling the ISS and WSUS.
3) I already did the permissions checking on the client Web service
directory from the steps mention in the link I provided in this comment.
Found everything to be ok.

Could you please suggest me something I can do on this server to resolve
this issue without reinstalling the ISS and WSUS.


Thanks

"A-S-I-F" <> wrote in message
news:27B06C96-C439-4A78-9828-...
> Hi Lawrence,
>
> Thanks for ur reply.
>
> 1) I have done a clean installation of WSUS on clean installation of
> windows
> 2003 SP2 and IIS6.

The presence of the error messages suggests otherwise. A clean installation
of WSUS on a clean installation of Window Server 2003 SP2 and a clean
installation of IIS6 does not produce error messages.

> 2) It is a clean install, everthing is working well as all the client pc
> are
> able to connect WSUS and load the update very well so I don't think I need
> to
> reinstall IIS6 or WSUS as it is working.

And yet.. you have unexplained error messages with no identified cause -- so
who knows what else is *not* working!

> However, I don't know why this error event id 13042, 13031 are coming up

They're coming up because you have something misconfigured in your
installation.

EventID 13031: Client computers are not reporting status to the WSUS server.
EventID 13042: Self-update is not working.


> I just wanted to get rid of it.

Well, you can't just "get rid of it". You have to identify the cause and FIX
the problem.


> Could you
> please suggest me something I can do on this server to resolve this issue
> without reinstalling the ISS and WSUS.

I'm trying. A bit less resistance to suggestion and a bit more information
would probably be helpful. I've already offered two suggestions. You've
outright refused one, with no real reason except personal inconvenience, and
you've not even commented on the results of the other -- suggesting to me
that you've completely ignored the suggestion.


> 3) I already did the permissions checking on the client Web service
> directory from the steps mention in the link I provided in this comment.

Great, that's about 2% of the things you need to check. Now you need to
finish by checking (and correcting) *ALL* of the permissions for IIS and the
filesystem.

In your previous post, you admitted to resetting permissions to an invalid
value:

>> 3) I given 'Everyone' windows group read only rights to "Folder:
>> C:\program files\update services\selfupdate".

So at least one permission setting is still incorrect.

My suggestion to you (again) is to get the WSUS Operations Guide and verify
every single NTFS and IIS permissions setting that is documented in that
guide.

Of course, I'll also say this again: A *CLEAN* installation of Windows
Server 2003 and IIS6 will already have all of those permissions set by
default, so the only way they could be wrong (like having "Everyone"
permissions on the selfupdate folder) is if they've been changed after the
installation. If *nothing* has been changed, then you wouldn't be getting
these errors!


> Found everything to be ok.

And yet, it's not.


> Could you please suggest me something I can do on this server to resolve
> this issue without reinstalling the ISS and WSUS.

Beyond what I've already suggested... no. You've not provided enough
information to offer any more suggestions.

So far there are only two options on the table.

1. Check *every* permission and verify it with the WSUS Operations Guide

=or=

2. Uninstall WSUS; Uninstall IIS; Reboot; Reinstall IIS; Reinstall WSUS --
and do NOT change anything.

If you have more information about things you've done to this server that
you've not yet shared (like whatever you changed after the installation that
is causing a standard installation of WSUS on a "clean" installation of
Win2003/IIS6 to not work; or other things you've installed that would make
this a "not clean" installation of Win2003/IIS6), now would be a good time.



--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin