Trying to export a user that has left the company. By opening the VAC, right-clicking on Archives and selecting Export. At first it would just sit there not using any cpu cycles so rebooted KVS Server. After doing this the export fails with the following useful(!) description:
Export of archive USERNAME failed. Reason: Unspecified error encountered during export operation. Please check the event log
No errors whatsoever in the Event Log.
Checked permissions on mailbox and vault - all looks to be okay.
Next: Tried exporting my own vault to pst using my logon, same result.
So here I am with over 100 users requiring archiving and an extremely helpful KVS error!
First time I've done a dtrace, so hope I've got it right. I have seen that there was a problem (search for EV~E PST file access error occurred) But I can't see a reason why, the account has access to the folder.
Anyhoo, here's the output:
Monitor Trace Output
Running in Terminal Services session... Monitoring debug output from processes running in the console session Another process is monitoring debug output from processes running in the current Terminal Services session
Ctrl-C to quit
1 15:42:37.028 (MigratorServer) <3624> EV~I Storage trace enabled. Detail level is: 1 Process Id is: 5916 Module is: C:\Program Files\Enterprise Vault\MigratorServer.exe 2 15:42:37.059 (MigratorServer) <3624> EV~I Migrator Server started 3 15:42:37.075 (MigratorServer) <3624> EV~I CIndirectProcessSetMember::Register Registered - Rep. No: 1 4 15:42:37.075 (MigratorServer) <3624> EV~I CIndirectProcessSetMember::ConfirmRunning State: 2 Result: TRUE 5 15:42:37.090 (DirectoryService) <4608> EV~I DirectoryService: Method call: AmIALocalAdmi nistrator() 6 15:42:37.371 (MigratorServer) <4648> EV~I CIndirectProcessSetMember::GetRegistrationStat e State: 1 7 15:42:37.371 (MigratorServer) <4648> EV~I CExporter::GetUserAccount Process Token User: *KVSADMINACCOUNT* SID Type: User 8 15:42:37.386 (MigratorServer) <4648> EV~I CExporter::GetUserAccount Privileges: SeTcbPrivilege, SeDebugPrivilege, SeChangeNotifyPrivilege, SeSecurityPrivilege , SeBackupPrivilege, SeRestorePrivilege, SeSystemtimePrivilege, SeShutdownPrivilege, SeRemot eShutdownPrivilege, SeTakeOwnershipPrivilege, SeSystemEnvironmentPrivilege, SeSystemProfilePri vilege, SeProfileSingleProcessPrivilege, SeIncreaseBasePriorityPrivilege, SeLoadDriverPrivileg e, SeCreatePagefilePrivilege, SeIncreaseQuotaPrivilege, SeUndockPrivilege, SeManageVolumePri vilege, SeImpersonatePrivilege, SeCreateGlobalPrivilege 9 15:42:37.635 (MigratorServer) <4648> EV~I Storage trace enabled. Detail level is: 1 Process Id is: 5916 Module is: C:\Program Files\Enterprise Vault\MigratorServer.exe 10 15:42:37.651 (MigratorServer) <4648> EV~I Storage trace enabled. Detail level is: 1 Process Id is: 5916 Module is: C:\Program Files\Enterprise Vault\MigratorServer.exe 11 15:42:38.835 (MigratorServer) <4648> EV~E PST file access error occurred
I've tried both, all items and then reducing to 4 months (we used to archive 3months and older). I'm beginning to think our installation of V5 is so bugged that I'm going to scrub it and go with V6 - It's a case of which is the lesser of two evils, spending time & resources (of which I have very little) getting V5 running or bite the bullet and install V6. If anybody has any advice, it would be appreciated. Also have the option of migrating off a NAS and onto a SAN and building a new KVS server onto a blade.
The only other thing I can think of is disable the mbx for archiving and Exmerging to a .pst.