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:

I've only not included the server identifier in the above, everything else is as it came.  DNN was installed from a special applications as part of a Hosting Package, so I'm really not sure what the problem is.  To top it all off, it's only the third install I've done of DNN and the first one was wiped because KHZ was afraid that I'd try to steal his code

Thanks.  The History Purge was not turned on.  As I said I'm new to this.  Also the Max Threads forthe Scheduler is 1 and I've got two events (Forum Email Queue Task, And UsersOnline Purge Users) that are set for the same schedule (Every Minute)  It's a small site, but I want it to stay up to date.  So I changed the scheduls around, and set the purgeScheduleHistry Task to on.  I'll let you know if anything else crops up. 

One other question though, how do I make the Max Threads larger, or can I.  I do have Super User Account, so I think I should be able to, but I'm not sure.