Morgoth
16 years agoLevel 4
Errors after upgrade from V2007 to V2008
Hello all,
i have recenty upgraded Enterprise Vault 2007 SP4 to EV 2008.
After that i have problems archiving mails.
Here is what is happening:
- The archiving job runs normally but the items remain in the "Enterprise Vault storage archive" under MSQM
- After i restart the storage service (after backup), EV archives about 100 items and removes them from the "Enterprise Vault storage archive" queue, and after that it stops removing items from the queue and reports the following errors:
An exception has been raised.
Internal reference
.\ADODataAccess.cpp (CADODataAccess::ExecuteSQLCommand) [lines {1379,1381,1396,1414}] built Mar 25 13:23:31 2009
and
A COM exception has been raised.
An exception was detected in '' while accessing the Vault Database ''. [0xc004341f]
Internal reference
.\VaultStoreDB.cpp (CVaultStoreDB::AddSaveset) [lines {...,2871,2872,2873,2874,2875,2876,2877,2878,2879,2880,2881,2884}] built Mar 25 14:48:10 2009
After each restart of the Storage Service same thing happens and the items which are archived (removed from the queue) are functional and accessible.
Any ideas?
Regards,
Kresimir
i have recenty upgraded Enterprise Vault 2007 SP4 to EV 2008.
After that i have problems archiving mails.
Here is what is happening:
- The archiving job runs normally but the items remain in the "Enterprise Vault storage archive" under MSQM
- After i restart the storage service (after backup), EV archives about 100 items and removes them from the "Enterprise Vault storage archive" queue, and after that it stops removing items from the queue and reports the following errors:
An exception has been raised.
Internal reference
.\ADODataAccess.cpp (CADODataAccess::ExecuteSQLCommand) [lines {1379,1381,1396,1414}] built Mar 25 13:23:31 2009
and
A COM exception has been raised.
An exception was detected in '' while accessing the Vault Database ''. [0xc004341f]
Internal reference
.\VaultStoreDB.cpp (CVaultStoreDB::AddSaveset) [lines {...,2871,2872,2873,2874,2875,2876,2877,2878,2879,2880,2881,2884}] built Mar 25 14:48:10 2009
After each restart of the Storage Service same thing happens and the items which are archived (removed from the queue) are functional and accessible.
Any ideas?
Regards,
Kresimir