cancel
Showing results for 
Search instead for 
Did you mean: 

enterprise vault service unavailable

cemileba_ak
Level 3
Partner Accredited

Hi;

We just move our EV databases to the new SQL server. We able to see archived mailes via icons on Outlook. But on search .asp we took the enterprise vault service unavailable error. and also on the event view we see this log.

An error was detected while accessing the Vault Database 'EnterpriseVaultDirectory' (Internal reference: {CADODataAccess::OpenRecordset} [.\ADODataAccess.cpp, lines {2650,2652,2653,2656,2659,2663}, built Jul 10 17:51:36 2013]):

Description:

Invalid object name '#rootidentities'.


SQL Command:
GetObjectsBySIDs


Additional Microsoft supplied information:

Source: Microsoft OLE DB Provider for SQL Server
Number: 0x80040e37
SQL State: 42S02
Native Error: 00000208
HRESULT 0x80040e37

Can you please help us urgently.

1 ACCEPTED SOLUTION

Accepted Solutions

cemileba_ak
Level 3
Partner Accredited

The cause of the problem is sql server collation.

The SQL server default collation must be same with EV sql collations.

 

Thanks for all.

 

Regards

View solution in original post

4 REPLIES 4

Rob_Wilcox1
Level 6
Partner

Do you get the service unavailable message as soon as you click on Search within Outlook?

What happens if you try to open an archived item from within Outlook?

 

Which version and service pack of EV are you referring to here?

Working for cloudficient.com

EdLacey
Level 5
Certified

Did you follow all the required steps when you moved databases?

https://www-secure.symantec.com/connect/videos/how-move-enterprise-vault-sql-databases-another-sql-s...

 

 

GabeV
Level 6
Employee Accredited

What version of Enterprise Vault are you running? Doing a quick search about that error message, I couldn't find a reference to #rootidentities in that SQL command, that error might not be related to the behavior in the search.asp .... Did you move the DBs from one SQL server to another or did you restore the DB's from backup? You might need to open a case with support to troubleshoot this issue further.

cemileba_ak
Level 3
Partner Accredited

The cause of the problem is sql server collation.

The SQL server default collation must be same with EV sql collations.

 

Thanks for all.

 

Regards