Replica wsus shows as an autonomous server

I have WSUS 3.0 SP1 on Server 2003 and the same for the replica

The installation has worked fine and all seemed well, the updates have
sync'd across as well as the update approvals

The problem i am having is on the main Wsus server in the downstream server
section it shows my replica server as an autonomous server? It is rolling up
sucessfully and sync regularly.

Any ideas anyone? I can provide more info if needed.
Thanks in advance

Well, obviously only one of those statements can be accurate, sinceautonmous

Well, obviously only one of those statements can be accurate, since
autonmous servers do not support reporting rollup.

Of course, that also presumes that the successful operation of "reporting
rollup" has been properly characterized in this scenario.

My observation on my server, which currently has nine downstream servers of
mixed heritage, is that the Mode column is an accurate representation of the
status of a downstream server.

The question here really discounts any concern with reporting rollup
working, or not working. Either the downstream server is autonomous, or it
is a replica. If it is a replica, then whether or not Reporting Rollup is
enabled may be of interest, but it seems to me that the fundamental question
is whether the console is accurately reporting the state of the downstream
server, and I am inclined to trust the actual data reported rather than the
interpretation that "reporting rollup" is working on that downstream server.

On the downstream server in the Options | Update Source and Proxy Server
dialog, on the Update Source tab,
is the checkbox "This server is a replica of the upstream server checked"?
and is the "Server Name" the correct value for the upstream server?

If the downstream server is a replica configured to use the correct upstream
server,
then what was the time of the last successful synchronization by this
downstream server,
and what is the time reported by the upstream server for "Last
Synchronization" of this downstream server?

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

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

Sorry it also says this as well just above it2009-11-19 04:00:19.

Sorry it also says this as well just above it

2009-11-19 04:00:19.596
UTC	Error	WsusService.19	UpdateServicesRollup.GetRollupConfiguration	Failed
to get rollup configuration from USS. Exception=The request failed with HTTP
status 401: Unauthorized.
at
Microsoft.UpdateServices.Internal.Reporting.Rollup.UpdateServicesRollup.GetRollupConfiguration()
at
Microsoft.UpdateServices.Internal.Reporting.Rollup.UpdateServicesRollup.SynchronizeConfiguration()
at
Microsoft.UpdateServices.Internal.Reporting.Rollup.UpdateServicesRollup.DoRollup()
at
Microsoft.UpdateServices.Internal.Reporting.Rollup.RollupAgent.WakeUpWorkerThreadProc()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at
System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext
executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

Okay sorry about my terminology let me go about this the correct way:Server1

Okay sorry about my terminology let me go about this the correct way:

Server1 Setup as the main instance of WSUS
Server2 is the replica server

Background info: They do not use SSL and are both on different subnets ??? I
think this may be part of the root of the problem.

Server 1 is functioning correctly and has all machines connecting to it.

On server2 the update source and proxy server this is cofigured correctly (I
have tried netbios and the FQDN name of server1) I have not filled in the
proxy server as it is downloading its updates from server1. Under the source
tab the option is ticked to make it a replica server.

Server2 shows all the updates that I have downloaded to the system with the
approvals I have chosen.
The problem is under server1 when you click downstream servers you see
server2 listed. Server2 is syncronizing correctly (and on both servers they
show the same time and date) and this shows in the last syncronization
column. The mode column however shows ???unknown??? If you click on the server to
look at its details under mode it says ???autonomous??? It does not have a last
rollup time it just says ???not yet rolled up??? and it lists the server version
as ???0.0.0.0???

This may help as well

The software distribution log off the replica server says this repeatedly

2009-11-19 04:00:19.596
UTC	Error	WsusService.19	UpdateServicesRollup.SynchronizeConfiguration	Failed
to handle rollup configuration. Rollup terminated.
at
Microsoft.UpdateServices.Internal.Reporting.Rollup.UpdateServicesRollup.SynchronizeConfiguration()
at
Microsoft.UpdateServices.Internal.Reporting.Rollup.UpdateServicesRollup.DoRollup()
at
Microsoft.UpdateServices.Internal.Reporting.Rollup.RollupAgent.WakeUpWorkerThreadProc()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at
System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext
executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

