Summation Clean up tool

Created by: Tod Ewasko
Created date:
Last Updated date:



  • Clear Reindex - Delete all reindex jobs from the work list. Older versions that created many work orders for reindex jobs cause the work manager console
  • Clear Bulk Print - Deletes all bulk print jobs from the work manager and marks them failed in the cases.
  • Fail Active Jobs - This marks any job on the system in the worklist or the work manager as failed. Requires Recycling of Services.
  • Fail All Productions - Marking all productions failed.
  • Not Processing All Cases - Forces the case into a Not Processing state and clears out the workflow40. Requires Recycling of Services.
  • Unlock All Users - This will mark all users that are currently locked out as not locked out.
  • OCR to Best Practice - Not Implemented yet
  • Enable AD Viewer - This will default the processing setting to default to the Standard Viewer for all cases.
  • Disable AD Viewer - This will default the processing setting to default to the Alternative Viewer for all cases.
  • Disable Tag Indexing - This will mark all cases processing setting as "Disable Tag Indexing".
  • Remove Dup Status - This will remove the duplicate status from load file imports. Note: When you add another piece of evidence this will need to be run again to remove the status. Works on all cases.

Regarding Failed Evidence jobs please review this help article about using FTK to remove the failed evidence: FTK Remove Evidence

Restarting the services after making these changes are recommended.

The "Fail All Productions" and "Not Processing All Cases" command buttons can help if you see the following error when attempting to delete a production or export set.

Error: Cannot delete production sets while jobs are running.

Was this article helpful?
3 out of 3 found this helpful
Have more questions? Submit a request


  • Avatar

    Is this compatible with all version 5.2.2 and up? (ADG59 schema ? )

  • Avatar
    Tod Ewasko

    This is database schema agnostic so the schema doesn't matter. Let us know if you have any trouble.

  • Avatar
    Yian Sun

    For the Setting Change options, is there a way to do it just for specific cases?

  • Avatar
    Jacob H. Harder

    We have a 4-server setup. Which server should this application be installed on? Thanks

  • Avatar
    Tod Ewasko

    Yian - sorry didn't see this earlier. These are all or none options we can lead you to areas where this change is made if you open a ticket.

    Jacob - The location does not matter the user you log into windows does. As this assumes windows authentication when communicating with the SQL Database and with the Case Data folder. So as long as your user has sufficient rights and can reach those two locations it can be installed on any machine. Traditionally we see it installed on the application server because some of the changes require a service restart.

Powered by Zendesk