Your shared folder is stored in a remote location and it is set in the matter's General tab using Windows Administrative Shares format, i.e. \\HOSTNAME\c$\Shared . You have upgraded Legal Processing from version 3.4 to 3.6 and now observe that LegalReview Indexer actions for existing matters fail in Legal Processing with error "Legal Review Indexer couldn't add documents to index after 10 attempts".
eDiscovery Bundle 3.6 upgrade wizard changes the content of the "ZyLAB.EDiscovery.Indexers.AddToLegalReview.dll.xml" file stored in the Assemblies folder of the existing matters using Windows SYSTEM credentials. This fails when the file is stored in a remote location as SYSTEM account has no access to remote resources.
If you also have matters stored in a local Shared folder, you can use the local copy of the "ZyLAB.EDiscovery.Indexers.AddToLegalReview.dll.xml" to copy to the remote location.
Should no local Shared location be available, you can use the "C:\Program Files (x86)\ZyLAB\EDiscovery\Ediscoveryservice\Assemblies\Performers\ZyLAB.EDiscovery.Indexers.AddToLegalReview.dll.xml" (Default Path) instead, but you need to modify it first.
- Create a copy of the "C:\Program Files (x86)\ZyLAB\EDiscovery\Ediscoveryservice\Assemblies\Performers\ZyLAB.EDiscovery.Indexers.AddToLegalReview.dll.xml" (Default Path) file.
- Modify the copy created in point (1) so that the service is called via HTTP, rather than TCP port 4114. For instance: <setting key="LegalReviewProcessingFacadeUri" value="http://HOSTNAME/EdiscoveryReviewStandalone/ProcessingFacade" />
- Copy the file modified in point (2) in the "Assemblies\Performers\" folder of each matter stored in the remote Shared location.
For the above steps: always make a backup of any file before overwriting it.
Article is closed for comments.