File System Archiving (FSA) Reporting Scans do not start when an Enterprise Vault Server is used as the FSA Reporting Proxy Server
Article ID: 100026560
Updated On:
Description
Error Message
A Dtrace of the FSAReportingService process on the FSA Reporting Proxy EV server shows that this process is unable to determine the computer name for the server it is running on:
(FSAReportingService) <4624> EV:L CFSAReporting::GetEVServerAliasName FQDN is EVSERVER1
(FSAReportingService) <4624> EV:L CFSAReporting::GetEVServerAliasName EVServer Alias is
(FSAReportingService) <4624> EV:L CFSAReporting::GetEVServerAliasName function leaving with result:1
(FSAReportingService) <4624> EV-M {CLIENT.EN_US} GetConfigurationInformation : domainName = testdomain.local,serverName = ,version = 10.0.0.1316
The entries below will also be logged in Dtrace:
(FSAReportingService) <4780> EV:L CFSAReporting::get_Servers method called |
(FSAReportingService) <4780> EV:H CFSAReporting::get_Servers .The server collection is empty. Returning false
Note: This can also appear on a Windows file server target when attempting to start a scan.
Resolution
To resolve this problem the ComputerName value in the EnterpriseVaultDirectory database for the Enterprise Vault server needs to be modified to be Fully Qualified. i.e. in the example above the ComputerName value should be changed from EVSERVER1 to EVSERVER1.testdomain.local. If there are multiple EV servers in the site then these should also be similarly updated in order to maintain a common standard in the site.
In addition, the ProxyServerName value within the FSAReportingProxyServers table in the EnterpriseVaultDirectory database should be adjusted so that it is Fully Qualified as well.
Once these database changes have been made, a restart of the Enterprise Vault Admin Service on the FSA Reporting Proxy EV server should be done for the changes to take effect.
Issue/Introduction
