After modifying the Protect.properties by enabling the incident externalization and setting the externalization directory the Enforce server reports Error 1758 after restarting the services.
Note that incidents will also have YSOD and RSOD while viewing them.
DLP 14.0 and above
Error code 1758 Incident attachment external storage directory is not accessible.
Message: Directory setting is invalid.
Message: Throwable while persisting incident.
The value used for the com.symantec.dlp.incident.blob.externalization.dir setting in the SymantecDLP\Protect\config\Protect.properties file contained back slashes. for exampe:
com.symantec.dlp.incident.blob.externalization.dir = E:\DLPstorage
Convert the backslashes to forward slashes.
com.symantec.dlp.incident.blob.externalization.dir = E:/DLPstorage
If the destination is remote then try the following:
For example, if the remote path is \\<server>\<share>\<directory> try the following settings
If the fully qualified name does not work then try converting it to an IP address.
Note that the protect user needs to be able to access the remote location. See the DLP Maintenance guide for details.
Workaround for Remote Storage
In some cases, a backslash may be unavoidable, for example when accessing a DFS share. In this case, you can use a symbolic link instead of specifying the network path.
To do this in windows use the following command:
mklink /D E:\DLP_Attachments \\<server>\<share>\<directory>
Then in the Protect.properties specify
com.symantec.dlp.incident.blob.externalization.dir = E:/DLP_Attachments
For more information on external incident storage see the DLP Maintenance guide
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
This will clear the history and restart the chat.