Prev: 2008 server unable to ping sbs 2003 box
Next: Disk space Issues in SBS2003
From: Les Connor [SBS MVP] on 14 Apr 2010 09:37
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]

From: Paul Shapiro on 14 Apr 2010 10:02
"Les Connor [SBS MVP]" <les.connor(a)DEL.cfive.ca> wrote in message
news:#14pye92KHA.5196(a)TK2MSFTNGP05.phx.gbl...
> 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


From: James Hurrell "j_a_hurrell at hotmail on 14 Apr 2010 10:38
On 14/04/2010 14:37, Les Connor [SBS MVP] wrote:
> 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.
>
Ah... i have this issue too on SBS 2003 R2. With WSUS 2 (yes I know I
should upgrade).... This morning's emailed report just contained:

The page cannot be displayed
An error occurred on the page you are trying to view.

--------------------------------------------------------------------------------

To work around this problem, perform the following steps. After each
step, try again to access the page.

Ensure that the MSSQL$SBSMONITORING service is started.
Ensure that the server is not low on memory or disk space.
Restart the server.
Verify that the server is functional and that there are no system-wide
problems.
Run the Set Up Monitoring Reports and Alerts task in the Server
Management Monitoring and Reporting taskpad.


I thought it was just a blip as it does happen occasionally. On futher
investigation (and like Paul) I get the same error message in the
"Update Services" node (The element already exists in the collection.
Parameter name: value )

My WSUS server synchronises overnight and new updates are pending today.

Searching Google for "The element already exists in the collection.
Parameter name: value " I found this:

http://support.microsoft.com/kb/938314

But have not tried the fixes...

Any ideas???

From: Chris Puckett [MSFT] on 14 Apr 2010 10:52
I'll look into it and see what I can find.

--
Chris Puckett

This posting is provided "AS IS" with no warranties, and confers no rights.



"James Hurrell" <"j_a_hurrell at hotmail com"> wrote in message
news:#C1ZoA#2KHA.4016(a)TK2MSFTNGP05.phx.gbl...
> On 14/04/2010 14:37, Les Connor [SBS MVP] wrote:
>> 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.
>>
> Ah... i have this issue too on SBS 2003 R2. With WSUS 2 (yes I know I
> should upgrade).... This morning's emailed report just contained:
>
> The page cannot be displayed
> An error occurred on the page you are trying to view.
>
> --------------------------------------------------------------------------------
>
> To work around this problem, perform the following steps. After each step,
> try again to access the page.
>
> Ensure that the MSSQL$SBSMONITORING service is started.
> Ensure that the server is not low on memory or disk space.
> Restart the server.
> Verify that the server is functional and that there are no system-wide
> problems.
> Run the Set Up Monitoring Reports and Alerts task in the Server Management
> Monitoring and Reporting taskpad.
>
>
> I thought it was just a blip as it does happen occasionally. On futher
> investigation (and like Paul) I get the same error message in the "Update
> Services" node (The element already exists in the collection. Parameter
> name: value )
>
> My WSUS server synchronises overnight and new updates are pending today.
>
> Searching Google for "The element already exists in the collection.
> Parameter name: value " I found this:
>
> http://support.microsoft.com/kb/938314
>
> But have not tried the fixes...
>
> Any ideas???
>
From: Les Connor [SBS MVP] on 14 Apr 2010 12:17
right, it's not related to the application (installation) of updates, it's
got something to do with what updates were synchronized overnight. See
Chris's response, he'll look into it ;-).

--
-----------------------------------------------
Les Connor [SBS MVP]

"Paul Shapiro" <paul(a)hideme.broadwayData.com> wrote in message
news:OBy2is92KHA.5588(a)TK2MSFTNGP06.phx.gbl...
> "Les Connor [SBS MVP]" <les.connor(a)DEL.cfive.ca> wrote in message
> news:#14pye92KHA.5196(a)TK2MSFTNGP05.phx.gbl...
>> 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
>
>
 |  Next  |  Last
Pages: 1 2 3 4 5
Prev: 2008 server unable to ping sbs 2003 box
Next: Disk space Issues in SBS2003