Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Remove ghost databases

Created: 30 Jul 2013 • Updated: 29 Dec 2013 | 3 comments
Baron164's picture
This issue has been solved. See solution.

I have an Enterprise Vault system that is trying to connect to two non-existant databases. Looks like someone created a store and then the store was only partially removed. I keep getting Event ID's 13395 The connection 'Provider=SQLOLEDB;Server=EV02\EV;Database=EVVSExpressVaultStore_2;Trusted_Connection=yes' was lost and the system failed to reconnect (Thread Id: 5952) I tried just deleting the store group that is associated with this particaly database but it's stick in Marked for deletion.

Operating Systems:

Comments 3 CommentsJump to latest comment

TonySterling's picture

So you may have to manually remove those from SQL. To be safe i would recommend opening a call with support.  You don't really want to muck around with SQL without guidance.

GabeV's picture

I agree with Tony. You might need to manipulate the directory database to clean some information regarding the Vault Store Group or Vault Store databases from the system. Please, open a ticket with support.

“Success is not final, failure is not fatal: it is the courage to continue that counts.”–Winston Churchill

EV_Ajay's picture


This issue may occur if a database within SQL server has become unstable.  Cycling the Microsoft SQL services may resolve this issue.

As per Tony is better to open case with Symantec.