Has anyone got any idea what could be causing this error to be repeatedly coming up in the event log?

AssemblyVersion: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: Collection index must be in the range 1 to the size of the collection.
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message: System.IndexOutOfRangeException: Collection index must be in the range 1 to the size of the collection. at Microsoft.VisualBasic.Collection.IndexCheck(Int32 Index) at Microsoft.VisualBasic.Collection.get_Item(Int32 Index) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.ScheduleQueueContains(ScheduleItem objScheduleItem) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.AddToScheduleQueue(ScheduleHistoryItem objScheduleHistoryItem) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.LoadQueueFromTimer() at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.Start()
Source:
Server Name: SWINDON

I also seem to be getting this one quite frequently as well

AssemblyVersion: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4)
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message: System.ApplicationException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4) at System.Threading.ReaderWriterLock.AcquireReaderLockInternal(Int32 millisecondsTimeout) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.get_ScheduleInProgress()
Source:
Server Name: SWINDON

I have removed the ScheduleHistory records every 2 or 3 days now for about a week.  The table reaches 1000 records in a few days.  It seems like fixing the symptom is not the answer.  Is the reason for these errors known? 

Paul

Hi all,

I have the same problem and the enabled scheduler jobs are:

 DotNetNuke.Entities.Users.PurgeUsersOnline, DOTNETNUKE   Every 1 Minute  Every 5 Minutes
  DotNetNuke.Services.Log.SiteLog.PurgeSiteLog, DOTNETNUKE   Every 1 Day  Every 2 Hours
  DotNetNuke.Services.Scheduling.PurgeScheduleHistory, DOTNETNUKE   Every 1 Day  Every 2 Days 
  DotNetNuke.Services.Log.EventLog.PurgeLogBuffer, DOTNETNUKE   Every 1 Minute  Every 5 Minutes 
  DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE   Every 30 Minutes  Every 60 Minutes 
  DotNetNuke.Modules.Events.EventNotification, DotNetNuke.Modules.Events   Every 1 Hour  Every 30 Minutes

any suggestions?

Thanks in advance, Costas