Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

WSUS 3 - replica server fails to replicate approved updates

373 views
Skip to first unread message

LeaUK

unread,
May 28, 2010, 5:49:03 AM5/28/10
to
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'm not convinced that it's 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

LeaUK

unread,
May 28, 2010, 8:23:00 AM5/28/10
to
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'm 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

Lawrence Garvin [MVP]

unread,
May 29, 2010, 7:37:02 PM5/29/10
to
"LeaUK" <Le...@discussions.microsoft.com> wrote in message
news:C7C83A81-AAEA-4424...@microsoft.com...

> 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.

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

Lawrence Garvin [MVP]

unread,
May 29, 2010, 7:38:16 PM5/29/10
to
"LeaUK" <Le...@discussions.microsoft.com> wrote in message
news:D8194086-9E89-4C66...@microsoft.com...

> WebException: The request failed with HTTP status 404: Not Found.

It's 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.

0 new messages