After SP!, Windows Server Update 13042 Self-update is not working

My WSUS was running correctly on my SBS2K3 R2 server until I installed the
SP1. Since then I am getting the Windows Server Update Event 13042 in the
Server Application log, and all but one of my workstations is not reporting
to the server. For some odd reason, one XP Workstation seems to be reporting,
but the remainder of the XP and Vista machines have not reported to the
server since the day I installed SP1. If I try to manually check for updates
from one of the vista machines, I get error code 80244019. I use GP for the
update settings to the workstations. Any help appreciated, as I want to begin
rolling out the SP1 to customer sites, but obviously want it to work on mine
first. I have done the requisite Google and MS Support searches but nothing
seems to be quite what I have here.
--
Philip Mollica
President
ZDT Networks LLC

I solved my problem. I had some other similar servers to look at. Their was a
SelfUpdate Virtual Directory under the Default Website, but there was not one
under the WSUS Administration Website. I manually created that Virtual
Directory, then everything started working again. Did I do something during
the installation of the SP1 that caused that to happen?
--
Philip Mollica
President
ZDT Networks LLC


"Philip Mollica" wrote:

> My WSUS was running correctly on my SBS2K3 R2 server until I installed the
> SP1. Since then I am getting the Windows Server Update Event 13042 in the
> Server Application log, and all but one of my workstations is not reporting
> to the server. For some odd reason, one XP Workstation seems to be reporting,
> but the remainder of the XP and Vista machines have not reported to the
> server since the day I installed SP1. If I try to manually check for updates
> from one of the vista machines, I get error code 80244019. I use GP for the
> update settings to the workstations. Any help appreciated, as I want to begin
> rolling out the SP1 to customer sites, but obviously want it to work on mine
> first. I have done the requisite Google and MS Support searches but nothing
> seems to be quite what I have here.
> --
> Philip Mollica
> President
> ZDT Networks LLC

"Philip Mollica" <PhilipMollica@discussions.microsoft.com> wrote in message
news:E1119A66-C946-49C2-9D1C-DB5C39F5370E@microsoft.com...

>> My WSUS was running correctly on my SBS2K3 R2 server until I installed
>> the
>> SP1. Since then I am getting the Windows Server Update Event 13042 in the
>> Server Application log, and all but one of my workstations is not
>> reporting
>> to the server. For some odd reason, one XP Workstation seems to be
>> reporting,
>> but the remainder of the XP and Vista machines have not reported to the
>> server since the day I installed SP1. If I try to manually check for
>> updates
>> from one of the vista machines, I get error code 80244019. I use GP for
>> the
>> update settings to the workstations. Any help appreciated, as I want to
>> begin
>> rolling out the SP1 to customer sites, but obviously want it to work on
>> mine
>> first. I have done the requisite Google and MS Support searches but
>> nothing
>> seems to be quite what I have here.


>I solved my problem. I had some other similar servers to look at. Their was
>a
> SelfUpdate Virtual Directory under the Default Website, but there was not
> one
> under the WSUS Administration Website. I manually created that Virtual
> Directory, then everything started working again. Did I do something
> during
> the installation of the SP1 that caused that to happen?
> --
> Philip Mollica
> President
> ZDT Networks LLC

Philip, I'm not aware of any known issues with the SP1 installation removing
virtual directories.

--
Lawrence Garvin, M.S., MCBMSP, MCTS, MCP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)

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

> Philip, I'm not aware of any known issues with the SP1 installation removing
> virtual directories.
>
> --
> Lawrence Garvin, M.S., MCBMSP, MCTS, MCP
> Senior Data Architect, APQC, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2008)
>
> MS WSUS Website:http://www.microsoft.com/wsus
> My Websites:http://www.onsitechsolutions.com;htt...hsolutions.com
> My MVP Profile:http://mvp.support.microsoft.com/pro...wrence.Garvin- Hide quoted text -
>
> - Show quoted text -

Lawrence,

I would just like to confirm that I experienced that same (or similar)
problem in my environment. I have WSUS running on port 8530, and
another website running on port 80 (Symantec Endpoint Protection
Manager).

After upgrading WSUS 3.0 to SP1, the Selfupdate Virtual Directory was
there on the website on Port 80, but not on the WSUS website on 8530.

It took me an awfully long time to figure out that it needed to exist
in both places, because all of the troubleshooting topics and message
board posts that I came across only said to make sure that it exists
on the site on Port 80 if WSUS is installed on 8530.

---
Colin Edwards
Systems Administrator

On Apr 2, 1:35*pm, Colin.P.Edwa...@gmail.com wrote:
> > Philip, I'm not aware of any known issues with the SP1 installation removing
> > virtual directories.
>
> > --
> > Lawrence Garvin, M.S., MCBMSP, MCTS, MCP
> > Senior Data Architect, APQC, Houston, Texas
> > Microsoft MVP - Software Distribution (2005-2008)
>
> > MS WSUS Website:http://www.microsoft.com/wsus
> > My Websites:http://www.onsitechsolutions.com;htt...hsolutions.com
> > My MVP Profile:http://mvp.support.microsoft.com/pro...ce.Garvin-Hide quoted text -
>
> > - Show quoted text -
>
> Lawrence,
>
> I would just like to confirm that I experienced that same (or similar)
> problem in my environment. *I have WSUS running on port 8530, and
> another website running on port 80 (Symantec Endpoint Protection
> Manager).
>
> After upgrading WSUS 3.0 to SP1, the Selfupdate Virtual Directory was
> there on the website on Port 80, but not on the WSUS website on 8530.
>
> It took me an awfully long time to figure out that it needed to exist
> in both places, because all of the troubleshooting topics and message
> board posts that I came across only said to make sure that it exists
> on the site on Port 80 if WSUS is installed on 8530.
>
> ---
> Colin Edwards
> Systems Administrator

