Security Update for Exchange 2000 Service Pack 3 (KB976703) De
|
Prev: Adprep can't update AD during SBS2008 migration
Next: Changing Domain Name through Internet Address Management Wizard
From: gocat2005 on 16 Apr 2010 03:24 Hi Susan The version of exchange in SBS2003R2Prem is 6.5.7638.1 which I understand is Exchange 2003 SP2. So I guess the offending update does not relate to this environment. However, today in the performance report I got error: Server Status Report: URL: http://localhost/monitoring/perf.aspx?reportMode=0 Error Message: The element already exists in the collection. Parameter name: value Stack Trace: at Microsoft.UpdateServices.Administration.WsusCollection.CheckItemIsValid(Int32 index, Object value) at Microsoft.UpdateServices.Administration.WsusCollection.OnInsert(Int32 index, Object value) at System.Collections.CollectionBase.System.Collections.IList.Add(Object value) at Microsoft.UpdateServices.Administration.UpdateSummaryCollection.Add(IUpdateSummary value) at Microsoft.UpdateServices.Internal.BaseApi.UpdateSummary.BuildSummaryCollection(GenericReadableRow[] rows, GroupBy groupBy) at Microsoft.UpdateServices.Internal.BaseApi.ComputerTargetGroup.GetSummaryPerUpdate() at Microsoft.SBS.UpdateServices.DataProvider.GetPendingUpdateCollection() at Microsoft.SBS.UpdateServices.DataProvider.GetPendingUpdateCounts() at Microsoft.SBS.UpdateServices.StatusPage.Utility.GetStatusItems() at usage.frmPerf.PopulateStatusItems() at usage.frmPerf.renderReportWorker() at usage.frmPerf.renderReport() "Susan Bradley" wrote: > gocat2005 wrote: > > Hi Susan > > > > The performance report has now been restored in our environment. Thank you. > > > > We now have an unpatched Exchange Server right? > > > > Please advise. > > > > Regards > > Graham > > > > > > > I'ts "2000" that was declined, not 2003. You have an Exchange 2000 in > your network? > . >
From: Chris Puckett [MSFT] on 16 Apr 2010 10:52 The Exchange 2000 update should not be needed in an SBS 2003 environment unless you have added an additional server to the domain that is running Exchange 2000. With that said, our dear friends in Exchange were kind enough to expire 976703 and re-release it with modified metadata so that this issue would resolve itself after the next WSUS Sync. If you did or did not decline 976703 before, there is no need to take further action after WSUS has synced again. You can wait for the next sync to occur as scheduled or sync manually if you wish. -- Chris Puckett This posting is provided "AS IS" with no warranties, and confers no rights. "gocat2005" <gocat2005(a)discussions.microsoft.com> wrote in message news:A5A31FA4-8961-42B8-A07D-5D3B5DAC5F8B(a)microsoft.com... > Hi Susan > > The version of exchange in SBS2003R2Prem is 6.5.7638.1 which I understand > is > Exchange 2003 SP2. So I guess the offending update does not relate to this > environment. > > However, today in the performance report I got error: > > Server Status Report: > URL: http://localhost/monitoring/perf.aspx?reportMode=0 > > Error Message: The element already exists in the collection. > Parameter name: value > Stack Trace: at > Microsoft.UpdateServices.Administration.WsusCollection.CheckItemIsValid(Int32 > index, Object value) > at Microsoft.UpdateServices.Administration.WsusCollection.OnInsert(Int32 > index, Object value) > at System.Collections.CollectionBase.System.Collections.IList.Add(Object > value) > at > Microsoft.UpdateServices.Administration.UpdateSummaryCollection.Add(IUpdateSummary > value) > at > Microsoft.UpdateServices.Internal.BaseApi.UpdateSummary.BuildSummaryCollection(GenericReadableRow[] > rows, GroupBy groupBy) > at > Microsoft.UpdateServices.Internal.BaseApi.ComputerTargetGroup.GetSummaryPerUpdate() > at Microsoft.SBS.UpdateServices.DataProvider.GetPendingUpdateCollection() > at Microsoft.SBS.UpdateServices.DataProvider.GetPendingUpdateCounts() > at Microsoft.SBS.UpdateServices.StatusPage.Utility.GetStatusItems() > at usage.frmPerf.PopulateStatusItems() > at usage.frmPerf.renderReportWorker() > at usage.frmPerf.renderReport() > > > "Susan Bradley" wrote: > >> gocat2005 wrote: >> > Hi Susan >> > >> > The performance report has now been restored in our environment. Thank >> > you. >> > >> > We now have an unpatched Exchange Server right? >> > >> > Please advise. >> > >> > Regards >> > Graham >> > >> > >> >> >> I'ts "2000" that was declined, not 2003. You have an Exchange 2000 in >> your network? >> . >>
From: gocat2005 on 16 Apr 2010 13:37
Many thanks Regards Graham "Chris Puckett [MSFT]" wrote: > The Exchange 2000 update should not be needed in an SBS 2003 environment > unless you have added an additional server to the domain that is running > Exchange 2000. > > With that said, our dear friends in Exchange were kind enough to expire > 976703 and re-release it with modified metadata so that this issue would > resolve itself after the next WSUS Sync. If you did or did not decline > 976703 before, there is no need to take further action after WSUS has synced > again. You can wait for the next sync to occur as scheduled or sync > manually if you wish. > > -- > Chris Puckett > > This posting is provided "AS IS" with no warranties, and confers no rights. > > > > "gocat2005" <gocat2005(a)discussions.microsoft.com> wrote in message > news:A5A31FA4-8961-42B8-A07D-5D3B5DAC5F8B(a)microsoft.com... > > Hi Susan > > > > The version of exchange in SBS2003R2Prem is 6.5.7638.1 which I understand > > is > > Exchange 2003 SP2. So I guess the offending update does not relate to this > > environment. > > > > However, today in the performance report I got error: > > > > Server Status Report: > > URL: http://localhost/monitoring/perf.aspx?reportMode=0 > > > > Error Message: The element already exists in the collection. > > Parameter name: value > > Stack Trace: at > > Microsoft.UpdateServices.Administration.WsusCollection.CheckItemIsValid(Int32 > > index, Object value) > > at Microsoft.UpdateServices.Administration.WsusCollection.OnInsert(Int32 > > index, Object value) > > at System.Collections.CollectionBase.System.Collections.IList.Add(Object > > value) > > at > > Microsoft.UpdateServices.Administration.UpdateSummaryCollection.Add(IUpdateSummary > > value) > > at > > Microsoft.UpdateServices.Internal.BaseApi.UpdateSummary.BuildSummaryCollection(GenericReadableRow[] > > rows, GroupBy groupBy) > > at > > Microsoft.UpdateServices.Internal.BaseApi.ComputerTargetGroup.GetSummaryPerUpdate() > > at Microsoft.SBS.UpdateServices.DataProvider.GetPendingUpdateCollection() > > at Microsoft.SBS.UpdateServices.DataProvider.GetPendingUpdateCounts() > > at Microsoft.SBS.UpdateServices.StatusPage.Utility.GetStatusItems() > > at usage.frmPerf.PopulateStatusItems() > > at usage.frmPerf.renderReportWorker() > > at usage.frmPerf.renderReport() > > > > > > "Susan Bradley" wrote: > > > >> gocat2005 wrote: > >> > Hi Susan > >> > > >> > The performance report has now been restored in our environment. Thank > >> > you. > >> > > >> > We now have an unpatched Exchange Server right? > >> > > >> > Please advise. > >> > > >> > Regards > >> > Graham > >> > > >> > > >> > >> > >> I'ts "2000" that was declined, not 2003. You have an Exchange 2000 in > >> your network? > >> . > >> > . > |