Users are unable to access Network shares after the Enterprise Vault Agent services start on a Windows File Server

book

Article ID: 100028549

calendar_today

Updated On:

Description

Error Message

The following error occurs:

Error: Network Path was not found.

Cause

A possible cause of this issue is that the instance of the Enterprise Vault Filter driver loaded in memory has become unaccessible

Resolution

  1. On the File Server, open a command prompt and run the fltmc command, the output will be similar to the following:
    1. C:\>fltmc
      FLTMC output
      Filter Name Num Instances  Altitude
      FileScreenFilter 2

      260800

      EvFilter 2 185100
      luafv 1 135000
  2. Open the Services.msc panel and stop the following services:
    • Enterprise Vault File Blocking Service
    • Enterprise Vault File Collector Service
    • Enterprise Vault File Placeholder Service
  3. To reload the EvFilter mini driver use the following commands (detailed in the related article 000089589):
    1. Fltmc unload EvFilter
    2. Fltmc load EvFilter
  4. Start the following services:
    • Enterprise Vault File Blocking Service
    • Enterprise Vault File Collector Service
    • Enterprise Vault File Placeholder Service  
  5.  Test the accessibility of the problem volumes
 

 

Issue/Introduction

After the Enterprise Vault (EV) services are started on the file server users can no longer connect to the shared volumes.