I am having a terrible time with the PSTs from one user. He has 11 to import, a total of 4 GB. I want to import half with no shortcuts, and the other half with shortcuts. I am using the Scripted method.
I am generating the INI files using a vbscript, so I know they are exactly the same as the ones I used with other users - all successfully.
For the 5 x PSTs that I wish to migrate with NO SHORTCUTS - two complete properly and the other three fail part way through with events 6592 and 6593. The only message is "Abnormal error occurred".
I only tried importing two of the PSTs that I want to import WITH shortcuts. They both also failed with exactly the same events.
And the other thing that happened with those is that the shortcuts got created IN THE PST FILE rather than the mailbox! Why on earth would this happen?? The Shortcut Mode is set to "MAILBOXSHORTCUTS".
This is a very bad thing to happen. I am now going to have to ask for the PSTs to be restored from backup so I can attempt the import again. Why on earth is it modifying the PST files in this way?
It does sound like you had some issues!
Firstly it is normal for the process to create shortcuts
in the pst. What should happen then is these are moved to the mailbox. Of course if you receive abnormal error and this fails you are left with shortcuts in pst. Very annoying.
The only suggestion I can give to try and work out why you receive abnormal error is to dtrace migratorserver and EVPM.
Post it up and will take a look if you want to try and get to the bottom of this.
I searched and searched on that error number and on all sorts of other aspects of the problem and that document did not come up. Actually perhaps I searched on both the error numbers together, but still...
It's too late to try this now as I have manually processed the PSTs, but I will be sure to try it the next time. I'm sure it was stopping on patricular messages as it did successfully archive a lot of the PSTs.
Hi, Can the previous two posters log there own posts with the information. You may receive the same event ID but the cause when broken down could well be different. Also if someone does solve your issue you cannot reward them and mark as solved.