Hello,

I am experiencing next error. It seems the appliation hangs, but never an error shows up. In the logviewer the error below shows up. It seems to be related to the scheduler. What should I do to get rid of it? I have a seperate dedicated server for SQL and for the webserver; so performance shouldn't be a problem.

Can it be that instead of a SQL Workgroup server edition I am currently using a developer edition to have the trace option and that this developer edition is limited in connection pools or something?

Any help appreciated.

J.

AssemblyVersion: 04.05.05
PortalID: 10
PortalName: -
UserID: -1
UserName:
ActiveTabID: 339
ActiveTabName: Tennisshop
RawURL: XX
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: xxx
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: f9b23d61-5dd7-43eb-b897-50bb49214c4e
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.SqlDataReader.ConsumeMetaData()at System.Data.SqlClient.SqlDataReader.get_MetaData()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.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters, SqlConnectionOwnership connectionOwnership)at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters)at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues)at DotNetNuke.Services.Scheduling.DNNScheduling.SqlDataProvider.GetNextScheduledTask(String Server)at DotNetNuke.Services.Scheduling.DNNScheduling.SchedulingController.GetNextScheduledTask(String Server)at DotNetNuke.Services.Scheduling.SchedulingProvider.set_ScheduleLastPolled(DateTime Value)at DotNetNuke.Common.Global.Application_BeginRequest(Object sender, EventArgs e)
Source:
Server Naam: -

I guess that Evotica backup module was scheduled for a child and main portal. I have removed it now and that seemed to be helpful. I also truncated the log. I only have now two entries of  "duplicate" keys. I have the feeling it is from the purge scheduler. I think I switched it off weeks ago because of the duplicate key errors I am receiving now. I will monitor it for some more days. It is however difficult to track down from the event log what schedule caused the error.