Event ID 13360 after moving SQL databases with named instances

Article: 100019891
Last Published: 2015-01-07
Ratings: 0 0
Product(s): Enterprise Vault

Problem

Event ID 13360 after moving Enterprise Vault SQL databases from one SQL server to another SQL server with named instances.

Error Message

Event: 13360
Category: Directory Service
Description: An error was detected while accessing the Vault Database 'TMP_MASTER_TMP_FOR_536708329' (Internal reference: CC1):
Description: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Invalid Instance()).

SQL Command: N/A

Additional Microsoft supplied information:
Source: Microsoft OLE DB Provider for ODBC Drivers
Number: 0x80004005
SQL State: 01000
Native Error: 00000014
HRESULT 0xc0043433
V-437-13360

 

When attempting to Test ODBC connections of EV System DSN's we receive the following:
Connection failed:
SQL State: '01000'
SQL Server Error: 14
[Microsoft][ODBC SQL_Server Driver][DBNETLIB] ConnectionOpen (Invalid Instance())
Connection failed:
SQL State:'08001'
SQL Server Error: 14
[Microsoft][ODBC SQL_Server Driver][DBNETLIB]Invalid Connection

Cause

The preceding can occur when the SQL Server is using a named instance.

Solution

To resolve this issue modify the following registry key:
 
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.


HKEY_LOCAL_MACHINE\Software\KVS\Enterprise Vault\Directory\Directory Service\SQLServer Name
Modify the SQLServer Name Key to reflect  SQL Server Name\Named  Instance.


If the error relates to a specific database then confirm that the SQL Server values are correct under the Vault Store properties / database tab in the Admin Console and also that the EnterpriseVaultDirectory Database tables below contain the correct Server and Instance names:
 
FingerprintCatalogueDatabase
FingerprintCatalogueInstance
VaultStoreEntry
 

 

Was this content helpful?