Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Classifying Content > Manually deleting fingerprinting classifiers
Manually deleting fingerprinting classifiers
Administrator Help | Forcepoint DLP | Version 8.5.x
If the crawler is unresponsive for any reason when administrators delete a fingerprinting classifier from the management server, the crawler is not alerted that the classifier has been deleted. When the crawler becomes responsive, it continues to run the fingerprinting scan as scheduled and consume unnecessary resources.
To avoid these repercussions, manually delete the classifier from its associated crawler.
The Forcepoint Security Manager displays a warning in this situation, and asks if you want to continue. If so, manually delete the classifier as follows:
1.
*
The classifier Fingerprint_Name ID 8e76b07c-e8e5-43b7-b991-9fc2e8da8793 was deleted from the management server, but not from the crawler, Crawler_Name 10.201.33.1.
*
*
%DSS_HOME% is the Forcepoint DLP installation folder.
*
For example, the first line of one file might show:
<job type="fingerprinting" id="3178b4f9-96fe-4554-ad1d-eaa29fa23374" name="ora3" altID="168476">
If the task was named "ora3", the ID is 3178b4f9-96fe-4554-ad1d-eaa29fa23374.
2.
a.
%DSS_HOME% is the Forcepoint DLP installation folder.
b.
Python WorkSchedulerWebServiceClient.pyc -o deleteJob -j #jobId#
Here, jobID is the ID number identified in step 1.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Classifying Content > Manually deleting fingerprinting classifiers
Copyright 2017 Forcepoint. All rights reserved.