Prev: 2008 server unable to ping sbs 2003 box
Next: Disk space Issues in SBS2003
From: Chris Puckett [MSFT] on 14 Apr 2010 14:00
I've narrowed it down to the Security Update for Exchange Server 2003
Service Pack 2 (KB976702) - Non-cluster (MS10-024). If you decline that one
(not that I recommend it), the Update Services page
(http://localhost/updateservices/home.aspx) loads without error.

Now , on to figure out what within that update is causing the error.

--
Chris Puckett

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



"Chris Puckett [MSFT]" <chris.puckett(a)online.microsoft.com> wrote in message
news:#DLDYI#2KHA.5212(a)TK2MSFTNGP04.phx.gbl...
> 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 14:17
Thanks for your efforts, Chris.

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

"Chris Puckett [MSFT]" <chris.puckett(a)online.microsoft.com> wrote in message
news:#kl1px$2KHA.4964(a)TK2MSFTNGP05.phx.gbl...
> I've narrowed it down to the Security Update for Exchange Server 2003
> Service Pack 2 (KB976702) - Non-cluster (MS10-024). If you decline that
> one (not that I recommend it), the Update Services page
> (http://localhost/updateservices/home.aspx) loads without error.
>
> Now , on to figure out what within that update is causing the error.
>
> --
> Chris Puckett
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
>
> "Chris Puckett [MSFT]" <chris.puckett(a)online.microsoft.com> wrote in
> message news:#DLDYI#2KHA.5212(a)TK2MSFTNGP04.phx.gbl...
>> 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 14:35
Something in the title? that's preventing the report from generating,
causing the error on the parent node of SBSUpdate, and also preventing the
child nodes of SBS Update from showing any updates.

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

"Chris Puckett [MSFT]" <chris.puckett(a)online.microsoft.com> wrote in message
news:#kl1px$2KHA.4964(a)TK2MSFTNGP05.phx.gbl...
> I've narrowed it down to the Security Update for Exchange Server 2003
> Service Pack 2 (KB976702) - Non-cluster (MS10-024). If you decline that
> one (not that I recommend it), the Update Services page
> (http://localhost/updateservices/home.aspx) loads without error.
>
> Now , on to figure out what within that update is causing the error.
>
> --
> Chris Puckett
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
>
> "Chris Puckett [MSFT]" <chris.puckett(a)online.microsoft.com> wrote in
> message news:#DLDYI#2KHA.5212(a)TK2MSFTNGP04.phx.gbl...
>> 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 14:47
Not that you need someone to confirm ... ;-) but declining that update does
indeed fix the report, and the SBS Update Services nodes in standard
management.

Approving the update (if approval is pending) breaks everything again. So if
the update status is anything but 'declined', the error exists.

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

"Chris Puckett [MSFT]" <chris.puckett(a)online.microsoft.com> wrote in message
news:#kl1px$2KHA.4964(a)TK2MSFTNGP05.phx.gbl...
> I've narrowed it down to the Security Update for Exchange Server 2003
> Service Pack 2 (KB976702) - Non-cluster (MS10-024). If you decline that
> one (not that I recommend it), the Update Services page
> (http://localhost/updateservices/home.aspx) loads without error.
>
> Now , on to figure out what within that update is causing the error.
>
> --
> Chris Puckett
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
>
> "Chris Puckett [MSFT]" <chris.puckett(a)online.microsoft.com> wrote in
> message news:#DLDYI#2KHA.5212(a)TK2MSFTNGP04.phx.gbl...
>> 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: Jim on 14 Apr 2010 15:10
On Wed, 14 Apr 2010 13:00:44 -0500, "Chris Puckett [MSFT]"
<chris.puckett(a)online.microsoft.com> wrote:

>I've narrowed it down to the Security Update for Exchange Server 2003
>Service Pack 2 (KB976702) - Non-cluster (MS10-024). If you decline that one
>(not that I recommend it), the Update Services page
>(http://localhost/updateservices/home.aspx) loads without error.
>
>Now , on to figure out what within that update is causing the error.

Very well spotted....though sadly uninstalling it after the event
doesn't magically make it al work again :-(



Jim
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: 2008 server unable to ping sbs 2003 box
Next: Disk space Issues in SBS2003