From: Chris Puckett [MSFT] on
Here's the solution for now.

Go into the WSUS Console and DECLINE Security Update for Exchange 2000
Server Service Pack 3 (KB976703)

--
Chris Puckett

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



"James Hurrell" <j_a_hurrell(a)remove.hotmail.com> wrote in message
news:u7QfgmA3KHA.4964(a)TK2MSFTNGP05.phx.gbl...
> On 14/04/2010 19:00, Chris Puckett [MSFT] 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.
>>
> Thanks for your effort Chris. I've not declined the update at the moment -
> will wait to see if there is anything further that can be done.
>
> Many thanks.

From: Susan Bradley on
Chris Puckett [MSFT] wrote:
> Here's the solution for now.
>
> Go into the WSUS Console and DECLINE Security Update for Exchange 2000
> Server Service Pack 3 (KB976703)
>
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
From: Jim on
On Wed, 14 Apr 2010 21:15:25 -0700, Susan Bradley
<sbradcpa(a)pacbell.net> wrote:

>Chris Puckett [MSFT] wrote:
>> Here's the solution for now.
>>
>> Go into the WSUS Console and DECLINE Security Update for Exchange 2000
>> Server Service Pack 3 (KB976703)
>>
>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


You guys rock!

May I ask how you narrowed it down to this one?



Jim
From: Susan Bradley on
Jim wrote:
> On Wed, 14 Apr 2010 21:15:25 -0700, Susan Bradley
> <sbradcpa(a)pacbell.net> wrote:
>
>
>> Chris Puckett [MSFT] wrote:
>>
>>> Here's the solution for now.
>>>
>>> Go into the WSUS Console and DECLINE Security Update for Exchange 2000
>>> Server Service Pack 3 (KB976703)
>>>
>>>
>> 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
>>
>
>
> You guys rock!
>
> May I ask how you narrowed it down to this one?
>
>
>
> Jim
>
Easy. Chris, Damian and Justin are geniuses.


I'm guessing tracing back through the WSUS sync logs and seeing what it
was barfing on.
From: Jim on
On Wed, 14 Apr 2010 23:34:38 -0700, Susan Bradley
<sbradcpa(a)pacbell.net> wrote:

>Jim wrote:
>> On Wed, 14 Apr 2010 21:15:25 -0700, Susan Bradley
>> <sbradcpa(a)pacbell.net> wrote:
>>
>>
>>> Chris Puckett [MSFT] wrote:
>>>
>>>> Here's the solution for now.
>>>>
>>>> Go into the WSUS Console and DECLINE Security Update for Exchange 2000
>>>> Server Service Pack 3 (KB976703)
>>>>
>>>>
>>> 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
>>>
>>
>>
>> You guys rock!
>>
>> May I ask how you narrowed it down to this one?
>>
>>
>>
>> Jim
>>
>Easy. Chris, Damian and Justin are geniuses.
>
>
>I'm guessing tracing back through the WSUS sync logs and seeing what it
>was barfing on.


Beer is on the way to you all :-)


Jim