Prev: Anybody seen this error before in SBS 2008? "Archived Email S
Next: 066157 M3i Zero , Ezflash Dsi , R4i Dsi 25458
From: PC Dom on 7 Sep 2009 22:41
Hi,

Some weeks ago I noticed disk thrashing happening at a specific
interval on an SBS 2008 server.

I found it was the SBSMonitoring instance of SQL thrashing with it's
database which had magically grown to 2.4GBs.

I noticed that the bulk of the data was in the Events table, on a
specific day, hundreds of thousands of a repeated event with hundred
of them every second.

I found the cleanup sql script on the MS blog that sets the expire
interval to 30 days (from 90) and re-indexes all the entires and ran
it, the database was reduced to a couple hundred MB.

However I was also monitoring DataServiceComponents.log, which had a
few timeout errors in it that I was expected to be fixed with the
reduced database size. It fixed the timeout error (or it resolved
itself):

Microsoft.WindowsServerSolutions.SystemHealth.Monitoring.MonitoringSQLDataStore.ProcessAlertsPerComputer
(String computerName)

However unfortunately the error below is still occurring every 30
minutes:

An exception of type 'Type: System.Data.SqlClient.SqlException,
System.Data, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089' has occurred.
Timestamp: 09/07/2009 08:13:46
Message: Timeout expired. The timeout period elapsed prior to
completion of the operation or the server is not responding.
Stack: at System.Data.SqlClient.SqlConnection.OnError(SqlException
exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning
(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
SqlCommand cmdHandler, SqlDataReader dataStream,
BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject
stateObj)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader
(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds
(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean
returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader
(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean
returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery
(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at
Microsoft.WindowsServerSolutions.SystemHealth.Monitoring.MonitoringSQLDataStore.WriteEventLogResultsToStore
(ItemsDictionary`1 eventLogItems)

Anyone have any information?

Thanks!

Dom
From: Russ Grover [SBS-MVP] on 8 Sep 2009 01:48
Try Taming the SQL the Memory usage with
Microsoft SQL Server Management Studio Express

Russ

--
Russell Grover - SBITS.Biz [SBS-MVP]
Microsoft Gold Certified Partner
Microsoft Certified Small Business Specialist
World Wide 24hr SBS Remote Support - http://www.SBITS.Biz
Microsoft Online Services - http://www.microsoft-online-services.com/



"PC Dom" <lifers(a)gmail.com> wrote in message
news:ec60777f-5c8e-4f11-9401-dd40cbe98b31(a)v37g2000prg.googlegroups.com...
> Hi,
>
> Some weeks ago I noticed disk thrashing happening at a specific
> interval on an SBS 2008 server.
>
> I found it was the SBSMonitoring instance of SQL thrashing with it's
> database which had magically grown to 2.4GBs.
>
> I noticed that the bulk of the data was in the Events table, on a
> specific day, hundreds of thousands of a repeated event with hundred
> of them every second.
>
> I found the cleanup sql script on the MS blog that sets the expire
> interval to 30 days (from 90) and re-indexes all the entires and ran
> it, the database was reduced to a couple hundred MB.
>
> However I was also monitoring DataServiceComponents.log, which had a
> few timeout errors in it that I was expected to be fixed with the
> reduced database size. It fixed the timeout error (or it resolved
> itself):
>
> Microsoft.WindowsServerSolutions.SystemHealth.Monitoring.MonitoringSQLDataStore.ProcessAlertsPerComputer
> (String computerName)
>
> However unfortunately the error below is still occurring every 30
> minutes:
>
> An exception of type 'Type: System.Data.SqlClient.SqlException,
> System.Data, Version=2.0.0.0, Culture=neutral,
> PublicKeyToken=b77a5c561934e089' has occurred.
> Timestamp: 09/07/2009 08:13:46
> Message: Timeout expired. The timeout period elapsed prior to
> completion of the operation or the server is not responding.
> Stack: at System.Data.SqlClient.SqlConnection.OnError(SqlException
> exception, Boolean breakConnection)
> at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning
> (TdsParserStateObject stateObj)
> at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
> SqlCommand cmdHandler, SqlDataReader dataStream,
> BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject
> stateObj)
> at System.Data.SqlClient.SqlCommand.FinishExecuteReader
> (SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
> at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds
> (CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean
> returnStream, Boolean async)
> at System.Data.SqlClient.SqlCommand.RunExecuteReader
> (CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean
> returnStream, String method, DbAsyncResult result)
> at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery
> (DbAsyncResult result, String methodName, Boolean sendToPipe)
> at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
> at
> Microsoft.WindowsServerSolutions.SystemHealth.Monitoring.MonitoringSQLDataStore.WriteEventLogResultsToStore
> (ItemsDictionary`1 eventLogItems)
>
> Anyone have any information?
>
> Thanks!
>
> Dom

From: PC Dom on 8 Sep 2009 21:50
On Sep 8, 3:48 pm, "Russ Grover [SBS-MVP]"
<supp...(a)REMOVETHIS.sbits.biz> wrote:
> Try Taming the SQL the Memory usage with
> Microsoft SQL Server Management Studio Express
>
> Russ

Done that. I haven't monitored it so closely since expiring the 2.5GB
of records, but I'm not worried about the RAM/Disk/CPU use now, just
the error, and changing memory (except for increasing it) is unlikely
to fix the sql error.

Dom
 | 
Pages: 1
Prev: Anybody seen this error before in SBS 2008? "Archived Email S
Next: 066157 M3i Zero , Ezflash Dsi , R4i Dsi 25458