Prev: Last night patches broke network connectivity
Next: Windows 2003 SBS Max connections / users
From: Chris Puckett [MSFT] on 14 Apr 2010 17:53
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.



"Susan Bradley" <sbradcpa(a)pacbell.net> wrote in message
news:eANPJkA3KHA.1016(a)TK2MSFTNGP02.phx.gbl...
> Jim wrote:
>> On Wed, 14 Apr 2010 12:02:46 -0700, Susan Bradley
>> <sbradcpa(a)pacbell.net> wrote:
>>
>>
>>> Jim wrote:
>>>
>>>> Hmm...using different google criteria I just found this:
>>>>
>>>> http://www.eggheadcafe.com/software/aspnet/35974985/server-performance-report.aspx
>>>>
>>>> Not a fix, but others having the problem.
>>>>
>>>> Jim
>>>>
>>> Yes it's the message about three up from this one.
>>>
>>> In investigation, hang loose.
>>>
>>
>> Thanks Susan, I don't often check the daily report as that's someone
>> else's remit, so I didn't make the connection.
>>
>> As I've commented on the other thread, uninstalling that patch sadly
>> didn't make it all work again.
>>
>> Fingers crossed you can narrow it down (and identify a fix).
>>
>>
>>
>> Jim
>>
> The issue is not with the update it's with the metadata sync with WSUS.
>
> Reinstall that update and then hang tight for exact instructions.

From: Susan Bradley on 15 Apr 2010 00:15
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
First  |  Prev  | 
Pages: 1 2
Prev: Last night patches broke network connectivity
Next: Windows 2003 SBS Max connections / users