Hi Please try to use MFCMAPI to remove any weird folders or duplicates. http://www.microsoft.com/en-us/download/details.aspx?id=2953 hope it helps CheersZi Feng TechNet Community Support

Hi Please try to use MFCMAPI to remove any weird folders or duplicates. http://www.microsoft.com/en-us/download/details.aspx?id=2953 hope it helps Cheers That download link is no longer accurate, so I downloaded here. The documentation tab on that site doesn't appear to have anything useful. Could you give me a hint on what I might be looking for and/or how to look for it? For instance, do I need to do this on the computer of the user in question in order to try to correct the live Exchange data, or do I need to connect to the PST that won't import? Additionally, if it is a "weird folder" would it be something like a / in a folder name? In that case, could I just rename folders accordingly in the PSTs?

I spoke with the user and he did see a lot of folder name anomalies (and some folders he couldn't delete until he renamed them). Additionally, he has already manually imported one of the PSTs and intends to do the same with the other. Since he had made so many changes, hopefully removing most anomalies, we tried the import again, but it still quickly failed. Since he was already planning to manually import it, I won't be troubleshooting this further. Since there were some anomalies, I will mark Zi Feng's post as answer.

I am importing PST files using New-MailBoxImportRequest in Exchange 2013, and I am consistently getting the following from two specific PSTs: FailureCode : -2146233088 FailureType : JobIsPoisonedPermananentException FailureSide : Message : Error: Job is poisoned, poison count = 6. There were actually three PSTs that returned this error, but one of them imported fine when I retried. The other two fail so consistently that it seems like a user mailbox issue and not a PST issue (although this isn't 100% definitive). I came to that conclusion after the following discoveries: 1) Performing a repair on these PSTs using SCANPST.EXE did not resolve the issue 2) Larger PSTs have imported fine (even to the same user mailbox) 3) Splitting these PSTs makes no difference (each is an archive, and I manually dragged the Inbox and Sent folders to separate newly created PSTs, when those failed the same way, I archived just a small portion of the data from those split PSTs into a new archive PST, importing it also failed) I also tried the following commands, and still got the same error when trying to import the same PSTs again afterwards: New-MailboxRepairRequest -Mailbox <user> -CorruptionType ProvisionedFolder New-MailboxRepairRequest -Mailbox <user> -CorruptionType FolderView Searching the net (and this forum) didn't turn up anything at all for me. Can anyone tell me what I should do next / how I should troubleshoot and/or fix this problem?

Hi Please try to use MFCMAPI to remove any weird folders or duplicates. http://www.microsoft.com/en-us/download/details.aspx?id=2953 hope it helps CheersZi Feng TechNet Community Support