Forwarded to WSUS newsgroup via crosspost.
Try posting to the WSUS-specific newsgroup instead:
microsoft.public.windows.server.update_services
Via the web-interface:
http://www.microsoft.com/communities...pdate_services
Via your newsreader:
news://msnews.microsoft.com/microsof...pdate_services
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin; DTS-L.org
Scooty wrote:
> Hi all
> I recently upgraded my Win2k3 environment to WSUS Version 3
> It seemed to work OK for a few days but now all my replica servers get
> a
> The upstream server is too busy to process the request when attempting
> to sync with the master server
> When I click on details I see the following
>
> WebException: The request failed with HTTP status 503: Service
> Unavailable.
> at
> System.Web.Services.Protocols.SoapHttpClientProtoc ol.ReadResponse(SoapClientMessage
> message, WebResponse response, Stream responseStream, Boolean
> asyncCall)
> at
> System.Web.Services.Protocols.SoapHttpClientProtoc ol.Invoke(String
> methodName, Object[] parameters)
> at
> Microsoft.UpdateServices.ServerSyncWebServices.Ser verSync.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.CatalogSyncAge ntCore.SyncConfigUpdatesFromUSS()
> at
> Microsoft.UpdateServices.ServerSync.CatalogSyncAge ntCore.ExecuteSyncProtocol(Boolean
> allowRedirect)
>
> Any suggestions would be most welcome
> Otherwise I think the only solution is to roll back to Version 2
>
> Regards
> Scott