Hi Leupold,

today, point blank, my scheduler went crazy and started throwing errors. CPU activity was constantly 100%, my log viewer was full of red status lines generated by portal -1 that had to do with the scheduler. Some of them were mentioning the KeepAlive.aspx page others the Default.aspx page, other no page at all.

I'm running version 05.06.00 (459) with SQL Server 2005. The SQL machine has 8 GB of free memory and when my CPU was up 100% i still had approximately 6 Gigabytes of free RAM.

I read your post and disabled the scheduler. Now everything works as usual again.

My quesiton is: what happens in the long run if I keep the scheduler disabled? Is it safe to run my DNN installation with the scheduler disabled? How does disabling the scheduler affect my installation?

How could I solve the scheduler problem? Any clues as to why this suddenly happened?

Thank you in advance

Edoardo

 Hello Leupold, how exactly to I go about determining which jobs I don't need?

I'm not exactly sure how to determine which scheduled tasks are necessary and which ones I can do without.

By the way Looking into the ScheduleHistory table in my DNN installation I get this error message:

Schedule history purge failed.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. (SqlException exception, Boolean breakConnection)     at System.Data.SqlClient.SqlInternalConnection. (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 DotNetNuke.Services.Scheduling.DNNScheduling.SqlDataProvider.PurgeScheduleHistory()     at DotNetNuke.Services.Scheduling.DNNScheduling.DNNScheduler.PurgeScheduleHistory()     at DotNetNuke.Services.Scheduling.PurgeScheduleHistory.DoWork() 

I can't figure out what, which task or which module is causing this problem.

Any Ideas as how to go about things? Do you suggest I reactivate one scheduler item at a time a see which one catastrophically affects my server?

Thank you for your suggestions.

Edoardo