Follow

AccessData Service Impact

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

AccessData Service Impact

Description: The purpose of this document is to empower customers with the ability perform initial troubleshoot. Having internal resources perform restarting of services when a certain area has been deemed the problem based on the below information will allow for more reliable up time. Below is a listing of services and a summary of what they handle. Allowing you to restart services needed to get back up and running if an event occurred that caused a service to become unresponsive.

 

FTK Business Services (aka AccessData Business Services Common)

There are many functions in the software that use FTK business. This service facilitates the communication to the ADG and Case databases in SQL Server (or Postgres). The Case databases store any user generated information (coding, redactions, labels) and document meta data. The ADG database stores information about the defaults, case listing, work orders, permissions and many other global settings. This service also is responsible for the file streams from the file system to the end users system (Native Viewer, Image Viewer, Text Viewer) If this service is in need of a restart, restarting all the services is recommended. RTT Business Service is dependent on this service.

Service Impact: High - Users will experience down time if this service is restarted.

eDiscovery Business Services

The eDisco service is similar to the FTK service above being that it communicates with the database however the database used here are the Application Databases (eDiscovery). This database stores Job information for agents and collections. If this service is in need of a restart, restarting all the services is recommended.

Service Impact: High - Users will experience down time if this service is restarted.

Infrastructure Services

The infrastructure service communicates with the infrastructure database and holds a few system level settings; this database is being merged into the ADG database. This service manages AD authentication and KFF Service. This service can be restarted without resetting all the services.

Service Impact: Low – Restarting will have minimal impact on users.

License Services

The License service depends on the CodeMeter service which pulls license from the dongle. This service tracks work managers that have a license and which work managers have a site server installed.

Service Impact: Medium – Restarting will have impact on job or evidence loads starting, minimal user impact.

Asynchronous Processing Services

The Asynchronous Processing Services performs many of the bulk actions performed by users. Some of the actions that use this service Search, Audit Logging, Bulk Label and Bulk Code. This service exists in Microsoft Internet Information Service and uses Private MSMQ Queues for queuing.

Service Impact: High – Restarting (using iisreset command) will have high user impact, suggested to have 15 minute down time while this service comes back up.

Orchestration Services

The Orchestration Service is a liaison of job creation and completion. This service is responsible for ending services or processes. This service communicates with Work Distribution service. This service communicates primarily with the following databases Workflow40 and ADG. Restarting the Work Distribution service after this service starts is recommended.

Service Impact: Medium – Restarting this service will have impact on job or evidence loads starting, minimal user impact.

RTT Business Services

The Real Tim Transcript Business Service is built for a feature called Real Time Transcripts. This feature communicates with the serial port to take in transcripts from a stenographer device.

Service Impact: Low – Restarting this service will only affect the ability to use Real Time Transcript Feature, no user impact.

Work Distribution Services

The Work Distribution Service interacts with work managers and handles queuing of jobs for the work manager.

Service Impact: Medium – Restarting this service will have an impact on work being placed into the queue for work manager to pick up, minimal user impact.

Work Manager

The Work Manager Service handles the actual execution of jobs, i.e. processing evidence or collecting data.

Service Impact: Medium – Restarting this service will have an impact on currently processing work, minimal user impact.

Distributed Processing Engine (if applicable)

The Distributed Processing Engine runs as service and performs most of the work order tasks for jobs. This service will spawn ADIndexer and ADProcessor among others located in the Evidence Processing folder.

Service Impact: Low – Restarting this will only affect the currently running job, after restart is complete the job will pick back up; this will have no impact on users.

Distributed Processing Manager (if applicable)

The Distributed Processing Manager runs as service and manages DPEs. This service pushes work to the Distributed Processing Engine.

Service Impact: Low – Restarting this will only affect the currently running job, after restart is complete the job will pick back up; this will have no impact on users. AccessData Recommends to removing evidence if this was ended during processing.

KFF Server Service (if applicable)

The Known File Format Server Service facilitates management of the KFF libraries.

Service Impact: Low – Restarting this will only affect your ability to use KFF on processed jobs.

Non-Service related executables

ProcessingHost.exe

ProcessingHost is called by the Work Manager locally installed. This executable will spawn ADIndexer and ADProcessor among others located in the Evidence Processing folder.

Impact: Low – Ending this process will only affect the currently running job, current running jobs will not complete; this will have no impact on users. AccessData Recommends to removing evidence if this was ended during processing.

ADIndexer.exe

ADIndexer this executable performs the indexing for processing and reindex actions.

Impact: Low – Ending this process will stop current indexing but will be re-spawned to complete, no job loss expected; this will have no impact on users.

ADProcessor.exe

ADProcessor this executable performs the enumeration among other tasks.

Impact: Low – Ending this process will stop current processing and will not re-spawn, job loss is expected; this will have no impact on users. AccessData Recommends to removing evidence if this was ended during processing.

 

 

 

 

 

 

 

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

Comments

Powered by Zendesk