We’ve developed some resources to help you work effectively from home during COVID-19 Click to learn more

Recycle bin does not get emptied and/or change deleted date in SQL

Hi

I have some issues with the Recycle bin on some installations (both 8.4 Onsite). One installation it does not empty at all after the desired days.

The ejScheduler runs as it should and I'v tried to run the ejCrontab.exe in debug mode, without any errors.

Any suggestion what to do?

One other installation it did work but after some fiddling with the preferences it seems not to work anymore. I have tried to change the preference Retain deleted data to 0 but I wonder if that actually disable the functionallity?.

Then I sat the value to 1 day. But if I wants the records to get permanently deleted faster than 1 day, I tried to change DeletedDate to 2 days earlier in contacts table in SQL. But it seems it does not delete this record at all. It it possible to change this date? Do I have the change somethong else in addition?

(The last try was mostly to reduce the time to wait for the recycle bin to get emptied.)

Any other that has tried to do some changes to the default settings and got it to work?

 

 

 

RE: Recycle bin does not get emptied and/or change deleted date in SQL

And today the recycle bin are emptied on both installations....

I thought the ejScheduler should delete the recycle bin every time it run. But if that's not the case, when are the recycle bin emptied?

Is it once a day at a certain time or what? If so, can the interval bee adjusted somewhere?

Av: Ingar Karlsen 16. feb 2019

RE: Recycle bin does not get emptied and/or change deleted date in SQL

Hard delete happens default every 14 days, or specified by preference "Retain deleted data" (system level preference).
Data is deleted at midnight, in onsite installations triggered by ejScheduler.
Av: Margrethe Romnes 18. feb 2019

RE: Recycle bin does not get emptied and/or change deleted date in SQL

Hello,

If you set the "Retain deleted data" preference to '-1' the data is deleted as soon as the ejscheduler runs the clean up job. If you want to force the ejscheduler to run the cleanup, you can start the eJournalcron with the -force parameter:

ejournalcron.exe -force yourdomain

Look in the ejCrontab.txt file of your CS installation to find out what the domain is if you don't know it.

Note: running the ejournalcron with the -force parameter will also force other jobs like deleting tickets with status deleted etc.

Av: David Hollegien 18. feb 2019