This issue can occur when there are two separate namespaces, internal domain-name and external domain-name. (Example: internal.example.com & external.example.com)
The advantage to this approach is that it provides a unique internal domain name. The disadvantage is that this configuration requires a management of two separate namespaces. Also, using a stand-alone internal domain that is unrelated to an external domain might create confusion for users because the namespaces do not reflect a relationship between resources within and outside of the network. In addition, this may requires two DNS names registration with an Internet name authority to make the internal domain publicly accessible.
As a result, the Accelerator (CA or DA) is unable to contact the Global Address List (GAL) and is unable to populate the list of users. Adding Account information in the Configuration Tab also does not help.
1. Determine the correct Directory DNS Alias. One method is to use the SQL Server Management Studio to browse the ComputerEntry table in the EnterpriseVaultDirectory database and check the ComputerName column for the DNS Alias.
2. Using Internet Explorer logged in to the Accelerator server as the Vault Service Account (VSA), open the EVBAAdmin administration web page on the server by browsing to https://localhost/evbaadmin.
3. Right click on the Accelerator Customer in question and click on Properties.
4. Add the DNS alias found in Step 1 to the Directory DNS Aliases and click on OK.
5. Restart the Enterprise Vault Accelerator Manager Service (EVAMS).