Skip to main content

Troubleshooting Proxy Service

The following are potential errors that may occur during installation and how to resolve each.

Error MessageResolution
Service ‘Access Analyzer FSAA Proxy Scanner’ (StealthAUDITFSAA) failed to start. Verify that you have sufficient privileges to start system services.The domain account used during setup doesn't have sufficient privileges to start the service. Open Local Security Policies on the proxy server. In User Rights Assignment under Local policies, add the user to the Log on as a service policy. After the user has this privilege, retry the installation.

The following are potential errors that may occur during File System scans and how to resolve each.

Error MessageResolution
Failed to launch SDD client (2): The system can't find the file specified.This indicates the Sensitive Data Discovery Add-On isn't installed on the proxy server.
Error creating DLP components. Error:Error initializing DLP communications, received invalid pipe handle.This indicates the Sensitive Data Discovery Add-On isn't installed on the proxy server.
Unable to start scan: Couldn't initialize scan session with any proxy host suppliedThis can indicate a few things and is a broad error:
  • The Access Analyzer Console can't reach the proxy server via the network.
  • Network communications are blocked for TCP on port 8766 – possibly by the Windows Firewall on the Access Analyzer Console server or proxy server, or by another firewall in the network (you can customize this port through the FSAA Data Collector query configuration).
  • The Netwrix Access Analyzer (formerly Enterprise Auditor) FSAA Proxy Scanner service isn't running or isn't installed on the target proxy server.

Verbose Logging​

Enable verbose logging to troubleshoot a problem with the proxy server.

Run the following command in the directory where the installer lives (to prompt the install):

msiexec /i FileSystemProxy.msi /l*v install.log

Run the following command in the directory where the installer lives (to prompt the removal):

msiexec /x FileSystemProxy.msi /l*v install.log