Stuck in import pst problem

Anonymous
2022-10-21T21:05:37+00:00

Hello All,

I'm stuck in a very strange problem and need help.

I imported pst file to m365 exchange using lifecycle data management console (https://compliance.microsoft.com), i sent as usal my pst using azcopy; i validate my mapping file and then i launched import to 365, as I maded it several times.

After a long time (my pst are quite little (12 gb in two files) i got an import error.

The same error appears on log with each pst.

Many thanks for helping me.

Best regards.

Herve

*******************************************

Here are the logs :

PST Filename,Target Mailbox,Import Status,Error,Total Items,Item Imported,Target Folder,Skipped Item Count,Last Failure,Total Item Size,Imported Item Size

mypstfilename.pst,___@___.___,Failed,Unknown,0,0,,0,System.NullReferenceException: Object reference not set to an instance of an object.

at Microsoft.IdentityModel.Clients.ActiveDirectory.AuthenticationContext.RunAsyncTaskT

at Microsoft.Office.Compliance.Ingestion.OAuthProvider.GetAppTokenFromESTS(OAuthTokenType tokenType, String tenantId, String serviceName, String serviceHostName) in k:\dbs\sh\nibr\1018_000434\cmd\0\sources\dev\ingestion\src\workloadapi\PSWSProvider\OAuthProvider.cs:line 492

at Microsoft.Office.Compliance.Ingestion.OAuthProvider.OAuthHackToInsertServicePrincipal(String tenantId) in k:\dbs\sh\nibr\1018_000434\cmd\0\sources\dev\ingestion\src\workloadapi\PSWSProvider\OAuthProvider.cs:line 238

at Microsoft.Office.Compliance.Ingestion.OAuthProvider.GetAppTokenFromAcs(OAuthTokenType tokenType, String tenantId, String serviceName, String serviceHostName) in k:\dbs\sh\nibr\1018_000434\cmd\0\sources\dev\ingestion\src\workloadapi\PSWSProvider\OAuthProvider.cs:line 463

at Microsoft.Office.Compliance.Ingestion.OAuthProvider.<>c__DisplayClass18_0.<GetTenantToken>b__0(String serviceName) in k:\dbs\sh\nibr\1018_000434\cmd\0\sources\dev\ingestion\src\workloadapi\PSWSProvider\OAuthProvider.cs:line 198

at Microsoft.Office.Compliance.Ingestion.OAuthProvider.GetAuthToken(OAuthTokenType tokenType, String tenantId, String serviceHostName, Func`2 authentication) in k:\dbs\sh\nibr\1018_000434\cmd\0\sources\dev\ingestion\src\workloadapi\PSWSProvider\OAuthProvider.cs:line 367

at Microsoft.Office.Compliance.Ingestion.OAuthProvider.GetUserToken(OAuthTokenType tokenType, String tenantId, String upn, String puid, String serviceHostName, Boolean usingSts) in k:\dbs\sh\nibr\1018_000434\cmd\0\sources\dev\ingestion\src\workloadapi\PSWSProvider\OAuthProvider.cs:line 215

at Microsoft.Office.Compliance.Ingestion.PswsOAuthAuthenticator.Authenticate(HttpWebRequest request) in k:\dbs\sh\nibr\1018_000434\cmd\0\sources\dev\ingestion\src\workloadapi\PSWSProvider\PswsOAuthAuthenticator.cs:line 106

at Microsoft.Exchange.PswsClient.PswsCmdlet.InternalRun()

at Microsoft.Exchange.PswsClient.NewPswsCmdlet`1.Run()

at Microsoft.Office.Compliance.Ingestion.ExchangeIngestionProvider.CreateNewMailboxImportRequest(String targetId, String azureBlobStorageAccountUri, String azureBlobSASToken, Boolean isArchive, String azureStatusPublishEndpointInfo, String name, String targetRootFolder, Nullable`1 contentCodePage, Int32 unrecognizedMailLimitPercent, String rulesBlobSasUri, ILogWriter logWriter, String& cmdText, String& error) in k:\dbs\sh\nibr\1018_000434\cmd\0\sources\dev\ingestion\src\workloadapi\IngestionProvider\ExchangeIngestionProvider.cs:line 727,0,0

Microsoft 365 and Office | Subscription, account, billing | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2022-11-17T07:29:59+00:00

I've not yet had to do another import, but on my support ticket they said it was now fixed.

Was this answer helpful?

2 people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2022-11-10T16:42:09+00:00

Are you still having this issue?

Everything looks good on my end with the 365 import service among other things.

I'm also unable to find incident EX450352 anywhere under service health or via Google.

Was this answer helpful?

1 person found this answer helpful.
0 comments

50 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2022-10-25T13:34:58+00:00

    Yes its correct

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-10-25T20:42:25+00:00

    Hey Hervé,

    Please can you DM me the fix? I don't quite understand what you've done? I've done migrations for 5 years and never had an issue until now, so I guess its a Microsoft change as I always follow the same steps! I notice their article for imported was updated this month which suggests they changed something backend too....

    I always set the UPN and email address etc to the correct domain address to match both the exported PST, but also the PST mapping file, so not sure what could be wrong.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-10-26T07:38:30+00:00

    Hello Sean

    I added to my process impersonation :

    New-ManagementRoleAssignement -name impersonationAssignementName -Role ApplicationImpersonation -user myadmin.mydomain.com

    Here are my whole process right before migration :

    Connect-ExchangeOnline

    Enable-OrganizationCustomization 

    New-ManagementRoleAssignment -Role "Mailbox Import Export" -User "******@mydomain.com"

    New-ManagementRoleAssignment -Role "Mailbox Import Export" -SecurityGroup "Organization Management" -Name "Import Export Org Management"

    New-ManagementRoleAssignement -name impersonationAssignementName -Role ApplicationImpersonation -user myadmin.mydomain.com

    And check with

    Get-ManagementRoleAssignment –Role "Mailbox Import Export" | FL RoleAssigneeName, Name

    My process came from https://lazyadmin.nl/office-365/import-pst-file-into-office-365/ (solution 2)

    Was this answer helpful?

    0 comments