We are getting the following errors every time the Bring2mind.DNN.Modules.DMX.Services.Schedule.Maintenance runs. If I look in the schedule history, it is failing after 30 seconds every time.

I have tried increasing the connect timeout in the SQL connection string and also the application pool pinging but without success.

DNN: 5.6.2
DMX: 5.3.7
Windows 2008 R2 web and SQL express 2008 R2

7/11/2011 1:16:24 PM Scheduler Event Failure
THREAD ID: 3; TYPE: Bring2mind.DNN.Modules.DMX.Services. ...
THREAD ID: 3
TYPE: Bring2mind.DNN.Modules.DMX.Services.Schedule.Maintenance
EXCEPTION: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
RESCHEDULED FOR: 2011/07/11 03:15:53 PM
SOURCE: STARTED_FROM_BEGIN_REQUEST
ACTIVE THREADS: 0
FREE THREADS: 1
READER TIMEOUTS: 0
WRITER TIMEOUTS: 0
IN PROGRESS: 0
IN QUEUE: 7
Server Name: AGS02

7/11/2011 1:16:24 PM Scheduler Exception AssemblyVersion: 5.6.2; PortalID: -1; PortalName ...
AssemblyVersion: 5.6.2
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: ff0879dd-754a-4b94-a51f-81cde56404d4
InnerException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Data.SqlClient.SqlConnection.OnError
StackTrace:
Message: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. 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.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, String spName, Object[] parameterValues) at Bring2mind.DNN.Modules.DMX.Data.SqlDataProvider.ResetFolderSizes(Int32 PortalId) at Bring2mind.DNN.Modules.DMX.Services.Schedule.Maintenance.DoWork()
Source:
Server Name: AGS02

So the SPROC ResetFolderSizes times out in SQL. What you can try is to run it manually directly in SQL Mgt Studio to get an idea of how long this takes to run.

Note this bit is meant as "maintenance". I.e. the module will work correctly without it. This bit of code just checks if the folder size displayed on screen actually corresponds to the size of the documents underneath it. It refreshes that every time the maintenance task runs.

Peter

Thanks Peter, it is taking 34 seconds to execute. Do you know of a way to increase the timeout for the schedule?

The timeout is actually determined by the connection to SQL server. Check out MS's documentation on that. It is not governed by DMX or DNN specifically but I believe in the connection string or default settings on the server.

Peter