Discussion:
One or more Update Service components could not be contacted.
(too old to reply)
Scott Davis
2005-06-09 12:46:04 UTC
Permalink
One or more Update Service components could not be contacted. Check your
server status and ensure that the Windows Server Update Service is running.
Non-running services: SelfUpdate

This error is in my To Do List with a red X. All clients seem to be updating
and reporting. Any ideas?
--
Scott Davis
Joe Gettys [MSFT]
2005-06-09 16:29:40 UTC
Permalink
This advises you that the selfupdate virtual directory can not be contacted
over port 80.

If you have the WSUS site on port 80, make sure the virtual directory
exists.

If it's on another port, make sure the default site on port 80 is running
and that the virtual directory exists

Thanks,

Joe Gettys [MSFT]


This posting is provided "AS IS" with no warranties, and confers no rights.
Post by Scott Davis
One or more Update Service components could not be contacted. Check your
server status and ensure that the Windows Server Update Service is running.
Non-running services: SelfUpdate
This error is in my To Do List with a red X. All clients seem to be updating
and reporting. Any ideas?
--
Scott Davis
Lawrence Garvin
2005-06-09 16:34:20 UTC
Permalink
Joe, since Scott indicates that all of his clients "seem to be updating and
reporting", my guess is that he previously had the beta/RC running, so none
of his clients have a downlevel WUA, and thus don't need the port 80
service.

This would effectively make this error message insignificant (for the
moment), correct?
Until an installation of a new system necessitates a selfupdate from port
80. :-)

