cancel
Showing results for 
Search instead for 
Did you mean: 

PST Migration issue and bizzare problem

Chris_Horswill
Level 4
Hi all,
 
Since upgrading to KVS 7.0 from 6.0 SP 3 we have an issue with importing Plymouth staff PST.s.
 
The error is
"** 12/06/2007 09:20:21 Migration of PST \\KVSBRI01\C$\Leavers_PST_Files\1 To Process\CynthiaBanks.pst exception: Failed to read PST Policy record for Mailbox id: 1C120F251946CD74CBA59B3FE630924761n10000kvssiteply
Error: Unspecified error
Check that this mailbox is in a provisioning group then run the provisioning task **"
 
Our setup is 2 servers in different offices. One, Plymouth, just does the journaling, which works perfectly since the upgrade.
The other, Bristol, performs the mailbox archiving and the importing of PST's.
 
According to a support partner since the upgrade to version 7.0, we are no longer able to have 2 servers performing different tasks in different offices.  Most customers, aparently, have their server(s) in just one office.
Is this true?
 
As for the .pst import error, we have just one provisioning task and just the one provisioning group. We can import .pst's for Bristol and our other office, Southampton, with no problems.
 
Has anyone experienced this issue before? Many thanks for any help.
 
Chris
2 REPLIES 2

Chris_Horswill
Level 4
Just to clear up, our support chaps actually said "no other companies have their EV servers in separate logical sites".
 
Enterprise Vault
                |
                  Directory on KVSBRI01
                                 |
                                    Bristol
                                             |
                                                Enterprise Vault Server
                                 |
                                     Plymouth
                                             |
                                                Enterprise Vault Server
 
 
 

Robert_Guenther
Level 3
Chris,
 
Off the top of my head, this may be a situation where the PST may have been stamped with the wrong header info. This is just a guess.  Can you import the PST using the PST Wizard? if so then most likely the above situation is true. That being the case, I would then try disabling and then renabling the user for Client Driven PST.  You may also want to experiment with turn the "Mark PST" option on and off in conjunction with opening and closing outlook to see if that clears up the situation.
 
Rob