New Post: cart Cleanup schedule

Hi,

That file is in the source.

Odd this....just today I've been working on a test system (Not NB_Store) and I found a scheduler job in the job history that seems to be running for days??...and doing nothing!!!

Even after restarting the app, the job still looked like it was running in the background. yet, when I run the same jobs again, in the history both run and then the one I started after finishes...but the other continues to run.

I think this is a DNN issue, when a process gets lost somewhere it stays in the DB history and appears if it's still running.

Here's what I did to removed the job in question.

CAREFULL BECAUSE I DID THIS ON A TEST SYSTEM...I'VE NOT SEEN THE ISSUE ON A LIVE ONE!!

First find out what scheduler id is ...

/****** Script for SelectTopNRows command from SSMS ******/
SELECT TOP 1000 [ScheduleID]

  ,[TypeFullName]
  ,[TimeLapse]
  ,[TimeLapseMeasurement]
  ,[RetryTimeLapse]
  ,[RetryTimeLapseMeasurement]
  ,[RetainHistoryNum]
  ,[AttachToEvent]
  ,[CatchUpEnabled]
  ,[Enabled]
  ,[ObjectDependencies]
  ,[Servers]
  ,[CreatedByUserID]
  ,[CreatedOnDate]
  ,[LastModifiedByUserID]
  ,[LastModifiedOnDate]
  ,[FriendlyName]

FROM [dbo].[Schedule]


next find the process in the history...

/****** Script for SelectTopNRows command from SSMS ******/
SELECT TOP 1000 [ScheduleHistoryID]

  ,[ScheduleID]
  ,[StartDate]
  ,[EndDate]
  ,[Succeeded]
  ,[LogNotes]
  ,[NextStart]
  ,[Server]

FROM [dbo].[ScheduleHistory]
where ScheduleID = ###


then delete it from the history table...

delete FROM [dbo].[ScheduleHistory]
where ScheduleHistoryID = #####


Like I said I've only done this on a test system...maybe there is a clearer way to do it with the DNN interface???


It's odd how this has happened..in my case I think it was due to a restore of a live system from a backup that had the job running when I did the backup. hence on the restore I think DNN thought it was still running.....but that is a guess!!!!

I'm now testing my test system to see if the phantom job comes back!

Regards,
Dave.