Windows Server - WSUS 3 - replica server fails to replicate approved updates

Asked By LeaUK

28-May-10 05:49 AM

Hi All

We've recently made one of our servers a replica and enabled rollup
reporting, but even though I cannot approve updates on the replica (grayed
out) it has significantly different amount of approved updates.  Master has
1K+ the replica only 400 or so.

Also I am not convinced that it is rolling up the reports either as the
emailed reports from both servers are significantly different.

What am I doing wrong?

Any help much appreciated.
Lea

28-May-10 08:23 AM

Ah Ha - I see why, the sync log shows sync failures (detailed error below).

But the replica can connect to the master with no problem. Have tested the
following links and all ok:

https://compname:ourport/iuident.cab
https://compname:ourport/selfupdate/iuident.cab
https://compname:ourport/clientwebservice/wusserverversion.xml
https://compname:ourport/simpleauthwebservice/simpleauth.asmx
https://compname:ourport/SelfUpdate/wuident.cab

The replica can clearly coms with the master but it still fails to sync?

I tried:
https://compname:ourport/serversyncwebservice/serversyncwebservice.asmx

as I suspect this is the site that allows sync, it connected but I am not
sure what the result should be (if any)?



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)

Many thanks
Lea

29-May-10 07:37 PM

This is a natural artifact of converting an autonomous server to a replica:

[a] The former autonomous server keeps all of the approvals not synchronized
because the updates do not exist on the upstream server.
[b] The new replica server also gets any approvals that it did not
previously have after synchronizing with the upstream server.

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2010)

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

29-May-10 07:38 PM

it is not synchronizing because you have misconfigured the URL of the
upstream server.

HTTP 404 -- Not Found -- means the URL you supplied does not actually exist.

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2010)

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin