Event 8390, 13360 - Collation conflicts in the SQL database prevent the execution of stored procedures - 0x80040e14

  • Modified Date:
  • Article ID:000087856


Collation conflicts in the SQL database will prevent the execution of stored procedures.
    - The Netbackup (NBU) Agent for EV cannot place an Index location in backup mode causing a backup failure
    - Archving Task generates in event viewer

Error Message

Event ID: 8390
Hex Code: 0x80040e14
Event Category: Migrator Server
Event Description: The EnterpriseVault.DirectoryService object reported an error. The error code was 0x80040e14 CDirectoryConnectionObject::UpdateIndexLocationBackUpMode

Event ID: 13360
Event Category: Directory Service
An error was detected while accessing the Vault Database
There are mulitple examples of the secondary description:
- Description: The [Root] table is inconsistent for VaultEntryId [Vault Entry ID]
- Description: Cannot resolve the collation conflict between ""Latin1_General_CI_AS"" and ""SQL_Latin1_General_CP1_CI_AS"" in the equal to operation.

SQL Command:
- GetObjectSecurity
- uspu_UpdateIndexLocationBackupMode
Number: 0x80040e14
SQL State: 42000
Native Error: 00050000

The below example was documented as the Netbackup Agent for EV fails to place an EV Index Location backup mode.


To validate if this is the issue a DTRACE is needed, please perform the following steps on the EV server that has generated the applicable events.

  • For more information about Symantec Enterprise Vault’s DTRACE Utility please see HOWTO57893
  • DTRACE the process DirectoryService for no less than 5 minutes while re-creating the issue. 
  • Open the log file created and search for either of the following the strings:

(DirectoryService) <1712> EV~E Event ID: 13360 An error was detected while accessing the Vault Database 'EnterpriseVaultDirectory' (Internal reference: CADODataAccess::ExecuteSQLCommand .\ADODataAccess.cpp [lines {1407,1409,1424,1442}], built Mar 14 10:54:54 2011): |Description: |Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.| | |SQL Command: | uspu_UpdateIndexLocationBackupMode| | |Additional Microsoft supplied information:| |Source: Microsoft OLE DB Provider for SQL Server |Number: 0x80040e14 |SQL State: 42000 |Native Error: 00000468 |HRESULT|0x80040e14| | 
EV:H CADODataAccess::ExecuteSQLCommand - HRXEX fn trace : Error 0x80040e14 ref[1]: ESC12, .\ADODataAccess.cpp [lines {1407,1409,1424,1442}]


Here is a sample of bpresolver:
DebugLog(): INF - CEVBridgeHelper::ModifyEVEntityBackupModeByEntityID - EVBridge Instance FAILED to update the entity (107E19EB354E4FE499D0F49BB0CAB55E51810000 host.generic.com) of Site (1C77431CF6C7DB04297DD10647A1707491d10000 host.generic.com). Error: For the Archiving Option, an error occurred with the Enterprise Vault Directory API. Check the Enterprise Vault event log in the Windows Event Viewer for details.!! 
DebugLog(): INF - ModifyBackupModeStatus - Backup Mode request failed to PUSH for entity (EV-SIT::\\EV\EV Site (SIT (generic))\Index Locations\107E19EB354E4FE499D0F49BB0CAB55E51810000 host.generic.com/Path (// host.generic.com /I$/Indexing)).
DebugLog(): ERR - bedsEnterpriseVaultQuiesceComponent(): Call to ModifyBackupModeStatus failed with (-536832766).



This can occur if a SQL database is moved or upgraded and the default collation on the two instances are not the same.


Run Deployment Scanner and ensure the collation is uniform across all databases:
    1. Collecting an EV deployment scanner TECH58232
    2. If SQL Collation issues are identified in the results follow TECH55063.
    3. Once the issues have been corrected the NBU agent can be run again.

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)