Forum Discussion
PST Imports - Security & Compliance - Or Outlook Imports
- Feb 15, 2018
Having worked as support engineer, I know they have some policies around the number of tickets and they are always pressed to close them as soon as possible. And most of the time you end up with someone working for an outsourcing company, not a direct Microsoft employee, unless you pay from Premier. But that's the reality of it.
I've relayed your troubles to some of the Exchange folks, hope something will come out of it.
Craig, other have been seeing numerous issues with "corrupt" items when doing regular mailbox moves to O365 in the past few days. It might be a coincidence, but I have a suspicion the two issues are related. I'll try to ping few folks (and also relay your experience with support).
Thank you Vasil. I'm now up to 5 open tickets but it doesn't seem there is any urgency around the issue so any help would be greatly appreciated.
- Dean_GrossFeb 14, 2018Silver Contributor
This probably won't make you feel any better, but I have been getting some excellent support from the SharePoint Online team for 3 tickets in the past 3 weeks.
- Craig IrvinFeb 14, 2018Copper Contributor
I typically get great support. However what I'm finding if it's anything past the easy stuff no one seem to give urgency to the problem and you're constantly asked to perform mundane troubleshooting tasks multiple times and barely any wiliness to admit to an issue.. just buy time until it goes away. I really wish there was a pay for option because believe me; I would pay for it.
To the mater at hand though. I just reran another import using the same PST file (which has failed three times now) and it's successful. I ran another import that previously failed and it still failing.
- Craig IrvinFeb 14, 2018Copper ContributorFrom: Office 365 Ambassadors
From reading the log file provided it seems that even though the file was not corrupt when you did your original import, it now has become corrupt.
I have also now been advised by senior management that we cannot continue troubleshooting this particular case due to three other open tickets being on the system and this being a duplicate. The reason for this is, that when running fixes from different locations on the same tenant it can cause more problems internally for yourself.
The last piece of advice I can give is to create a new pst file from the successfully imported mailbox that you have from 1/26.
I would also close all but one of the still open tickets and do what you did on this one and click the "i'm available" button and reference this case as the other agents don't seem to have done much on their end, but their tickets are the original and this I am afraid is Microsoft policy and cannot be broken.