Forum Discussion
PST Imports - Security & Compliance - Or Outlook Imports
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 Irvin wrote:
From: 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.
The tickets though they are duplicate in nature the problem exists in all tenants; why should any be closed? Just because it's a single person opening the tickets in all of the environments doesn't mean the issue isn't legitimately being experienced in all of the environments. So what is being said is we don't care about 3 of the 4 tenants experiencing this problem? How exactly is the scale of the issue able to be defined when you can't open legitimate tickets in the environments where the problem is being experienced?
Anyone at Microsoft support please look up one of the tickets and give me a call. I would love to discuss this policy and why Microsoft has now basically taken a stance on not providing support on clearly an issue with the service on 3 of the 4 customers that are experiencing this issue.
FYI in terms of the "scanpst" I've already provided information that we
1. Generated new PST's
2. Was able to open and import previous and new PST's into a mailbox that is on our local Exchange server.
3. Shown that the same exact PST file was successful orginally, failed, failed and now succeeded. So if the PST file was corrupt then why is this happening?
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.