Downstream Servers Not Reporting.

I have one replica downstream server that can't roll-up its status to the
upstream server, sync works.
All WSUS servers are 3.0 SP1 and all other downstream servers roll-up as
expected.

The status of the malfunctioning server on the upstream server under the
"Downstream Servers" MMC node shows up like the following:
- Last Rollup: not yet rolled up
- Server Version: 0.0.0.0
(it should be 3.1.6001.65).

The log file %programfiles%\Update
Services\Logfiles\SoftwareDistribution.log seems to reveal there's something
wrong with the roll-up process (see excerpt below).

Someone have any idea about how to fix it? Tried several time to change the
status of the downstream server from Replica to Autonomous and even from
downstream to upstream, but it did not fix the issue.

Thanks so much, any suggestion will be more than welcome!
Regards - Gabriele.


2009-08-24 02.27.48.801
UTC Warning WsusService.26 DBConnection.OnReceivingInfoMessage Null value is
eliminated by an aggregate or other SET operation.
2009-08-24 02.27.48.832
UTC Error WsusService.26 UpdateServicesRollup.DoDownstreamServersInformatio nRollup Failed to rollup server information for child servers.
at
Microsoft.UpdateServices.Internal.Reporting.Rollup .UpdateServicesRollup.DoDownstreamServersInformati onRollup()
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(Objec t userData)
at
System.Runtime.CompilerServices.RuntimeHelpers.Exe cuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(Exec utionContext
executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionCon text
executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
2009-08-24 02.27.48.847
UTC Error WsusService.26 UpdateServicesRollup.DoRollup Failed to rollup DSS
information. Exception=System.ApplicationException: invalid summaryId 10 in
result from sPGetDownstreamServerClientSummaries
at
Microsoft.UpdateServices.Internal.ReportingDatabas eAccess.ExecuteSPGetDownstreamServerClientSummarie s(Guid serverId, Boolean isLocalServer)
at
Microsoft.UpdateServices.Internal.Reporting.Rollup .UpdateServicesRollup.GetClientSummaries(Guid serverId, Boolean isLocalServer)
at
Microsoft.UpdateServices.Internal.Reporting.Rollup .UpdateServicesRollup.GetServerRollupInfoForLocalS erver()
at
Microsoft.UpdateServices.Internal.Reporting.Rollup .UpdateServicesRollup.DoDownstreamServersInformati onRollup()
at
Microsoft.UpdateServices.Internal.Reporting.Rollup .UpdateServicesRollup.DoRollup(). Rollup terminated.
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(Objec t userData)
at
System.Runtime.CompilerServices.RuntimeHelpers.Exe cuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(Exec utionContext
executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionCon text
executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
............
2009-08-24 02.36.54.816
UTC Warning WsusService.8 DBConnection.OnReceivingInfoMessage The join order
has been enforced because a local join hint is used.
2009-08-24 02.36.59.691
UTC Warning w3wp.1 SoapUtilities.CreateException ThrowException: actor =
http://server01.domain.com/Reporting...ebService.asmx,
ID=e42e0805-a9ad-40e3-a07c-3f4cbda1ed00, ErrorCode=ConfigChanged, Message=,
Client=08c48514-7f3b-4c2c-9b16-7050f2035158
2009-08-24 02.36.59.691
UTC Error w3wp.1 WebService.ReportEventBatch Exception occured in
ReportEventBatch: Fault occurred
at
Microsoft.UpdateServices.Internal.Reporting.WebSer vice.ReportEventBatch(Cookie cookie, DateTime clientTime, ReportingEvent[] eventBatch)
at System.RuntimeMethodHandle._InvokeMethodFast(Objec t target, Object[]
arguments, SignatureStruct& sig, MethodAttributes methodAttributes,
RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[]
arguments, Signature sig, MethodAttributes methodAttributes,
RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean
skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Web.Services.Protocols.LogicalMethodInfo.In voke(Object target,
Object[] values)
at System.Web.Services.Protocols.WebServiceHandler.In voke()
at System.Web.Services.Protocols.WebServiceHandler.Co reProcessRequest()
at
System.Web.Services.Protocols.SyncSessionlessHandl er.ProcessRequest(HttpContext context)
at
System.Web.HttpApplication.CallHandlerExecutionSte p.System.Web.HttpApplication.IExecutionStep.Execut e()
at System.Web.HttpApplication.ExecuteStep(IExecutionS tep step, Boolean&
completedSynchronously)
at
System.Web.HttpApplication.ApplicationStepManager. ResumeSteps(Exception error)
at
System.Web.HttpApplication.System.Web.IHttpAsyncHa ndler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData)
at System.Web.HttpRuntime.ProcessRequestInternal(Http WorkerRequest wr)
at System.Web.HttpRuntime.ProcessRequestNoDemand(Http WorkerRequest wr)
at System.Web.Hosting.ISAPIRuntime.ProcessRequest(Int Ptr ecb, Int32
iWRType)
2009-08-24 02.37.04.144
UTC Warning w3wp.1 SoapUtilities.CreateException ThrowException: actor =
http://server01.domain.com/ClientWebService/client.asmx,
ID=5ee1a6aa-d2b2-468f-b3ea-dfd07bbcfa07, ErrorCode=ConfigChanged, Message=,
Client=5aea3681-73c0-4f04-baa3-75c94f3157f2

"Gabriel/TFI" <> wrote in message
news:68ECEA5A-7FEF-4E5B-9D4B-...

>I have one replica downstream server that can't roll-up its status to the
> upstream server, sync works.

> All WSUS servers are 3.0 SP1 and all other downstream servers roll-up as
> expected.

Hi Gabriel..

I've not seen a failure like this before, but given the fact that other
replicas are rolling up without issue, I'm inclined to think there's
something seriously wrong with this server -- and just this server.

My first guess here would be something is fubar in the database.

Since it is a replica server -- my first suggestion would be to uninstall
WSUS (keep the content but not the database), and also uninstall the
Windows Internal Databse (see Appendix A of the WSUS Operations Guide for
instructions).

Then reinstall WSUS as a replica (using the same content store) -- and see
if a new, clean database instance and database resolves this issue.



> Error WsusService.26
> UpdateServicesRollup.DoDownstreamServersInformatio nRollup Failed to rollup
> server information for child servers.
> at
> Microsoft.UpdateServices.Internal.Reporting.Rollup .UpdateServicesRollup.DoDownstreamServersInformati onRollup()

> Error WsusService.26 UpdateServicesRollup.DoRollup Failed to rollup DSS
> information.
> Exception=System.ApplicationException: invalid summaryId 10 in result
> from sPGetDownstreamServerClientSummaries
> at Microsoft.UpdateServices.Internal.ReportingDatabas eAccess.
> ExecuteSPGetDownstreamServerClientSummaries(Guid serverId,
> Boolean isLocalServer)

FWIW... this is the actual failure cause --- it looks to be an error
attempting to collect client summary data from the database, specifically a
bad data value, it looks like. If I were to actually look up the method call
in the API I could give you a more definitive answer, and while it might be
"repairable" (maybe even as simple as deleting one or more computers from
the replica server and letting them re-register/report again), I suspect the
amount of time (and risk) it would take to try to repair it (even assuming
we can identify the correct steps to repair it), is significantly more
involved than the time (and lack of risk) in simply reinstalling the server.

> Error w3wp.1 WebService.ReportEventBatch Exception occured in
> ReportEventBatch: Fault occurred
> at
> Microsoft.UpdateServices.Internal.Reporting.WebSer vice.ReportEventBatch(Cookie
> cookie, DateTime clientTime, ReportingEvent[] eventBatch)

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

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Hi Lawrence,

Thanks for your kind reply.
I concur with all your points, rebuilding was my thinking as well, but
before doing that I tried to look for a solution.
I've seen some posts around the web about the same issue I am experiencing,
but no solution was post.

I could not agree more, rebuilding in this case might be much safer than
trying to fix and mucking the DB!

Cheers - Gabriele.

"Lawrence Garvin [MVP]" wrote:

> "Gabriel/TFI" <> wrote in message
> news:68ECEA5A-7FEF-4E5B-9D4B-...
>
> >I have one replica downstream server that can't roll-up its status to the
> > upstream server, sync works.
>
> > All WSUS servers are 3.0 SP1 and all other downstream servers roll-up as
> > expected.
>
> Hi Gabriel..
>
> I've not seen a failure like this before, but given the fact that other
> replicas are rolling up without issue, I'm inclined to think there's
> something seriously wrong with this server -- and just this server.
>
> My first guess here would be something is fubar in the database.
>
> Since it is a replica server -- my first suggestion would be to uninstall
> WSUS (keep the content but not the database), and also uninstall the
> Windows Internal Databse (see Appendix A of the WSUS Operations Guide for
> instructions).
>
> Then reinstall WSUS as a replica (using the same content store) -- and see
> if a new, clean database instance and database resolves this issue.
>
>
>
> > Error WsusService.26
> > UpdateServicesRollup.DoDownstreamServersInformatio nRollup Failed to rollup
> > server information for child servers.
> > at
> > Microsoft.UpdateServices.Internal.Reporting.Rollup .UpdateServicesRollup.DoDownstreamServersInformati onRollup()
>
> > Error WsusService.26 UpdateServicesRollup.DoRollup Failed to rollup DSS
> > information.
> > Exception=System.ApplicationException: invalid summaryId 10 in result
> > from sPGetDownstreamServerClientSummaries
> > at Microsoft.UpdateServices.Internal.ReportingDatabas eAccess.
> > ExecuteSPGetDownstreamServerClientSummaries(Guid serverId,
> > Boolean isLocalServer)
>
> FWIW... this is the actual failure cause --- it looks to be an error
> attempting to collect client summary data from the database, specifically a
> bad data value, it looks like. If I were to actually look up the method call
> in the API I could give you a more definitive answer, and while it might be
> "repairable" (maybe even as simple as deleting one or more computers from
> the replica server and letting them re-register/report again), I suspect the
> amount of time (and risk) it would take to try to repair it (even assuming
> we can identify the correct steps to repair it), is significantly more
> involved than the time (and lack of risk) in simply reinstalling the server.
>
> > Error w3wp.1 WebService.ReportEventBatch Exception occured in
> > ReportEventBatch: Fault occurred
> > at
> > Microsoft.UpdateServices.Internal.Reporting.WebSer vice.ReportEventBatch(Cookie
> > cookie, DateTime clientTime, ReportingEvent[] eventBatch)
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>