What's the word on an MSI, or documentation, for slipstreaming the WUA into
install images so that reliance on the port-80 selfupdate tree can be
removed.
Post by Joe Gettys [MSFT]
This advises you that the selfupdate virtual directory can not be
contacted over port 80.
If you have the WSUS site on port 80, make sure the virtual directory
exists.
If it's on another port, make sure the default site on port 80 is running
and that the virtual directory exists
Thanks,
Joe Gettys [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by Scott Davis
One or more Update Service components could not be contacted. Check your
server status and ensure that the Windows Server Update Service is running.
Non-running services: SelfUpdate
This error is in my To Do List with a red X. All clients seem to be updating
and reporting. Any ideas?
--
Scott Davis
Jason
2005-06-09 18:15:36 UTC
Permalink
I am getting this message to. My WSUS site is set to use port 80 and there
is a virtual directory called Selfupdate in IIS Manger. Do you have any
other ideas?

Thanks,

Jason
Post by Joe Gettys [MSFT]
This advises you that the selfupdate virtual directory can not be
contacted over port 80.
If you have the WSUS site on port 80, make sure the virtual directory
exists.
If it's on another port, make sure the default site on port 80 is running
and that the virtual directory exists
Thanks,
Joe Gettys [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by Scott Davis
One or more Update Service components could not be contacted. Check your
server status and ensure that the Windows Server Update Service is running.
Non-running services: SelfUpdate
This error is in my To Do List with a red X. All clients seem to be updating
and reporting. Any ideas?
--
Scott Davis
Lawrence Garvin
2005-06-09 20:59:01 UTC
Permalink
I believe if the 'selfupdate' virtual directory is lacking anonymous access
permissions, you will also get the error message.
Post by Jason
I am getting this message to. My WSUS site is set to use port 80 and there
is a virtual directory called Selfupdate in IIS Manger. Do you have any
other ideas?
Thanks,
Jason
Post by Joe Gettys [MSFT]
This advises you that the selfupdate virtual directory can not be
contacted over port 80.
If you have the WSUS site on port 80, make sure the virtual directory
exists.
If it's on another port, make sure the default site on port 80 is running
and that the virtual directory exists
Thanks,
Joe Gettys [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by Scott Davis
One or more Update Service components could not be contacted. Check your
server status and ensure that the Windows Server Update Service is running.
Non-running services: SelfUpdate
This error is in my To Do List with a red X. All clients seem to be updating
and reporting. Any ideas?
--
Scott Davis
Jason
2005-06-09 22:41:19 UTC
Permalink
Under directory security, the allow Enable anonymous access checkbox is
checked and so is integrated windows authenication.

Thanks,
Jason
Post by Lawrence Garvin
I believe if the 'selfupdate' virtual directory is lacking anonymous access
permissions, you will also get the error message.
Post by Jason
I am getting this message to. My WSUS site is set to use port 80 and
there is a virtual directory called Selfupdate in IIS Manger. Do you have
any other ideas?
Thanks,
Jason
Post by Joe Gettys [MSFT]
This advises you that the selfupdate virtual directory can not be
contacted over port 80.
If you have the WSUS site on port 80, make sure the virtual directory
exists.
If it's on another port, make sure the default site on port 80 is
running and that the virtual directory exists
Thanks,
Joe Gettys [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by Scott Davis
One or more Update Service components could not be contacted. Check your
server status and ensure that the Windows Server Update Service is running.
Non-running services: SelfUpdate
This error is in my To Do List with a red X. All clients seem to be updating
and reporting. Any ideas?
--
Scott Davis
Lawrence Garvin
2005-06-10 03:52:51 UTC
Permalink
Well, shucks...

back to Joe. :-)
Post by Jason
Under directory security, the allow Enable anonymous access checkbox is
checked and so is integrated windows authenication.
Thanks,
Jason
Post by Lawrence Garvin
I believe if the 'selfupdate' virtual directory is lacking anonymous
access permissions, you will also get the error message.
Post by Jason
I am getting this message to. My WSUS site is set to use port 80 and
there is a virtual directory called Selfupdate in IIS Manger. Do you
have any other ideas?
Thanks,
Jason
Post by Joe Gettys [MSFT]
This advises you that the selfupdate virtual directory can not be
contacted over port 80.
If you have the WSUS site on port 80, make sure the virtual directory
exists.
If it's on another port, make sure the default site on port 80 is
running and that the virtual directory exists
Thanks,
Joe Gettys [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by Scott Davis
One or more Update Service components could not be contacted. Check your
server status and ensure that the Windows Server Update Service is running.
Non-running services: SelfUpdate
This error is in my To Do List with a red X. All clients seem to be updating
and reporting. Any ideas?
--
Scott Davis
Don Cottam [MS]
2005-06-10 17:14:00 UTC
Permalink
Jason, can you zip and send the %program files%\update
services\logfiles\softwaredistribution.log file please?
--
Don Cottam
Microsoft Corporation
Windows Server Update Services

donco AT microsoft DOT com
(I prefer to communicate through the newsgroup, so please do not email me
unless necessary...but if necessary, don't hesitate to email me. Thx!)

=====================
This posting is provided "AS IS" with no warranties, and confers no rights.
=====================
Post by Lawrence Garvin
Well, shucks...
back to Joe. :-)
Post by Jason
Under directory security, the allow Enable anonymous access checkbox is
checked and so is integrated windows authenication.
Thanks,
Jason
Post by Lawrence Garvin
I believe if the 'selfupdate' virtual directory is lacking anonymous
access permissions, you will also get the error message.
Post by Jason
I am getting this message to. My WSUS site is set to use port 80 and
there is a virtual directory called Selfupdate in IIS Manger. Do you
have any other ideas?
Thanks,
Jason
Post by Joe Gettys [MSFT]
This advises you that the selfupdate virtual directory can not be
contacted over port 80.
If you have the WSUS site on port 80, make sure the virtual directory
exists.
If it's on another port, make sure the default site on port 80 is
running and that the virtual directory exists
Thanks,
Joe Gettys [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by Scott Davis
One or more Update Service components could not be contacted. Check your
server status and ensure that the Windows Server Update Service is running.
Non-running services: SelfUpdate
This error is in my To Do List with a red X. All clients seem to be updating
and reporting. Any ideas?
--
Scott Davis
Martin Samuelsson
2005-06-13 09:35:01 UTC
Permalink
Hi

I have exactly the same symptoms and have done the same checks as Scott.

I can send my log file if it's of any help. How do you want me to send it?

/Martin
Post by Don Cottam [MS]
Jason, can you zip and send the %program files%\update
services\logfiles\softwaredistribution.log file please?
--
Don Cottam
Microsoft Corporation
Windows Server Update Services
donco AT microsoft DOT com
(I prefer to communicate through the newsgroup, so please do not email me
unless necessary...but if necessary, don't hesitate to email me. Thx!)
=====================
This posting is provided "AS IS" with no warranties, and confers no rights.
=====================
Post by Lawrence Garvin
Well, shucks...
back to Joe. :-)
Post by Jason
Under directory security, the allow Enable anonymous access checkbox is
checked and so is integrated windows authenication.
Thanks,
Jason
Post by Lawrence Garvin
I believe if the 'selfupdate' virtual directory is lacking anonymous
access permissions, you will also get the error message.
Post by Jason
I am getting this message to. My WSUS site is set to use port 80 and
there is a virtual directory called Selfupdate in IIS Manger. Do you
have any other ideas?
Thanks,
Jason
Post by Joe Gettys [MSFT]
This advises you that the selfupdate virtual directory can not be
contacted over port 80.
If you have the WSUS site on port 80, make sure the virtual directory
exists.
If it's on another port, make sure the default site on port 80 is
running and that the virtual directory exists
Thanks,
Joe Gettys [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by Scott Davis
One or more Update Service components could not be contacted. Check your
server status and ensure that the Windows Server Update Service is running.
Non-running services: SelfUpdate
This error is in my To Do List with a red X. All clients seem to be updating
and reporting. Any ideas?
--
Scott Davis
Ken Renouf
2005-06-13 11:36:01 UTC
Permalink
Yep, I've got the same issues too. I originally had the issue running the RC
on my corporate network, but when the full release came out, I tried that,
but still have the same issue. I've tried to run it on another
server/network just to eliminate this customer's server/network lockdown
policies but I also have the same symptoms elsewhere on a clean install.

Restarting the "Update Services" service temporarily removes the message but
it does come back at varying intervals from a couple of seconds to a few
minutes.

I'll email my log file to Don.

Cheers,

Ken Renouf.
Post by Martin Samuelsson
Hi
I have exactly the same symptoms and have done the same checks as Scott.
I can send my log file if it's of any help. How do you want me to send it?
/Martin
Post by Don Cottam [MS]
Jason, can you zip and send the %program files%\update
services\logfiles\softwaredistribution.log file please?
--
Don Cottam
Microsoft Corporation
Windows Server Update Services
donco AT microsoft DOT com
(I prefer to communicate through the newsgroup, so please do not email me
unless necessary...but if necessary, don't hesitate to email me. Thx!)
=====================
This posting is provided "AS IS" with no warranties, and confers no rights.
=====================
Post by Lawrence Garvin
Well, shucks...
back to Joe. :-)
Post by Jason
Under directory security, the allow Enable anonymous access checkbox is
checked and so is integrated windows authenication.
Thanks,
Jason
Post by Lawrence Garvin
I believe if the 'selfupdate' virtual directory is lacking anonymous
access permissions, you will also get the error message.
Post by Jason
I am getting this message to. My WSUS site is set to use port 80 and
there is a virtual directory called Selfupdate in IIS Manger. Do you
have any other ideas?
Thanks,
Jason
Post by Joe Gettys [MSFT]
This advises you that the selfupdate virtual directory can not be
contacted over port 80.
If you have the WSUS site on port 80, make sure the virtual directory
exists.
If it's on another port, make sure the default site on port 80 is
running and that the virtual directory exists
Thanks,
Joe Gettys [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by Scott Davis
One or more Update Service components could not be contacted. Check your
server status and ensure that the Windows Server Update Service is
running.
Non-running services: SelfUpdate
This error is in my To Do List with a red X. All clients seem to be
updating
and reporting. Any ideas?
--
Scott Davis
Darren Sell
2005-06-14 15:15:01 UTC
Permalink
I had this problem as well. I added "127.0.0.1" to my trusted sites on the
IE security tab of my server and it now works. As far as I can tell, even
though "localhost" is in the trusted sites, WSUS attempts to check if the
self update service is running by going to "http://127.0.0.1/selfupdate"
instead of "http://localhost/selfupdate".

It sort of makes sense that it couldn't get through because since 127.0.0.1
was not a trusted site, it would need credentials. (Try going there through
your browser on your server, you'll see what I mean). But when you add
127.0.0.1 to the trusted site, it does not get hung up asking for
credentials. Of course, that should be taken care of in other places, but I
digress....

Darren
Post by Ken Renouf
Yep, I've got the same issues too. I originally had the issue running the RC
on my corporate network, but when the full release came out, I tried that,
but still have the same issue. I've tried to run it on another
server/network just to eliminate this customer's server/network lockdown
policies but I also have the same symptoms elsewhere on a clean install.
Restarting the "Update Services" service temporarily removes the message but
it does come back at varying intervals from a couple of seconds to a few
minutes.
I'll email my log file to Don.
Cheers,
Ken Renouf.
Post by Martin Samuelsson
Hi
I have exactly the same symptoms and have done the same checks as Scott.
I can send my log file if it's of any help. How do you want me to send it?
/Martin
Post by Don Cottam [MS]
Jason, can you zip and send the %program files%\update
services\logfiles\softwaredistribution.log file please?
--
Don Cottam
Microsoft Corporation
Windows Server Update Services
donco AT microsoft DOT com
(I prefer to communicate through the newsgroup, so please do not email me
unless necessary...but if necessary, don't hesitate to email me. Thx!)
=====================
This posting is provided "AS IS" with no warranties, and confers no rights.
=====================
Post by Lawrence Garvin
Well, shucks...
back to Joe. :-)
Post by Jason
Under directory security, the allow Enable anonymous access checkbox is
checked and so is integrated windows authenication.
Thanks,
Jason
Post by Lawrence Garvin
I believe if the 'selfupdate' virtual directory is lacking anonymous
access permissions, you will also get the error message.
Post by Jason
I am getting this message to. My WSUS site is set to use port 80 and
there is a virtual directory called Selfupdate in IIS Manger. Do you
have any other ideas?
Thanks,
Jason
Post by Joe Gettys [MSFT]
This advises you that the selfupdate virtual directory can not be
contacted over port 80.
If you have the WSUS site on port 80, make sure the virtual directory
exists.
If it's on another port, make sure the default site on port 80 is
running and that the virtual directory exists
Thanks,
Joe Gettys [MSFT]
This posting is provided "AS IS" with no warranties, and confers no
rights.
Post by Scott Davis
One or more Update Service components could not be contacted. Check
your
server status and ensure that the Windows Server Update Service is
running.
Non-running services: SelfUpdate
This error is in my To Do List with a red X. All clients seem to be
updating
and reporting. Any ideas?
--
Scott Davis
Darren Sell
2005-06-14 15:42:02 UTC
Permalink
Never mind, it only worked for a little bit. Guess it's something else.
Post by Darren Sell
I had this problem as well. I added "127.0.0.1" to my trusted sites on the
IE security tab of my server and it now works. As far as I can tell, even
though "localhost" is in the trusted sites, WSUS attempts to check if the
self update service is running by going to "http://127.0.0.1/selfupdate"
instead of "http://localhost/selfupdate".
It sort of makes sense that it couldn't get through because since 127.0.0.1
was not a trusted site, it would need credentials. (Try going there through
your browser on your server, you'll see what I mean). But when you add
127.0.0.1 to the trusted site, it does not get hung up asking for
credentials. Of course, that should be taken care of in other places, but I
digress....
Darren
Post by Ken Renouf
Yep, I've got the same issues too. I originally had the issue running the RC
on my corporate network, but when the full release came out, I tried that,
but still have the same issue. I've tried to run it on another
server/network just to eliminate this customer's server/network lockdown
policies but I also have the same symptoms elsewhere on a clean install.
Restarting the "Update Services" service temporarily removes the message but
it does come back at varying intervals from a couple of seconds to a few
minutes.
I'll email my log file to Don.
Cheers,
Ken Renouf.
Post by Martin Samuelsson
Hi
I have exactly the same symptoms and have done the same checks as Scott.
I can send my log file if it's of any help. How do you want me to send it?
/Martin
Post by Don Cottam [MS]
Jason, can you zip and send the %program files%\update
services\logfiles\softwaredistribution.log file please?
--
Don Cottam
Microsoft Corporation
Windows Server Update Services
donco AT microsoft DOT com
(I prefer to communicate through the newsgroup, so please do not email me
unless necessary...but if necessary, don't hesitate to email me. Thx!)
=====================
This posting is provided "AS IS" with no warranties, and confers no rights.
=====================
Post by Lawrence Garvin
Well, shucks...
back to Joe. :-)
Post by Jason
Under directory security, the allow Enable anonymous access checkbox is
checked and so is integrated windows authenication.
Thanks,
Jason
Post by Lawrence Garvin
I believe if the 'selfupdate' virtual directory is lacking anonymous
access permissions, you will also get the error message.
Post by Jason
I am getting this message to. My WSUS site is set to use port 80 and
there is a virtual directory called Selfupdate in IIS Manger. Do you
have any other ideas?
Thanks,
Jason
Post by Joe Gettys [MSFT]
This advises you that the selfupdate virtual directory can not be
contacted over port 80.
If you have the WSUS site on port 80, make sure the virtual directory
exists.
If it's on another port, make sure the default site on port 80 is
running and that the virtual directory exists
Thanks,
Joe Gettys [MSFT]
This posting is provided "AS IS" with no warranties, and confers no
rights.
Post by Scott Davis
One or more Update Service components could not be contacted. Check
your
server status and ensure that the Windows Server Update Service is
running.
Non-running services: SelfUpdate
This error is in my To Do List with a red X. All clients seem to be
updating
and reporting. Any ideas?
--
Scott Davis
Jason
2005-06-14 16:01:07 UTC
Permalink
How would you like me to send it to you? I tried to post it, but the
attachment is too large.

Thanks,
Jason
Post by Don Cottam [MS]
Jason, can you zip and send the %program files%\update
services\logfiles\softwaredistribution.log file please?
--
Don Cottam
Microsoft Corporation
Windows Server Update Services
donco AT microsoft DOT com
(I prefer to communicate through the newsgroup, so please do not email me
unless necessary...but if necessary, don't hesitate to email me. Thx!)
=====================
This posting is provided "AS IS" with no warranties, and confers no rights.
=====================
Post by Lawrence Garvin
Well, shucks...
back to Joe. :-)
Post by Jason
Under directory security, the allow Enable anonymous access checkbox is
checked and so is integrated windows authenication.
Thanks,
Jason
Post by Lawrence Garvin
I believe if the 'selfupdate' virtual directory is lacking anonymous
access permissions, you will also get the error message.
Post by Jason
I am getting this message to. My WSUS site is set to use port 80 and
there is a virtual directory called Selfupdate in IIS Manger. Do you
have any other ideas?
Thanks,
Jason
Post by Joe Gettys [MSFT]
This advises you that the selfupdate virtual directory can not be
contacted over port 80.
If you have the WSUS site on port 80, make sure the virtual directory
exists.
If it's on another port, make sure the default site on port 80 is
running and that the virtual directory exists
Thanks,
Joe Gettys [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by Scott Davis
One or more Update Service components could not be contacted. Check your
server status and ensure that the Windows Server Update Service is running.
Non-running services: SelfUpdate
This error is in my To Do List with a red X. All clients seem to be updating
and reporting. Any ideas?
--
Scott Davis
Don Cottam [MS]
2005-06-15 07:31:27 UTC
Permalink
My email address is in my sig. Martin, Ken and Darren - send yours as well.
I assume all of your are running into issues with the error? What is the
specific error you are seeing? Also, when you send me email also include
this thread or otherwise remind me why you're sending me your log(s).
--
Don Cottam
Microsoft Corporation
Windows Server Update Services

donco AT microsoft DOT com
(I prefer to communicate through the newsgroup, so please do not email me
unless necessary...but if necessary, don't hesitate to email me. Thx!)

=====================
This posting is provided "AS IS" with no warranties, and confers no rights.
=====================
Post by Jason
How would you like me to send it to you? I tried to post it, but the
attachment is too large.
Thanks,
Jason
Post by Don Cottam [MS]
Jason, can you zip and send the %program files%\update
services\logfiles\softwaredistribution.log file please?
--
Don Cottam
Microsoft Corporation
Windows Server Update Services
donco AT microsoft DOT com
(I prefer to communicate through the newsgroup, so please do not email me
unless necessary...but if necessary, don't hesitate to email me. Thx!)
=====================
This posting is provided "AS IS" with no warranties, and confers no rights.
=====================
Post by Lawrence Garvin
Well, shucks...
back to Joe. :-)
Post by Jason
Under directory security, the allow Enable anonymous access checkbox is
checked and so is integrated windows authenication.
Thanks,
Jason
Post by Lawrence Garvin
I believe if the 'selfupdate' virtual directory is lacking anonymous
access permissions, you will also get the error message.
Post by Jason
I am getting this message to. My WSUS site is set to use port 80 and
there is a virtual directory called Selfupdate in IIS Manger. Do you
have any other ideas?
Thanks,
Jason
Post by Joe Gettys [MSFT]
This advises you that the selfupdate virtual directory can not be
contacted over port 80.
If you have the WSUS site on port 80, make sure the virtual
directory exists.
If it's on another port, make sure the default site on port 80 is
running and that the virtual directory exists
Thanks,
Joe Gettys [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by Scott Davis
One or more Update Service components could not be contacted. Check your
server status and ensure that the Windows Server Update Service is running.
Non-running services: SelfUpdate
This error is in my To Do List with a red X. All clients seem to be updating
and reporting. Any ideas?
--
Scott Davis
BigDave
2005-06-24 14:34:02 UTC
Permalink
We are also having the problem after upgrading from WSUS RC. I tried
uninstalling WSUS & MSDE and reinstalling and the problem has returned.
Post by Don Cottam [MS]
My email address is in my sig. Martin, Ken and Darren - send yours as well.
I assume all of your are running into issues with the error? What is the
specific error you are seeing? Also, when you send me email also include
this thread or otherwise remind me why you're sending me your log(s).
--
Don Cottam
Microsoft Corporation
Windows Server Update Services
donco AT microsoft DOT com
(I prefer to communicate through the newsgroup, so please do not email me
unless necessary...but if necessary, don't hesitate to email me. Thx!)
=====================
This posting is provided "AS IS" with no warranties, and confers no rights.
=====================
Post by Jason
How would you like me to send it to you? I tried to post it, but the
attachment is too large.
Thanks,
Jason
Post by Don Cottam [MS]
Jason, can you zip and send the %program files%\update
services\logfiles\softwaredistribution.log file please?
--
Don Cottam
Microsoft Corporation
Windows Server Update Services
donco AT microsoft DOT com
(I prefer to communicate through the newsgroup, so please do not email me
unless necessary...but if necessary, don't hesitate to email me. Thx!)
=====================
This posting is provided "AS IS" with no warranties, and confers no rights.
=====================
Post by Lawrence Garvin
Well, shucks...
back to Joe. :-)
Post by Jason
Under directory security, the allow Enable anonymous access checkbox is
checked and so is integrated windows authenication.
Thanks,
Jason
Post by Lawrence Garvin
I believe if the 'selfupdate' virtual directory is lacking anonymous
access permissions, you will also get the error message.
Post by Jason
I am getting this message to. My WSUS site is set to use port 80 and
there is a virtual directory called Selfupdate in IIS Manger. Do you
have any other ideas?
Thanks,
Jason
Post by Joe Gettys [MSFT]
This advises you that the selfupdate virtual directory can not be
contacted over port 80.
If you have the WSUS site on port 80, make sure the virtual
directory exists.
If it's on another port, make sure the default site on port 80 is
running and that the virtual directory exists
Thanks,
Joe Gettys [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by Scott Davis
One or more Update Service components could not be contacted. Check your
server status and ensure that the Windows Server Update Service is
running.
Non-running services: SelfUpdate
This error is in my To Do List with a red X. All clients seem to be
updating
and reporting. Any ideas?
--
Scott Davis
Brian
2005-06-15 17:12:06 UTC
Permalink
I had the same problem and I just found my builtin group in Active directory
Users did not have any members in it. I added the domain users to the Users
group and the error was no longer there.

See if that helps

P.S. My installation is on a W2k DC
Post by Jason
Under directory security, the allow Enable anonymous access checkbox is
checked and so is integrated windows authenication.
Thanks,
Jason
Post by Lawrence Garvin
I believe if the 'selfupdate' virtual directory is lacking anonymous access
permissions, you will also get the error message.
Post by Jason
I am getting this message to. My WSUS site is set to use port 80 and
there is a virtual directory called Selfupdate in IIS Manger. Do you have
any other ideas?
Thanks,
Jason
Post by Joe Gettys [MSFT]
This advises you that the selfupdate virtual directory can not be
contacted over port 80.
If you have the WSUS site on port 80, make sure the virtual directory
exists.
If it's on another port, make sure the default site on port 80 is
running and that the virtual directory exists
Thanks,
Joe Gettys [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by Scott Davis
One or more Update Service components could not be contacted. Check your
server status and ensure that the Windows Server Update Service is running.
Non-running services: SelfUpdate
This error is in my To Do List with a red X. All clients seem to be updating
and reporting. Any ideas?
--
Scott Davis
Brian
2005-06-15 17:20:05 UTC
Permalink
Just to clarify. The folder selfupdate has the NTFS permissions for
Administrator, system and Users with users having read access. Since Users
did not have groups in it, only an administrator had access to the selfupdate.
Post by Brian
I had the same problem and I just found my builtin group in Active directory
Users did not have any members in it. I added the domain users to the Users
group and the error was no longer there.
See if that helps
P.S. My installation is on a W2k DC
Post by Jason
Under directory security, the allow Enable anonymous access checkbox is
checked and so is integrated windows authenication.
Thanks,
Jason
Post by Lawrence Garvin
I believe if the 'selfupdate' virtual directory is lacking anonymous access
permissions, you will also get the error message.
Post by Jason
I am getting this message to. My WSUS site is set to use port 80 and
there is a virtual directory called Selfupdate in IIS Manger. Do you have
any other ideas?
Thanks,
Jason
Post by Joe Gettys [MSFT]
This advises you that the selfupdate virtual directory can not be
contacted over port 80.
If you have the WSUS site on port 80, make sure the virtual directory
exists.
If it's on another port, make sure the default site on port 80 is
running and that the virtual directory exists
Thanks,
Joe Gettys [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by Scott Davis
One or more Update Service components could not be contacted. Check your
server status and ensure that the Windows Server Update Service is running.
Non-running services: SelfUpdate
This error is in my To Do List with a red X. All clients seem to be updating
and reporting. Any ideas?
--
Scott Davis
Continue reading on narkive:
Loading...