Well, that is a lot more useful than the other information.

Well, that is a lot more useful than the other information. :)

Pretty simple statement. The rollup is failing because the upstream server
is denying the connection.

Next step is to find the IIS log entry in the Upstream Server and get the
SUBCODE for the HTTP 401 error and determine exactly which resource and
reason the access was denied.


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

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

This is what its saying in the IIS upstream server log.

This is what its saying in the IIS upstream server log.
I have no idea what this means, im guessing the last bit on the end is the
unauthorized error, and the apiremoting30 is the bits its not getting access
to?

2009-11-25 15:02:13 W3SVC1317488195 SERVER1 POST
/ApiRemoting30/WebService.asmx - 8530 - SERVER1
Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.42) 401 1 0
2009-11-25 15:02:13 W3SVC1317488195 SERVER1 POST
/ApiRemoting30/WebService.asmx - 8530 GRABBIT\adminusr SERVER1
Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.42) 200 0 0
2009-11-25 15:02:13 W3SVC1317488195 SERVER1 POST
/ApiRemoting30/WebService.asmx - 8530 - SERVER1
Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.42) 401 1 0
2009-11-25 15:02:13 W3SVC1317488195 SERVER1 POST
/ApiRemoting30/WebService.asmx - 8530 GRABBIT\adminusr SERVER1
Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.42) 200 0 0
2009-11-25 15:03:34 W3SVC1317488195 SERVER1 POST
/reportingwebservice/reportingwebservice.asmx - 8530 - SERVER1
Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.42) 401 1 0
2009-11-25 15:03:34 W3SVC1317488195 SERVER1 POST
/ApiRemoting30/WebService.asmx - 8530 - SERVER1
Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.42) 401 1 0
2009-11-25 15:03:34 W3SVC1317488195 SERVER1 POST
/ApiRemoting30/WebService.asmx - 8530 GRABBIT\SERVER1$ SERVER1
Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.42) 200 0 0
2009-11-25 15:03:34 W3SVC1317488195 SERVER1 POST
/ServerSyncWebService/serversyncwebservice.asmx - 8530 - SERVER1
Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.42) 401 1 0
2009-11-25 15:03:34 W3SVC1317488195 SERVER1 POST
/ClientWebService/Client.asmx - 8530 - SERVER1
Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.42) 401 1 0
2009-11-25 15:03:34 W3SVC1317488195 SERVER1 POST
/SimpleAuthWebService/SimpleAuth.asmx - 8530 - SERVER1
Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.42) 401 1 0
2009-11-25 15:03:34 W3SVC1317488195 SERVER1 POST
/DssAuthWebService/DssAuthWebService.asmx - 8530 - SERVER1
Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.42) 401 1 0

This pair of commands is a standard console connection session.

This pair of commands is a standard console connection session. The first
entry is an attempt to authenticate anonymously, which is not permitted on
the /ApiRemoting30 webservice; the second entry is the authenticated
connection for the GRABBIT\adminusr console session.



This is a connection to the /ReportingWebService being denied with an HTTP
401.1 error.



This is a connection to the /ServerSyncWebService being denied with an HTTP
401.1 error



This is a connection to the /ClientWebService being denied with an HTTP
401.1 error



This is a connection to the /SimpleAuthWebService being denied with an HTTP
401.1 error



This is a connection to the /DssAuthWebService being denied with an HTTP
401.1 error.


*ALL* of the above services should be accessible via anonymous connections,
and the fact that they are being denied indicates to me that Anonymous
Access for the "WSUS Administration" virtual server has been DISABLED.

Re-ENABLE Anonymous Access for the "WSUS Administration" virtual server and
your issues should all be resolved.


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

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