There are no errors.
Running a Dtrace of the FSAReportingService process on the file server will show the following entry:
LoadConfigThread The FSA Reporting Web server sent an empty configuration
The server name that the FSA Agent on the file server sends to the Enterprise Vault (EV) Server does not match the corresponding record in the EV Database.
In the Dtrace of the FSAReportingService from the file server, there will be a line with the following information:
{Client.GetConfigurationInformation} GetConfigurationInformation : domainName = domain.local,serverName = fileservername,version = X.0.0.0
Combining the fileservername and the domainName will render the FQDN as it is reported to the EV Server.
This issue is based on the DNS configuration of the environment.
Because there can be many reasons why the File Server FSA Agent is reporting a different FQDN than the value stored in the EV Database FileServerEntry table, it is difficult to list all possible causes. Below are some basic examples of causes to look for.
1. Run Ping -a on the EV Server targeting the IP Address of the File Server. This should return the FQDN of the file server as reported by DNS.
a. If the FQDN for the file server is returned, but is different than what the Dtrace from the file server shows, then DNS changes will need to be made. A hosts file entry can be made for the file server, using the FQDN from Dtrace.
b. Alternatively, the file server record stored in the EV Database in the FileServerEntry table can be manually modified to match the correct DNS resolution. For more information on how to update the corresponding record in the EV Database, review the instructions from the document shown in the Related articles section below.