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 RenoufYep, 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 SamuelssonHi
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 GarvinWell, shucks...
back to Joe. :-)
Post by JasonUnder directory security, the allow Enable anonymous access checkbox is
checked and so is integrated windows authenication.
Thanks,
Jason
Post by Lawrence GarvinI believe if the 'selfupdate' virtual directory is lacking anonymous
access permissions, you will also get the error message.
Post by JasonI 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 DavisOne 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