Error Message

Event ID: 40966
Task Category: Compliance Sampler
Level: Error
Description:
A program fault has raised an exception.
Exception: Multiple default Customers have been defined.
Diagnostic:
Type: System.ApplicationException
Reference:
Command Line: "C:\Program Files (x86)\Enterprise Vault\EVCompliance.exe" -URL:tcp://A.B.C.D:E/e1b94b3e_5813_44d2_b2f7_0872af9fcea3/KVS.EnterpriseVault.ProcessManager60504909
Application Domain: EVCompliance.exe
Process Id: 123
Thread Id: 456
Stack Trace:
    at Symantec.EnterpriseVault.Compliance.ArchiveToCustomerMap.AdddefaultCustomer(CustomerData customerData)
    at Symantec.EnterpriseVault.Compliance.ArchiveToCustomerMap..ctor(IEnumerable`1 customers)
    at Symantec.EnterpriseVault.Compliance.SystemData.EvaluateArchiveToCustomers()
    at Symantec.EnterpriseVault.Compliance.CAConfigManager.set_SystemData(SystemData value)
    at Symantec.EnterpriseVault.Compliance.ConfigReader.ReadAllConfig()
    at Symantec.EnterpriseVault.Compliance.ConfigReader.BackgroundThread()

Event ID: 41577
Task Category: Compliance Sampler
Level: Error
Description:
Compliance Accelerator sampling has been misconfigured.
Multiple default Compliance Accelerator customers have been defined in the configuration database(s).
Only one default customer should be configured to ensure items are correctly sampled to the correct customer instance.
Compliance customers '' and '' have both been configured as the default customer instance.
Please correct this configuration issue in the Accelerator Manager website.
Enterprise Vault will stop the Storage service to ensure that no items are precluded from sampling.

Event ID: 41578
Task Category: Compliance Sampler
Level: Error
Description:
Compliance Accelerator sampling has been misconfigured.
The same Enterprise Vault Archive has been configured to be sampled to multiple Compliance Accelerator customer instances.
Each Enterprise Vault Archive can only be sampled to a single customer instance.
Compliance customers '' and '' have both been configured to sample from Archive '12345ABCDE12345ABCDE12345ABCDE12345ABCDE110000ExchangeJournal01.EV.local'.
Please correct this configuration issue in the Accelerator Manager website.
Enterprise Vault will stop the Storage service to ensure that no items are precluded from sampling.

Solution 1 - Set the 'VaultID(s)' field for all but one of the default Customers to a unique fictitious value

This solution is feasible if the existing default Customers do not contain any Departments or Monitored Employees. In other words, the default Customers are truly inactive. This can be accomplished by editing the default Customer's properties in the EVBAAdmin website, as follows:

• Access the EVBAAdmin website using the Vault Service Account's credentials. This page can usually be accessed on the CA server by browsing to https://localhost/EVBAAdmin .
• Right-click on the default Customer | Properties.
• In the default Customer's Properties page, add a unique fictitious entry (without spaces) to the 'VaultID(s)' field. An example would be: DoNotUse01
• Click OK to save the changes.
• Restart the EV Storage Service(s).

Repeat these steps for all default Customers except one, being sure to use a unique fictitious value (without spaces) for the VaultID, such as DoNotUse02 , DoNotUse03 , etc. There must be one default Customer present in one Configuration database; there must not be one default Customer present in each Configuration database.

Solution 2 - Configure all but one of the default Customers to target required Archives

This solution is feasible if the default Customers have been configured with Departments and Monitored Employees. The procedure to target Archives is to add the target Archives' respective Archive IDs from the Archives' Properties page in the Vault Administration Console to the 'VaultID(s)' field for the Customer (as above). It would be best if the Default Customer that has the least, or no, amount of configuration (Departments, Monitored Employees, etc.) is selected to remain as the default Customer. There must be one default Customer present in one Configuration database; there must not be one default Customer present in each Configuration database.

Note: An Archive can only be targeted by one Customer in an EV Site. For example, if CACustomer01 associated to CAConfiguration01 targets Journal Archive 'ExchangeJournal01' via its Archive ID, CACustomer02 associated to CAConfiguration02 cannot concurrently target 'ExchangeJournal01.'

Note:

EV and CA 14.1.0 and greater do not allow new customers to be created with a blank 'VaultID(s)' field when another customer already exists with the field blank.

 

In CA version 11.0.0, and earlier, the tagging process to apply Department Tags to messages that are based on Monitored Employee Department membership was performed by the Journal Connector (JC) which read the Customers' Department and Monitored Employee information from each Customer database.

The Journal Connector pointed to one Configuration database, configured during the Journal Connector installation. As such, each CA Configuration database must have contained one Customer with no Archives targeted, i.e.: with the 'VaultID(s)' field being blank. This Customer was known as the default Customer, also referred to as the catch-all Customer, and targeted all applicable Archives that were not targeted by any other Customers. One, and only one, default Customer could exist per CA Configuration database. The Journal Connector tracked CA Customers per Configuration database, therefore requiring each Configuration database to contain one default Customer.

In CA version 11.0.1, and higher, the Tagging process to apply Department Tags to messages based on Monitored Employee Department membership has been incorporated into the updated Storage Service, and the usage of the Journal Connector has been discontinued. As a part of incorporating the Tagging process into the Storage Service, Customers across multiple Configuration databases are now tracked by the Storage Service. As the requirement for having only one default Customer still exists, having two, or more, CA Servers -- each with their own Configuration databases, and default Customers -- will cause the errors above, and will shut down the Storage Service until the miss-configuration can be rectified.

A DTrace on the EV Storage Server of the EVCompliance and StorageServer processes will show entries similar to the following:

As only one default Customer can exist amongst all Customers across all Configuration databases in CA 11.0.1, and higher within an EV Site, all but one of the default Customers must be reconfigured. 

Select the most appropriate solution as described below:

The Enterprise Vault (EV) Storage Service stops with errors advising that multiple default customers have been defined. This condition occurs when Compliance Accelerator (CA) has been installed and configured on two, or more, CA servers, with each CA server having its own configuration database, and its own default customer database, at a minimum. There could be one, or more, customer databases targeting specific archives that are configured in each CA Configuration database, but this is not a requirement to generate the errors.

UMI: V-437-40966 UMI: V-437-41577 UMI: V-437-41578