WSUS server synchronization failed
april
3.0 on Windows 2003 server. The synchronization was working back to Nov
3 and stopped working since Nov 4. I checked the sync history and
noticed that the sync also stopped working on Oct 30 with the same
error. And then it started working by itself the next day until Nov 3.
As I do not have any problem in getting on Internet and microsoft
websites. All the settings should be correct since it was working
before. Here is the error:
WebException: The request failed with HTTP status 404: Not Found.
at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage
message, WebResponse response, Stream responseStream, Boolean asyncCall)
at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig()
at
Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy
proxy, WebServiceCommunicationHelper webServiceHelper)
at
Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager
authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy,
Cookie cookie, WebServiceCommunicationHelper webServiceHelper)
at
Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesFromUSS()
at
Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean
allowRedirect)
Can someone advise on this? Thank you very much!!!
Lawrence Garvin (MVP)
news:OQGHPTaR...@TK2MSFTNGP02.phx.gbl...
> Has anyone out there had the same problem as I have? We are running WSUS
> 3.0 on Windows 2003 server. The synchronization was working back to Nov 3
> and stopped working since Nov 4. I checked the sync history and noticed
> that the sync also stopped working on Oct 30 with the same error. And then
> it started working by itself the next day until Nov 3. As I do not have
> any problem in getting on Internet and microsoft websites. All the
> settings should be correct since it was working before.
Is the WSUS Server configured to use a proxy server?
Did you possibly get any unsolicited help from the admin(s) responsible for
perimeter security? (Like disabling a proxy account, or blocking
port(s)/source(s) in the firewall ruleset.)
> WebException: The request failed with HTTP status 404: Not Found.
Another issue that can result in a '404' is that the IP Address(es) have
been hijacked, and you're requests are being sent to an invalid/incorrect IP
Address. If this is suspected, firewall logs would be a good resource (Can
you see HTTP sessions being requested from the WSUS Server?).
Also, running NetMon on the WSUS Server and capturing the packet traces can
give you some insight as to the intended destination of the sync packets.
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
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/profile/Lawrence.Garvin
I.T.@discussions.microsoft.com Brandon I.T.
stopped sync'ing as well at 11:47 AM Central time on November 3rd.
Now, all manual or automatic synchronizations through the WSUS MMC result in
an error "unable to resolve the the upstream server name".
april
april
> "april" <ap...@123.com> wrote in message
> news:OQGHPTaR...@TK2MSFTNGP02.phx.gbl...
>> Has anyone out there had the same problem as I have? We are running
>> WSUS 3.0 on Windows 2003 server. The synchronization was working back
>> to Nov 3 and stopped working since Nov 4. I checked the sync history
>> and noticed that the sync also stopped working on Oct 30 with the same
>> error. And then it started working by itself the next day until Nov 3.
>> As I do not have any problem in getting on Internet and microsoft
>> websites. All the settings should be correct since it was working before.
>
> Is the WSUS Server configured to use a proxy server?
NO
>
> Did you possibly get any unsolicited help from the admin(s) responsible
> for perimeter security? (Like disabling a proxy account, or blocking
> port(s)/source(s) in the firewall ruleset.)
NO
>
>> WebException: The request failed with HTTP status 404: Not Found.
>
> Another issue that can result in a '404' is that the IP Address(es) have
> been hijacked, and you're requests are being sent to an
> invalid/incorrect IP Address. If this is suspected, firewall logs would
> be a good resource (Can you see HTTP sessions being requested from the
> WSUS Server?).
Would you please advise where is firewall logs located? Thank you very much.
>
> Also, running NetMon on the WSUS Server and capturing the packet traces
> can give you some insight as to the intended destination of the sync
> packets.
>
>
I appreciate your response. Thanks a lot!
Brandon I.T.
in order to track my own troubleshooting steps and to not interfere with
yours. I answered Lawrence Garvin's questions in my own thread for my own
server.
Basically though my WSUS server stopped syncing on October 30th just like
yours then began syncing for a few days then stopped again on November 3rd
and has not been able to sync since.
I verified it's not a firewall issue. In fact, my firewall admin says he
sees no traffic making it to the firewall from the WSUS server during the
synchronization process. It's almost like the hard-coded address for
Microsoft Update inside WSUS is incorrect or expired. I've tried re-running
the WSUS Server Configuration Wizard just to try and manually define a
Windows Update site but that doesn't work.
I believe WSUS is hard-coded to connect to "update.microsoft.com" for
updates. A ping request to that address from my WSUS server returned a
response from "update.microsoft.com.nsatc.com" [207.46.17.61]. I get no
reply.
Here's hoping Lawrence has some ideas on how to get this fixed. I still
don't have the patches from Patch Tuesday to release.
Lawrence Garvin (MVP)
news:98E20736-F2AE-49A7...@microsoft.com...
> I verified it's not a firewall issue. In fact, my firewall admin says he
> sees no traffic making it to the firewall from the WSUS server during the
> synchronization process.
*NO* traffic -- including DNS requests?
If there's no request to resolve the DNS name coming from the server,
then that suggest the problem is at the server.
> It's almost like the hard-coded address for
There is *NO* "hard-coded address" for Microsoft Update inside WSUS.
WSUS references a URL that's been in use for eons, and I assure you it's
still working.
Try running 'ipconfig /flushdns' on the WSUS Server to flush the DNS cache,
and then force a manual synchronization and observe what happens.
> I've tried re-running
> the WSUS Server Configuration Wizard just to try and manually define a
> Windows Update site but that doesn't work.
Nope. :-)
> I believe WSUS is hard-coded to connect to "update.microsoft.com" for
> updates. A ping request to that address from my WSUS server returned a
> response from "update.microsoft.com.nsatc.com" [207.46.17.61]. I get no
> reply.
Getting no reply to a ping from inside a corporate firewall is not
conclusive.
FYI.. I have 179 synchronzations (2x daily) from 8/16 through this morning
(an hour ago),
and not a single one shows a failure. I pulled down 55 new updates Tuesday
evening.
Lawrence Garvin (MVP)
> 3.0 on Windows 2003 server. The synchronization was working back to Nov 3
> and stopped working since Nov 4. I checked the sync history and noticed
> that the sync also stopped working on Oct 30 with the same error. And then
> it started working by itself the next day until Nov 3.
April, based on conversations in the new thread that Brandon created,
there appears to be a likely cause for this issue.
Can you please confirm the server version that you are using.
The "Server Version" can be obtained from the WSUS UI Admin Console,
on the server page, center pane, lower left corner in the group titled
"Connection".
The version number *should* be 6.1.6001.65 indicating WSUS 3.0 Service Pack
1.
Based on something we're tracking down with Brandon, I have reason to
believe you may still be running the =Release Candidate= version of WSUS
3.0, and Microsoft finally got around to pulling the plug on the RC server
DNS entries, which would explain the '404' errors encountered by you and
Brandon on exactly the same dates.
jared...@gmail.com
running the release candidate version. Is that the version you're
running?
viper...@gmail.com
wsusutil configuressl
restart wsusservice
restart bits
iisreset