Funky Monitoring reports? Try this

Thu, Jul 31 2008 21:08 bradley

http://msmvps.com/blogs/bradley/archive/2008/07/25/how-many-of-you-have-sbs-monitoring-reports-that-as-of-lately-have-gotten-a-little-funky.aspx

For all of those folks that have had "funky" monitoring reports since about mid July on your R2 boxes, I want you to try on a box or two the following test:

Subject: monitoring reports not working?

7/30/2008 7:18 AM PST

By:		Les Connor [SBS MVP]	In:		microsoft.public.windows.server.sbs

If you're on WSUS v3, try running the server cleanup wizard from within 
'options' in the WSUS console. Only tick the first box (deselect the rest, 
for now), and be warned, this could take 24 hours (or more) to complete so 
just let it go.

See if the monitoring report works after the cleanup. You can also select 
the other boxes on a subsequent run of the cleanup wizard.

-- 
Les Connor [SBS MVP]
________________________
Get the SBS BPA here:
http://support.microsoft.com/kb/940439/en-us

Filed under: SBS 2003 r2

# re: Funky Monitoring reports? Try this

Friday, August 01, 2008 2:49 AM by SRW

Any suggestions for boxes still on WSUS 2.0? Not sure if upgrading to 3.0 is a good idea at this point since there are already "issues".....

# re: Funky Monitoring reports? Try this

Friday, August 08, 2008 1:57 PM by Gary Hottman

Tried running server cleanup wizard as suggested with only first box selected but the performance still fails and the event log gets the same error

Server Status Report:

URL: localhost/.../perf.aspx

Error Message: Thread was being aborted.

Stack Trace: at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)

at System.Data.SqlClient.SqlCommand.ExecuteReader()

at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteReader()

at Microsoft.UpdateServices.Internal.SingleResultSetSPHandler.ExecuteStoredProcedure(DBConnection connection)

at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String spName, DBParameterCollection args, IExecuteSPHandler handler, Int32 queryTimeoutInSeconds)

at Microsoft.UpdateServices.Internal.DataAccess.ExecuteSPSingleResultSet(String spName, DBParameterCollection args, Type resultType, Int32 queryTimeoutInSeconds)

at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPGetTargetGroupById(Guid id)

at Microsoft.UpdateServices.Internal.BaseApi.ComputerTargetGroup.GetById(Guid id)

at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetComputerTargetGroup(Guid id)

at Microsoft.SBS.UpdateServices.DataProvider.IsUpdateApprovedToInstallInGroup(IUpdate update, Guid ComputerGroupId)

at Microsoft.SBS.UpdateServices.DataProvider.IsUpdateInstallationCompleted(IUpdate update)

at Microsoft.SBS.UpdateServices.DataProvider.GetScheduledUpdates()

at Microsoft.SBS.UpdateServices.StatusPage.Utility.GetStatusItems()

at usage.frmPerf.PopulateStatusItems()

at usage.frmPerf.renderReportWorker()

at usage.frmPerf.renderReport()

For more information, see Help and Support Center at

# re: Funky Monitoring reports? Try this

Friday, August 08, 2008 2:06 PM by bradley

Start at the bottom and do one at a time.

# re: Funky Monitoring reports? Try this

Friday, August 08, 2008 2:44 PM by Gary Hottman

Ran the server cleanup wizard one item at a time starting from the bottom on two servers and both servers performance report still fails: The event log Server Status Report error has difference contents:

Server Status Report:

URL: localhost/.../perf.aspx

Error Message: Thread was being aborted.

Stack Trace: at System.Data.Common.Dbnetlib.ConnectionRead(HandleRef pConnectionObject, Byte[] buffer, UInt16 readmin, UInt16 readmax, UInt16 timeout, IntPtr& errno)

at System.Data.SqlClient.TdsParser.ReadNetlib(Int32 bytesExpected)

at System.Data.SqlClient.TdsParser.ReadBuffer()

at System.Data.SqlClient.TdsParser.ReadByte()

at System.Data.SqlClient.TdsParser.Run(RunBehavior run, SqlCommand cmdHandler, SqlDataReader dataStream)

at System.Data.SqlClient.SqlInternalConnection.ExecuteTransaction(String sqlBatch, String method)

at System.Data.SqlClient.SqlConnection.ExecuteTransaction(String sqlBatch, String method)

at System.Data.SqlClient.SqlTransaction.Commit()

at Microsoft.UpdateServices.DatabaseAccess.DBConnection.CommitTransaction()

at Microsoft.UpdateServices.DatabaseAccess.DBConnection.CommitTransaction(String transactionName)

at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String spName, DBParameterCollection args, IExecuteSPHandler handler, Int32 queryTimeoutInSeconds)

at Microsoft.UpdateServices.Internal.DataAccess.ExecuteSPSingleResultSet(String spName, DBParameterCollection args, Type resultType, Int32 queryTimeoutInSeconds)

at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPGetTargetGroupSummariesForUpdate(Guid updateId)

at Microsoft.UpdateServices.Internal.BaseApi.Update.GetSummaryPerComputerTargetGroup()

at Microsoft.SBS.UpdateServices.DataProvider.IsUpdateInstallationCompleted(IUpdate update)

at Microsoft.SBS.UpdateServices.DataProvider.GetScheduledUpdates()

at Microsoft.SBS.UpdateServices.StatusPage.Utility.GetStatusItems()

at usage.frmPerf.PopulateStatusItems()

at usage.frmPerf.renderReportWorker()

at usage.frmPerf.renderReport()

2nd system

Server Status Report:

URL: localhost/.../perf.aspx

Error Message: Thread was being aborted.

Stack Trace: at Microsoft.Win32.RegistryKey.Dispose(Boolean disposing)

at Microsoft.Win32.RegistryKey.Close()

at Microsoft.UpdateServices.Internal.MachineSettingRedirector.DisposeHelper(Boolean disposing)

at Microsoft.UpdateServices.Internal.MachineSettingRedirector.Dispose()

at Microsoft.UpdateServices.Internal.DatabaseConfiguration.Load()

at Microsoft.UpdateServices.Internal.DatabaseConfiguration..ctor()

at Microsoft.UpdateServices.Internal.ClassFactory.CreateWellKnownType(Type type, Object[] args)

at Microsoft.UpdateServices.Internal.ClassFactory.CreateInstance(Type type, Object[] args)

at Microsoft.UpdateServices.DatabaseAccess.DBConnection.InitMembers()

at Microsoft.UpdateServices.DatabaseAccess.DBConnection..ctor()