Enterprise Vault™ Troubleshooting FSA Reporting
- About this document
- Troubleshooting an upgrade of FSA Reporting
- Troubleshooting the configuration of FSA Reporting
- Troubleshooting issues with FSA Reporting reports
- Using DTrace to troubleshoot FSA Reporting
Recreating the File Collector service if it is missing
Note that this problem and solution apply only to the following Enterprise Vault releases:
Enterprise Vault 9.0.3, and later versions of Enterprise Vault 9.0.
Enterprise Vault 10.0.1, and later versions of Enterprise Vault 10.0.
Problem: On a server on which the FSA Agent is installed, the Enterprise Vault File Collector service is missing from the list of services displayed by the Windows Services snap-in. The Enterprise Vault File Placeholder service and the Enterprise Vault File Blocking service are both present, as expected.
Cause: The Enterprise Vault File Collector service has been deleted from the server in error.
Resolution: You can run the fsareportingservice command to recreate the File Collector service. When you use the command as described, it removes any remaining components of the existing File Collector service. It then installs the File Collector service and configures the service to run under the specified account. You must specify the credentials of the Vault Service account.
To recreate the File Collector service if it is missing
- Open a command prompt window on the server on which the service is missing.
- Navigate to the Enterprise Vault installation folder, for example
C:\Program Files (x86)\Enterprise Vault.
- Run the following command:
fsareportingservice /user domaim_name\user_name /pwd password /service
domain_name is the domain name for the Vault Service account.
user_name is the user name of the Vault Service account.
password is the password of the Vault Service account.
fsareportingservice /user demo\vaultadmin /pwd 193xy$dq /service
- Use the Services snap-in to confirm that the Enterprise Vault File Collector service is now reinstated.