Migrator Server logs error events 13326, 6479, and 6592 many times

Article: 100025243
Last Published: 2021-10-04
Ratings: 1 0
Product(s): Enterprise Vault

Problem

Review of the Enterprise Vault Event Logs return events 13326, 6479, and 6592 about every 10 minutes generating from the task Migrator Server.

Error Message

Event ID:      13326
Task Category: Migrator Server
Description:
Unable to Create Connection <VaultStoreDatabaseName> 
V-437-13326
 
 
Event ID:      6479
Task Category: Migrator Server
Level:         Error
Description:
Error accessing Vault Store database.
 [Internal reference Unable to Create Connection #1      (0xc004340e)]
AFGC1  
V-437-6479
 
 
Event ID:      6592
Task Category: Migrator Server
Level:         Error
Description:
Abnormal error occurred 
V-437-6592 

Cause

This issue is caused when the connection to the Vault Store database is lost.

Solution

To correct this issue the ODBC connection needs to be reconfigured.  Perform the following steps on each server that logs the errors:

  1. Log in as the Vault Service account.
  2. Click Start > Run.
  3. Type the following:

    %systemroot%\SysWOW64\odbcad32.exe

  4. Click OK.
  5. In ODBC Data Source Administrator, click the System DSN tab. 
  6. Click Add.
  7. In the driver list click SQL Server and then click Finish.
  8. For both Name and Description enter the name of the Vault Store database that is shown in error 13326. 
  9. For Server, select the SQL Server that hosts the Vault Store database.
  10. Click Next.
  11. On the authentication page ensure that the following are selected:

    With Windows NT authentication using the network login ID
    Connect to SQL Server to obtain default settings for the additional configuration options
     
  12. Click Next.
  13. Select the checkbox next to Change the default database to and then select the Vault Store database that you entered as the Name in step 8.
  14. Click Next.
  15. Click Finish.
  16. Click Test Data Source to confirm that the connection works.
  17. Click OK to save the new connection.

Note: Repeat this procedure for each vault store connection that is listed in the event log messages.

 

 

References

Etrack : 6592 Etrack : 6479 Etrack : 2375589 Etrack : 13326 Etrack : 2391340

Was this content helpful?