Hi,

I am getting alot of log erros indicating a Scheduler is trying to insert a duplicate key (as below):

AssemblyVersion: -1
Method:
FileName:
FileLineNumber: -1
FileColumnNumber: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
AbsoluteURL:
AbsoluteURLReferrer:
ExceptionGUID:
DefaultDataProvider:
InnerException: Add failed. Duplicate key value supplied.
Message: System.ArgumentException: Add failed. Duplicate key value supplied. at Microsoft.VisualBasic.Collection.Add(Object Item, String Key, Object Before, Object After) at DotNetNuke.Services.Scheduling.DNNScheduling.CoreScheduler.AddToScheduleInProgress(ScheduleHistoryItem objScheduleHistoryItem) at DotNetNuke.Services.Scheduling.DNNScheduling.CoreScheduler.WorkStarted(SchedulerClient& objSchedulerClient)
StackTrace:
Source:
Server Name: DEDI383

This is followed by many Module load exceptions a general (timeout) execeptions.  I have also seen some SQL Deadlocked process (Kill Thread) exceptions after these scheduling exceptions also.

Here is the puzzling part.  I am just having this problem on one DNN installation, the second installation is running fine.  I upgraded both installations to DNN 3.2.2 this week.

Which leads me to believe I have some duplicate or erroneous records in one of my schedule tables.  Can I delete all the records in schedule or schedule history tables and then will(??) the system repopulate the tables with new schedule records and restart from scratch?

If I set each schedule item to "Retain History" of "None" will this achieve the same end?

Are these soln. I am asking about not even suggested for the error msg above?

Any help is greatly appreciated.

thanks,

J. Reirdon