SP3 Upgrade - Database update issues

[Lakshmi_Narayan]

Hi,

We are having issues with SP3 upgrade.

We have got 2 servers which archive Exchange mail, and SQL 2005 in the back-end

Upgradation of fist server was smooth, but second one giving issues in updating the vaul store to new version. Previously Directory update completed smoothly n first server

Here are the errors getting with this

----------------------------------------------
Event Type: Error
Event Source: Enterprise Vault
Event Category: Storage Server
Event ID: 13360
Date:  12/12/2009
Time:  19:42:53
User:  N/A
Computer: ARCH02
Description:
An error was detected while accessing the Vault Database '' (Internal reference: .\ADODataAccess.cpp (CADODataAccess::ExecuteSQLCommand) [lines {1390,1392,1407,1444}] built Nov  2 19:40:47 2009):

Description: 

[Microsoft][ODBC SQL Server Driver][SQL Server]Database 'EnterpriseVaultDirectory' cannot be opened. It is in the middle of a restore.
 
 ------------------------------------------

Event Type: Error
Event Source: Enterprise Vault
Event Category: Storage Server
Event ID: 6875
Date:  12/12/2009
Time:  19:51:32
User:  N/A
Computer: ARCH02
Description:
An error occurred attempting to update Storage database
Reason: <0x80040e14>
Reference: UVSDBs/uvsdb
 
Script File: C:\Program Files\Enterprise Vault\VaultStoreDB_8_Programmability.sql
Vault Store: MAILVAULTSTORE
Vault Store Id: 1E1B0AA8DE19CFF4FAAB5B88AC4DBA09B1210000EV1
Database Name: EVVSIXEMAILVAULTSTORE_3
DSN: EVVSIXEMAILVAULTSTORE_3
-----------------------------------------

I have checked the SQL system DSN and its fine.

Would be great if if any one could help me ASAP on this.

Thanks
Narayana

[Michael_Bilsbor]

Hi,

i would google the error about "it is in the middle of a restore"
EV is just returning the message given to it by SQL so I would research why SQL is doing that.

[Wayne_Humphrey · Accepted solution]

Hi Lakshmi,

Please see this:
http://seer.entsupport.symantec.com/docs/229542.htm

The solution is:

• If all transaction logs have not been restored yet, restore them in order, without checking Recovery in the Restore option except for the last log.
• If the database and all transaction logs have been restored, then the only possibility is to use Microsoft SQL Query Analyzer, and run the following script :

use master

RESTORE DATABASE <DATABASE_NAME> WITH RECOVERY

(For more information on Microsoft SQL Query Analyzer, please refer to Microsoft Technical Support).

[Lakshmi_Narayan]

Thanks for the response.

The database which had this issue was the Active/Master, and restoring Database(Log shiped one) was on a different server.

i tried disabling the Log shipping DB and problem wasnt stil solved. Hence, made the restoring DB as the master and updated the Vault Store DB to new location. That solved the issue.

But i am still not sure why this issue occurred.

Thanks
Narayana