none
SharePoint Migration Tool extremely slow Taxonomy migration. RRS feed

  • Question

  • Hi all,

    I'm working on migrating some on-premises SharePoint sites to SharePoint Online with the Microsoft SharePoint Migration Tool. Everything works well for the most part, but the tool itself stalls for almost an hour and a half before it actually scanns a single file and begins migrating anything.

    From cross referencing the logs, it seems like the culprit is the Taxonomy migration phase. My best prediction is that it is getting hung up when trying to migrate users that existed in the On Prem site but do not exist in SharePoint Online.

    After the taxonomy migration phase completes, around 90 minutes after the migration it started, it finally begins scanning files and then migrating them. Once this happens, the migration completes normally at an expected rate.

    Here are a couple excerpts from the log file. I only pulled out points of interest as I needed to sanitize emails / user IDs.

    I think the primary cause of concern might be the repeating "request to send message" logs. It seems like it is trying to send a request one every ~2 minutes. This happens several times throughout the log. Since it seems to take 10-15 minutes each time it happens, it likely is causing much of the slowness during this phase.

    I notices a couple (401) Unauthorized errors as well, but I am not sure why this would be happening as I am migrating the site as a site admin.

    2019-08-26 11:07:15.4021|DEBUG|WF|33|e0923b20|Taxonomy migration: start 
    2019-08-26 11:07:15.8067|DEBUG|WF|33|e0923b20|Taxonomy migration: start global groups migration 
    2019-08-26 11:07:16.8942|ERROR|WF|33|e0923b20|Csom call with TraceCorrelationId b50dfe9e-301d-0000-4758-4a1a8b771969 from SPO Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPAuthenticationException: Credential Issue when doing SP Query ---> Microsoft.SharePoint.Client.ServerUnauthorizedAccessException: Access denied. You do not have permission to perform this action or access this resource.
       at Microsoft.SharePoint.Client.ClientRequest.ProcessResponseStream(Stream responseStream)
       at Microsoft.SharePoint.Client.ClientRequest.ProcessResponse()
       at Microsoft.SharePoint.Client.ClientContext.ExecuteQuery()
       at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.WrapExceptions(Action logicToRetry)
       --- End of inner exception stack trace ---
       at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.WrapExceptions(Action logicToRetry)
       at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.ExecuteQuery(String callerMemberName, String callerFilePath)
    2019-08-26 11:07:16.9062|ERROR|WF|33|e0923b20|Taxonomy migration: error retrieving the taxonomy termstore Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPAuthenticationException: Credential Issue when doing SP Query ---> Microsoft.SharePoint.Client.ServerUnauthorizedAccessException: Access denied. You do not have permission to perform this action or access this resource.
       at Microsoft.SharePoint.Client.ClientRequest.ProcessResponseStream(Stream responseStream)
       at Microsoft.SharePoint.Client.ClientRequest.ProcessResponse()
       at Microsoft.SharePoint.Client.ClientContext.ExecuteQuery()
       at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.WrapExceptions(Action logicToRetry)
       --- End of inner exception stack trace ---
       at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.WrapExceptions(Action logicToRetry)
       at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.ExecuteQuery(String callerMemberName, String callerFilePath)
       at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.RunWithRetry(Action logicToRetry, Int32 retryCount, Int32 retryIntervalMiliSeconds, Func`2 exceptionHandler, String errorMessage, Boolean resetContextIfRetry)
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.RunWithRetry(Action logicToRetry, Int32 retryCount, Int32 retryIntervalMiliSeconds, Func`2 exceptionHandler, String errorMessage, Boolean resetContextIfRetry)
       at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.RunWithRetry(Action logicToRetry, Int32 retryCount, String errorMessage, Type[] retryExceptionTypes)
       at Microsoft.SharePoint.MigrationTool.MigrationLib.Taxonomy.TaxonomyCsomScanner.GetTermStoreMetaInfo()
    2019-08-26 11:07:16.9062|DEBUG|WF|33|e0923b20|Exception did not match retry types Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPAuthenticationException 
    2019-08-26 11:07:16.9062|DEBUG|WF|33|e0923b20|Credential issue when trying to retrieve GroupManagerPrincipalNames and ContributorPrincipalNames 
    2019-08-26 11:07:16.9231|DEBUG|WF|33|e0923b20|Taxonomy migration: fetch and store taxonomy information from OnPrem 
    2019-08-26 11:07:16.9231|DEBUG|WF|33|e0923b20|GroupManagerPrincipalNames and ContributorPrincipalNames properties are not initialized, only supported by lastest version. 
    2019-08-26 11:08:29.4396|DEBUG|WF|ARIA|Request to send message. 
    2019-08-26 11:08:29.4396|DEBUG|WF|ARIA|DispatchMessages - Done. Count:1 
    2019-08-26 11:09:37.0340|ERROR|WF|33|e0923b20|Csom call with TraceCorrelationId d60dfe9e-d0d8-0000-4971-36c43249bb87 from SPO Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPTooManyRequestsException: Too many requests response from SharePoint Online. Stop the task. ---> Microsoft.SharePoint.Migration.Common.Exceptions.WebTooManyRequestException ---> System.Net.WebException: The remote server returned an error: (401) Unauthorized.
       at System.Net.HttpWebRequest.GetResponse()
       at Microsoft.SharePoint.Client.SPWebRequestExecutor.Execute()
       at Microsoft.SharePoint.Client.ClientRequest.ExecuteQueryToServer(ChunkStringBuilder sb)
       at Microsoft.SharePoint.Client.ClientContext.ExecuteQuery()
       at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.WrapExceptions(Action logicToRetry)
       --- End of inner exception stack trace ---
       at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.WrapExceptions(Action logicToRetry)
       --- End of inner exception stack trace ---
       at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.WrapExceptions(Action logicToRetry)
       at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.ExecuteQuery(String callerMemberName, String callerFilePath)
    
    ...
    
    2019-08-26 11:18:35.1482|DEBUG|WF|33|e0923b20|GroupManagerPrincipalNames and ContributorPrincipalNames properties are not initialized, only supported by lastest version. 
    2019-08-26 11:18:40.8576|DEBUG|WF|33|e0923b20|GroupManagerPrincipalNames and ContributorPrincipalNames properties are not initialized, only supported by lastest version. 
    2019-08-26 11:18:47.7846|ERROR|WF|33|e0923b20|Csom call with TraceCorrelationId 5d0efe9e-80b6-0000-4971-3cfab1d4c190 from SPO Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPServerException: Server Issue when doing SP Query ---> Microsoft.SharePoint.Client.ServerException: The specified user [e-mail redacted] could not be found.
       at Microsoft.SharePoint.Client.ClientRequest.ProcessResponseStream(Stream responseStream)
       at Microsoft.SharePoint.Client.ClientRequest.ProcessResponse()
       at Microsoft.SharePoint.Client.ClientContext.ExecuteQuery()
       at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.WrapExceptions(Action logicToRetry)
       --- End of inner exception stack trace ---
       at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.WrapExceptions(Action logicToRetry)
       at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.ExecuteQuery(String callerMemberName, String callerFilePath)
    2019-08-26 11:18:47.7956|ERROR|WF|33|e0923b20|Taxonomy migration: failed resolving property Term Owner: cannot load user i:0#.f|membership|[e-mail redacted] Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPServerException: Server Issue when doing SP Query ---> Microsoft.SharePoint.Client.ServerException: The specified user [e-mail redacted] could not be found.
       at Microsoft.SharePoint.Client.ClientRequest.ProcessResponseStream(Stream responseStream)
       at Microsoft.SharePoint.Client.ClientRequest.ProcessResponse()
       at Microsoft.SharePoint.Client.ClientContext.ExecuteQuery()
       at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.WrapExceptions(Action logicToRetry)
       --- End of inner exception stack trace ---
       at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.WrapExceptions(Action logicToRetry)
       at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.ExecuteQuery(String callerMemberName, String callerFilePath)
       at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.RunWithRetry(Action logicToRetry, Int32 retryCount, Int32 retryIntervalMiliSeconds, Func`2 exceptionHandler, String errorMessage, Boolean resetContextIfRetry)
    2019-08-26 11:18:47.8287|DEBUG|WF|33|e0923b20|Normal retry:[e98410b3], Retry Times[1] 
    
    ...
    
    2019-08-26 11:19:45.4962|DEBUG|WF|33|e0923b20|Taxonomy migration: (from cache) failed resolving property Term Owner: cannot find user [ID redacted] 
    2019-08-26 11:19:45.4962|DEBUG|WF|33|e0923b20|Taxonomy migration: (from cache) failed resolving property Term Owner: cannot find user [ID redacted] 
    2019-08-26 11:19:45.4962|DEBUG|WF|33|e0923b20|Taxonomy migration: (from cache) failed resolving property Term Owner: cannot find user [ID redacted] 
    2019-08-26 11:19:45.4962|DEBUG|WF|33|e0923b20|Taxonomy migration: (from cache) failed resolving property Term Owner: cannot find user [ID redacted] 
    2019-08-26 11:19:45.7054|DEBUG|WF|33|e0923b20|GroupManagerPrincipalNames and ContributorPrincipalNames properties are not initialized, only supported by lastest version. 
    2019-08-26 11:19:47.1865|DEBUG|WF|33|e0923b20|GroupManagerPrincipalNames and ContributorPrincipalNames properties are not initialized, only supported by lastest version. 
    2019-08-26 11:19:54.0928|DEBUG|WF|33|e0923b20|GroupManagerPrincipalNames and ContributorPrincipalNames properties are not initialized, only supported by lastest version. 
    2019-08-26 11:19:54.7889|DEBUG|WF|33|e0923b20|GroupManagerPrincipalNames and ContributorPrincipalNames properties are not initialized, only supported by lastest version. 
    2019-08-26 11:20:29.8377|DEBUG|WF|ARIA|Request to send message. 
    2019-08-26 11:20:29.8377|DEBUG|WF|ARIA|DispatchMessages - Done. Count:1 
    2019-08-26 11:22:29.9058|DEBUG|WF|ARIA|Request to send message. 
    2019-08-26 11:22:29.9058|DEBUG|WF|ARIA|DispatchMessages - Done. Count:1 
    2019-08-26 11:24:29.9779|DEBUG|WF|ARIA|Request to send message. 
    2019-08-26 11:24:29.9779|DEBUG|WF|ARIA|DispatchMessages - Done. Count:1 
    2019-08-26 11:26:30.0440|DEBUG|WF|ARIA|Request to send message. 
    2019-08-26 11:26:30.0440|DEBUG|WF|ARIA|DispatchMessages - Done. Count:1 
    2019-08-26 11:28:30.1060|DEBUG|WF|ARIA|Request to send message. 
    2019-08-26 11:28:30.1060|DEBUG|WF|ARIA|DispatchMessages - Done. Count:1 
    2019-08-26 11:30:30.1737|DEBUG|WF|ARIA|Request to send message. 
    2019-08-26 11:30:30.1737|DEBUG|WF|ARIA|DispatchMessages - Done. Count:1 
    2019-08-26 11:32:30.2384|DEBUG|WF|ARIA|Request to send message. 
    2019-08-26 11:32:30.2384|DEBUG|WF|ARIA|DispatchMessages - Done. Count:1 
    2019-08-26 11:34:30.3039|DEBUG|WF|ARIA|Request to send message. 
    2019-08-26 11:34:30.3039|DEBUG|WF|ARIA|DispatchMessages - Done. Count:1 
    
    ...
    
    2019-08-26 11:55:44.2030|DEBUG|WF|33|e0923b20|Taxonomy migration: (from cache) failed resolving property Term Owner: cannot find user [ID redacted]
    2019-08-26 11:55:44.2030|DEBUG|WF|33|e0923b20|Taxonomy migration: (from cache) failed resolving property Term Owner: cannot find user [ID redacted]
    2019-08-26 11:55:44.2030|DEBUG|WF|33|e0923b20|Taxonomy migration: (from cache) failed resolving property Term Owner: cannot find user [ID redacted]
    2019-08-26 11:55:44.2030|DEBUG|WF|33|e0923b20|Taxonomy migration: (from cache) failed resolving property Term Owner: cannot find user [ID redacted]
    2019-08-26 11:55:44.3992|DEBUG|WF|33|e0923b20|GroupManagerPrincipalNames and ContributorPrincipalNames properties are not initialized, only supported by lastest version. 
    2019-08-26 11:55:46.0351|DEBUG|WF|33|e0923b20|GroupManagerPrincipalNames and ContributorPrincipalNames properties are not initialized, only supported by lastest version. 
    2019-08-26 11:55:54.3848|DEBUG|WF|33|e0923b20|GroupManagerPrincipalNames and ContributorPrincipalNames properties are not initialized, only supported by lastest version. 
    2019-08-26 11:55:55.1434|DEBUG|WF|33|e0923b20|GroupManagerPrincipalNames and ContributorPrincipalNames properties are not initialized, only supported by lastest version. 
    2019-08-26 11:56:31.0514|DEBUG|WF|ARIA|Request to send message. 
    2019-08-26 11:56:31.0514|DEBUG|WF|ARIA|DispatchMessages - Done. Count:1 
    2019-08-26 11:58:31.1186|DEBUG|WF|ARIA|Request to send message. 
    2019-08-26 11:58:31.1186|DEBUG|WF|ARIA|DispatchMessages - Done. Count:1 
    2019-08-26 12:00:31.1846|DEBUG|WF|ARIA|Request to send message. 
    2019-08-26 12:00:31.1846|DEBUG|WF|ARIA|DispatchMessages - Done. Count:1 
    2019-08-26 12:02:31.2508|DEBUG|WF|ARIA|Request to send message. 
    2019-08-26 12:02:31.2508|DEBUG|WF|ARIA|DispatchMessages - Done. Count:1 
    2019-08-26 12:04:31.3016|DEBUG|WF|ARIA|Request to send message. 
    2019-08-26 12:04:31.3016|DEBUG|WF|ARIA|DispatchMessages - Done. Count:1 
    2019-08-26 12:06:31.3676|DEBUG|WF|ARIA|Request to send message. 
    2019-08-26 12:06:31.3676|DEBUG|WF|ARIA|DispatchMessages - Done. Count:1 
    2019-08-26 12:08:31.4389|DEBUG|WF|ARIA|Request to send message. 
    2019-08-26 12:08:31.4389|DEBUG|WF|ARIA|DispatchMessages - Done. Count:1 
    2019-08-26 12:10:31.5054|DEBUG|WF|ARIA|Request to send message. 
    2019-08-26 12:10:31.5054|DEBUG|WF|ARIA|DispatchMessages - Done. Count:1 
    
    ...
    
    2019-08-26 12:23:21.2143|DEBUG|WF|33|e0923b20|Taxonomy migration: no groups at OnPrem, no need to do migration 
    2019-08-26 12:23:21.2143|DEBUG|WF|33|e0923b20|Taxonomy migration: site level taxonomy migration finished successfully 
    2019-08-26 12:23:21.2143|DEBUG|WF|33|e0923b20|Taxonomy migration: end 

    I also wanted to mention, that if the internet is disconnected during the taxonomy migration, then reconnected after half a minute, the taxonomy migration fails due to network exceptions but the rest of the migration continues and completes successfully. 

    Has anyone else experienced something like this? I figure it could potentially be an issue with the On Prem site configuration, but other tools like Metalogix Content Matrix, and Quest Essentials do not run into an issue like this.

    Tuesday, August 27, 2019 3:40 PM

All replies

  • Seems product defect, needs product Group Team involved. Ask customer to submit request to uservoice.

    --
    Freya

    Tuesday, October 29, 2019 1:25 PM