In an attempt to clear out any currently running jobs, you have run the options in the clean up tool and recycled services. However, once the services restart, some tasks, like ADProcessor and ADIndexer, may also restart automatically.
Step 1: Use the Recycle Services Script to Stop all services. Once all services are stopped, go to step 2. Do NOT press 1 to continue the script at this point.
Step 2: Launch the Clean up tool and choose the options "Clear Reindex", "Clear Bulk Print", "Fail Active Jobs", "Fail All Productions", and "Not Processing All Cases". Close the clean up tool.
Step 3: Delete the contents of the PEstate (PM) and ADTemp folders manually while all services are stopped during the recycle services script.
These are the possible default locations:
- PM: C:\ProgramData\AccessData\PM
- PEState: C:\Users\<service account>\AppData\Local\Temp\PEState
- ADTemp: C:\Users\<service account>\AppData\Local\Temp\adtemp
In addition to these three locations, there may be a designated location for these as well. You will need to verify in the Registry where those locations are if you are not sure. **Note: If these locations don't list either ADTemp or PEState, or say either (default) (value not set), then there is nothing for you to delete in these locations**
- ADTemp: HKEY_LOCAL_MACHINE\SOFTWARE\AccessData\Products\Common.
PEState: HKEY_LOCAL_MACHINE\SOFTWARE\AccessData\Products\Evidence Processing Engine\10.x
Delete the contents of all five folders if they exist.
NOTE: In an environment utilizing additional distributed processing engines (DPE's), you will need to check these locations on the primary application server as well as all DPE servers.
Step 4: Press 1 to continue the Recycle Service Script
In some instances, the temporary files and processing status contained within these locations can trigger a job to restart despite the job being canceled by the clean up tool.