Problem
Event ID: 158 generated in the Enterprise Vault Event Log every 10 minutes.
Error Message
Event ID 158 can have several different Description field contents. Each entry begins with either APP AS or APP AT, followed by Customer ID: and the CA or DA Customer ID number. A partial listing of those contents begin as follows:
-- For Event Source: Accelerator Service Processor
- APP AS - Customer ID: -1 - Error in customers synchronising thread. System.Data.SqlClient.SqlException: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection
- APP AS - Customer ID: -1 - Error in customers synchronising thread. System.Data.SqlClient.SqlException: Cannot generate SSPI context.
- APP AT - Customer ID: 2 - Error in customers synchronising thread. System.Data.SqlClient.SqlException: Login failed for user ''. The user is not associated with a trusted SQL Server connection
- APP AT - Customer ID: 2 - Error in customers synchronising thread. System.Data.SqlClient.SqlException: Cannot open database "EVConfiguration" requested by the login. The login failed. Login failed for user domain\user
- APP AT - Customer ID: 2 - Error in customers synchronising thread. System.Data.SqlClient.SqlException: Cannot generate SSPI context.
- APP ATM - Error in customers synchronising thread. System.Data.SqlClient.SqlException: Cannot generate SSPI context.
-- For Event Source: Accelerator Manager (on EV Journaling Server)
- APP JC - Error in customers synchronising thread. System.Data.SqlClient.SqlException: Cannot generate SSPI context.
Cause
When the Enterprise Vault Accelerator Manager Service (EVAMS) starts to allow Enterprise Vault (EV) Compliance Accelerator (CA) or Discovery Accelerator (DA) to process, a communications channel is established between the SQL Server containing the CA or DA databases and the CA or DA server. A similar communications channel is established between the SQL Server and any EV Journal Archiving server that has a CA Journal Connector (JC) installed. When this communications channel is unexpectedly broken, the error above is thrown into the Enterprise Vault Event Log on the EV Journaling, CA or DA server every 10 minutes for each JC or Customer that is currently running.
A partial listing of some common symptoms of this issue is:
- When accessing the EVBAAdmin administrative web site, a permission denied error can occur.
- Any search, export and review process will not complete successfully.
- Scheduled searches will not be started.
- CA Monitored Employees or DA Custodians will not synchronize with Active Directory or the Domino Directory.
This issue is caused by a break in the communications channel between the SQL Server hosting the accelerator databases and the EV Journaling, CA or DA server . Such breaks are typically environmental in nature. A partial listing of causes for the break in the communications channel is
- SQL Server host machine restart
- SQL Server and / or CA or DA server experiencing TCP port exhaustion
- Failure of a network switch or port to which the SQL or CA or DA server is connected
- TCP Chimney, TCP Offload Engine or Receive Side Scaling options being enabled on the SQL and / or CA or DA server operating system or network cards.
Workaround 1
1. Log onto the CA or DA server as the Vault Service Account (VSA)
2. Open the Services application
3. Select the Enterprise Vault Accelerator Manager Service (EVAMS)
4. Restart EVAMS
Workaround 2:
1. Log onto the CA or DA server as the Vault Service Account (VSA)
2. Open the Services application
3. Select the Enterprise Vault Accelerator Manager Service (EVAMS)
4. Open the Properties of EVAMS
5. Click on the Log On tab.
6. Type in the password for the VSA and confirm the password.
7. Click OK.
8. Restart EVAMS
Workaround 3:
1. Log onto the SQL Server as the Vault Service Account (VSA) or an account with the SQL server with the sysadmin role.
2. Open SQL Enterprise Manager for SQL Server 2000, or SQL Management Studio for SQL Server 2005 / 2008 / 2008 R2.
3. Expand the Server > Security > Logins. Double-click the VSA account
4. In the 'Server Roles' section, verify the 'dbcreator' Role is checked. If allowed by the business, also verify the 'sysadmin' role is checked. Click 'OK' to save all changes.
5. In the 'User Mappings' section, verify all of the Accelerator Configuration, Customer and Custodian (if applicable) Databases are checked in the 'Users mapped to this login' sub-section under the 'Map' column. Highlight each mapped Database and verify the 'db_owner' membership is selected in the 'Database role membership for …' sub-section. Click 'OK' to save all changes.
6. Close SQL Enterprise Manager / SQL Management Studio.
7. Log onto the CA or DA server as the VSA.
8. Open the Services application.
9. Select and restart EVAMS.
10. A restart of any or all Journal Tasks may also be required if the EV Journaling Server's EV Event Log has recent (i.e., within the last 10 minutes) Event ID 158 errors.
Solution
Veritas Technologies LLC has acknowledged that the above-mentioned issue is present in the current version(s) listed under the Product(s) Section of this article. Veritas Technologies LLC is committed to product quality and satisfied customers.
There are currently no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. This issue may be resolved in a future major revision of the software at a later time. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns. For information on how to contact Veritas Sales, please see http://www.veritas.com
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.