Unexpected migration status 'HasPstChunkMigrated'
I'm trying to use client driver PST migration to get a list of all PST files on client workstations. I want to do this without migrating any data as I need to use the information provided by the client to forecast how much storage will be required for the whole organisation. Migration will happen at a later date.
Everything for client and server driven PST migrations has been configured but I have deliberately left the PST Migrator Task running with the schedule set to Never Run. A quick test was done with a handful of user mailbox archives enabled for Client Driven Migration. Their PST's were listed in Personal Store Management and everything was sweet.
I then enable all remaining mailbox archives for client driven migration. Now I'm getting thousands of Error 8567 in the event log as shown below:
Event ID: 8567
Source: Enterprise Vault
Category: Directory Service
Description:
Error occurred with client-driven migration of PST '\\computername\C$\folder\nameofpst.pst'.
Unexpected migration status.
Reference: 'HasPstChunkMigrated'.
Each event is for a different PST file and there are multiple being logged every second. Eventually the following happens:
"There have been more than 10000 Errors in the last 7200 seconds, of which 90% or more are from Enterprise Vault.
Enterprise Vault will now shut down."
Vital Stats are Windows 2003 STD Server SP2, EV 7.0 SP1, Mostly Outlook 2003 SP3 with EV Client 7.0.1.2005.0.dcom
Please no comment on the EV version unless there is a documented fix directly related.... not my choice.
Any suggestions on what is going on here? is it just normal because the migrator task isn't even running? any suggestion on how to resolve would be appreciated.
Cheers
Comments
Helpful
Helpful ???
http://support.veritas.com/docs/319148
Hi Rob, Not exactly the same
Hi Rob,
Not exactly the same error I'm experiencing. Also, the article relates to the PST chuncks getting out of sync between the client and the server. This is not the case for me as I'm not running the Migrator task yet so there are no PST chunks in the PST Holding Folder.
Other suggestions?
FYI I ran the query in
FYI I ran the query in article 319148 and found that there were no records with a Filespecification of 'PST In Error'.
Looking more closely at the event log it looks like it maybe the same files with constantly reoccuring errors. I have identified at least 60+ PST files that have each been reported in the event viewer hundreds or thousands of times. Just how many are listed however I can't be sure as there are thousands of errors to go through in the event log.
In despiration I've
In despiration I've disabled client driven migration on all mailbox archives and changed the status of the 16000 PST files to 'Do Not Migrate'. Doing that reduced the number of PST files generating the error in the event log however I still had 10 PST's constantly reporting the same error still. In an attempt to stop these from erroring I deleted the PST files from the Personal Store Management\Files and the error promptly changed to :
Event ID: 8567
Source: Enterprise Vault
Category: Directory Service
Description:
Error occurred with client-driven migration of PST '\\computername\C$\folder\nameofpst.pst'.
PST record not found.
Reference: 'HasPstChunkMigrated'.
Any suggestion how to fix this? I think these 10 PST's are probably the first ones in line to be migrated?
http://news.support.veritas.c
http://news.support.veritas.com/connect/forums/enterprise-vault-will-now-shut-down
Tried this but no change... help anyone?
Answer
We'll after much stuffing around and support calls to Symantec we seem to have some answers.
To stop the "PST record not found" errors being logged in the EV servers event logs a restart of the offending outlook client was required.
To stop the "Unexpected migration status", the PST file had to be remvoed from the VAC and the offending outlook client restarted.
The root cause appears to be that the share permissions on the PST Holding Folder were set to everyone read. Changing this to everyone full control immediately resulted in the EV clients writing their chunks to the server. The resolution does not explain why only some clients generated the errors in the severs event log while the vast majority were perfectly fine but so far no more errors have occured.
Would you like to reply?
Login or Register to post your comment.