With regard PortalId -1. This means that the problem is at the Host level, not the individual portal level. The schedule is a host level function, therefore PortalId = -1. You need to look at the rest of the error to get a clue.

I'll see if I can do some digging.

Roger

Hi Roger

Thank you very much for that. Greatly appreciated and the problem is now 'disabled'.

There was a problem with at least one of the schedule items... 'DotNetNuke.Services.Scheduling.PurgeScheduleHistory'

It says:

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.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.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, CommandType commandType, String commandText) 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()

Has happened on occassions, although usually working... it seems to do this every few days.  Any ideas of what in the database might need editing?

I have kept all Schedule history etc... is it worth keeping it though until the problem is resolved?  Also, the schedule items that are running successfuly each time, I take it these could be enabled again?

Thanks again.

David

Thanks Roger

Used the SQL Server Managment Studio Express... easier for me as I didn't realise it was dbo.identifierschedule...  Was 4307 items there so I have removed most of them.

Just getting all Site Log info too into a spreadsheet as I find it a useful way to analyse the use of the site... then deleting it all too.

The site is still low use really... as we are only just starting to get going now (hence my concern) but as you mention... it is not worth keeping in the database info if it can only slow the site down.

Cheers

David