If your R2 servers’ monitoring reports are not working, it appears that something occurred with the sync of WSUS last night.

Update 4/14/2010 9 p.m pacific

RESOLUTION HERE:

The Official SBS Blog : Windows SBS 2003 Update Services Gives Error: The Element Already Exists in the Collection:
http://blogs.technet.com/sbs/archive/2010/04/14/windows-sbs-2003-update-services-gives-error-the-element-already-exists-in-the-collection.aspx

If your SBS 2003 R2 servers’ monitoring reports are not working, it appears that something occurred with the sync of WSUS last night.

Hang loose, figuring out what went boom.

Try kicking a manual resync and see if any ‘bad duplicates’ expire off.

“Les Connor [SBS MVP” wrote in message

It appears that all SBS 2k3 R2 reports are broken this morning. It may have something to do with the large number of updates that were sync’d overnight. The normal tricks to get the report working, aren’t.

– 
———————————————–
Les Connor [SBS MVP]

I was about to post on the same issue, but I think it started before applying any updates. When I synced the updates Tuesday afternoon and then checked for updates on a client computer, Server Manager did not show any updates to approve even though the WSUS console showed updates were needed. I approved the updates in WSUS, and the installations proceeded without incident.

Going to the Update Services node in Serve Manager generates an error that looks like it could be a problem with duplicates in the Pending Updates:

[ArgumentException: The element already exists in the collection. Parameter name: value]
  Microsoft.UpdateServices.Administration.WsusCollection.CheckItemIsValid(Int32 index, Object value) +152
  Microsoft.UpdateServices.Administration.WsusCollection.OnInsert(Int32 index, Object value) +20
  System.Collections.CollectionBase.System.Collections.IList.Add(Object value) +106
  Microsoft.UpdateServices.Administration.UpdateSummaryCollection.Add(IUpdateSummary value) +10
  Microsoft.UpdateServices.Internal.BaseApi.UpdateSummary.BuildSummaryCollection(GenericReadableRow[] rows, GroupBy groupBy) +476
  Microsoft.UpdateServices.Internal.BaseApi.ComputerTargetGroup.GetSummaryPerUpdate() +117
  Microsoft.SBS.UpdateServices.DataProvider.GetPendingUpdateCollection() +420
  Microsoft.SBS.UpdateServices.DataProvider.GetPendingUpdateCounts() +5
  Microsoft.SBS.UpdateServices.StatusPage.Utility.GetStatusItems(Boolean waitingForSyncStart) +2705

2 Thoughts on “If your R2 servers’ monitoring reports are not working, it appears that something occurred with the sync of WSUS last night.

  1. Joe-XLS on April 14, 2010 at 10:55 pm said:

    Thanks.. Glad to know that i’m not the only person with this issue!!!

    I have 3 x Win 2k3 SBS R2 with WSUS 3.2 SP2 installed. They’re all doing as described above. Monitoring & Reporting as well as Update Services are screwed within Server Manager. Also the Subgroups of Update Services aren’t showing anything at all.

    I will be very interested to know how to fix this, if you manage to figure it out.

  2. bradley on April 14, 2010 at 11:39 pm said:

    The Official SBS Blog : Windows SBS 2003 Update Services Gives Error: The Element Already Exists in the Collection:
    http://blogs.technet.com/sbs/archive/2010/04/14/windows-sbs-2003-update-services-gives-error-the-element-already-exists-in-the-collection.aspx

Post Navigation