For what it is worth, I was seeing the exact same problem, and the
exact same fixed the issue. There is likely something wrong with the
SP1 installer...

I had the exact same issue, and by making the "virtual directory" resolved
it...
Al

"Jerry" <jerrice@gmail.com> wrote in message
news:5f47287d-4e77-49ae-8ad6-9413eb92cdaf@q24g2000prf.googlegroups.com...
On Apr 2, 1:35 pm, Colin.P.Edwa...@gmail.com wrote:
> > Philip, I'm not aware of any known issues with the SP1 installation
> > removing
> > virtual directories.
>
> > --
> > Lawrence Garvin, M.S., MCBMSP, MCTS, MCP
> > Senior Data Architect, APQC, Houston, Texas
> > Microsoft MVP - Software Distribution (2005-2008)
>
> > MS WSUS Website:http://www.microsoft.com/wsus
> > My
> > Websites:http://www.onsitechsolutions.com;htt...hsolutions.com
> > My MVP
> > Profile:http://mvp.support.microsoft.com/pro...ce.Garvin-Hide
> > quoted text -
>
> > - Show quoted text -
>
> Lawrence,
>
> I would just like to confirm that I experienced that same (or similar)
> problem in my environment. I have WSUS running on port 8530, and
> another website running on port 80 (Symantec Endpoint Protection
> Manager).
>
> After upgrading WSUS 3.0 to SP1, the Selfupdate Virtual Directory was
> there on the website on Port 80, but not on the WSUS website on 8530.
>
> It took me an awfully long time to figure out that it needed to exist
> in both places, because all of the troubleshooting topics and message
> board posts that I came across only said to make sure that it exists
> on the site on Port 80 if WSUS is installed on 8530.
>
> ---
> Colin Edwards
> Systems Administrator

For what it is worth, I was seeing the exact same problem, and the
exact same fixed the issue. There is likely something wrong with the
SP1 installer...

[DavidRa]

I can confirm that this has also occurred on a clean installation of WSUS 3.0SP1 on Windows 2003 R2 Std. The only other software on the host is ISA server.

I had to:
* Run the "InstallSelfUpdateOnPort80.vbs" script;
* Export the configuration of the SelfUpdate tree from the default website;
* Import the saved configuration to the SelfUpdate tree on the WSUS website.

Definitely an installer problem.

"DavidRa" <DavidRa.398wne@DoNotSpam.com> wrote in message
news:DavidRa.398wne@DoNotSpam.com...

> I can confirm that this has also occurred on a clean installation of
> WSUS 3.0SP1 on Windows 2003 R2 Std. The only other software on the host
> is ISA server.
>
> I had to:
> * Run the "InstallSelfUpdateOnPort80.vbs" script;
> * Export the configuration of the SelfUpdate tree from the default
> website;
> * Import the saved configuration to the SelfUpdate tree on the WSUS
> website.
>
> Definitely an installer problem.

For what it's worth... a simpler 'repair' is:

1. Create a virtual directory named 'selfupdate'.
2. Set the path to %programfiles%\Update Services\selfupdate
3. Enable anonymous access on the ~/selfupdate virtual directory.


Which is pretty much what the vbs script does. :-)


--
Lawrence Garvin, M.S., MCITP, MCBMSP, MCTS(x4), MCP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)

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

I had WSUS 3 SP1 running fine on port 80. Installed Symanted Endpoint
Manager with the configuration to share a website and it broke WSUS
completely.

Uninstalled WSUS and reinstalled on port 8530. When I did this there was no
SelfUpdate site anywhere.

I ran C:\Program Files\Update Services\Setup\InstallSelfUpdateOnPort80.vbs
Exported the Self Update virtual directory config in the default website to
a file
Imported the config on the WSUS Admin website (port 8530)

Working great now! Thanks DavidRa


All information posted is AS-IS with no implicit or explicit warranty. Make
system changes at your own risk!

"genemcsween" <genemcsween@discussions.microsoft.com> wrote in message
news:0691F4E9-7947-4240-9E5A-86BC0ACC41D1@microsoft.com...
>I had WSUS 3 SP1 running fine on port 80. Installed Symanted Endpoint
> Manager with the configuration to share a website and it broke WSUS
> completely.

Known issue... for about six months now... discussed here at least once a
month.


> Uninstalled WSUS and reinstalled on port 8530. When I did this there was
> no
> SelfUpdate site anywhere.

Known issue... the WSUS SP1 installer has a 'bug' and fails to properly
create the /selfupdate virtual directory.


> I ran C:\Program Files\Update Services\Setup\InstallSelfUpdateOnPort80.vbs
> Exported the Self Update virtual directory config in the default website
> to
> a file Imported the config on the WSUS Admin website (port 8530)
>
> Working great now! Thanks DavidRa

That's one way to do it.

Manually creating the vdir and enabling anonymous access also works.



--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)

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