SharePoint Migration Tool
8 TopicsSharepoint Migration Tool - Missing config after update
Hi Community, I'm running a migration with data of a Window Server 2012 Server to Sharepoint using the Sharepoint Migration Tool. Until the users switch to sharepoint, I hit the incremental migration every day. But some days ago the Migration Tool started to update and now it doesn't start anymore.. I could use another server, but then I loose all migration config. Is there a way to get the old migration config without restarting the whole Migration process? Thanks a lot! Steffen1.1KViews0likes1CommentMigrating SharePoint List items created between two dates
Hello Community, I have a SharePoint 2013 list containing items created between 2012 and 2022. I want to migrate only the ones created in 2015 to SharePoint Online. I am using SharePoint Migration Tool. Note: I cannot migrate all of the source list and then delete all the non 2015 records because it exceeds 50 000 items. The tool only offers migrating list items that are created/modified after a certain date. Is there a way to only migrate list items that are created between two dates? Maybe using JSON for bulk migration? Maybe something like the following: { "Tasks": [ { "SourcePath": "source path", "TargetPath": "target path", "Items": { "Lists": [ { "SourceList": "source", "TargetList": "target" } ], "SubSites": [] }, "Settings":{ "MigrateFilesCreatedAfter": "2014-12-31", "MigrateFilesCreatedBefore": "2016-01-01" } } ] }581Views0likes0CommentsSharepoint Migration Tool Error 0x01710004
I'm trying to migrate on-premises sharepoint Server 2010 to Sharepoint 365, but the migration always terminate with error 0x01710004. The document analysis end without error, but the migration not. Looking at the log file I found this recourring error for each document: TimeStamp:09/03/2020 07:16:36 Package#:[0] EventType:[JOBERROR] PackageID:[2c56807f-6b08-4c8b-9c39-8576238ea2a4] JobID:[192d7662-d60a-450c-b21a-b6d9afa220e6] FilesCreated:0/2 Event:JobError JobId:192d7662-d60a-450c-b21a-b6d9afa220e6 Time:09/03/2020 07:16:36.803 TotalRetryCount:0 MigrationType:None MigrationDirection:Import ObjectType:ListItem Url:xxxxxxxxxx/xxxxxxxxxx/xxxxxxxxxxxx.xlsx Id:07c1aedb-01c5-4df4-958a-237c9f785224 SourceListItemIntId:1 TargetListItemIntId:1 ErrorCode:-2146232832 ErrorType:Microsoft.SharePoint.SPException Message:Item does not exist. It may have been deleted by another user. CallStack -- at Microsoft.SharePoint.SPListItem.EnsureItemIsValid() at Microsoft.SharePoint.SPListItem.GetValue(SPField fld, Int32 columnNumber, Boolean bRaw, Boolean bThrowException) at Microsoft.SharePoint.SPListItem.get_FileSystemObjectType() at Microsoft.SharePoint.SPListItem.get_File() at Microsoft.SharePoint.Deployment.ListItemSerializer.SetObjectData(Object obj, SerializationInfo info, StreamingContext context, ISurrogateSelector selector) at Microsoft.SharePoint.Deployment.XmlFormatter.CallSetObjectData(Object obj, SerializationInfo objectData, ISerializationSurrogate surrogate, ISurrogateSelector selector) CorrelationId:70a7cc01-fbcf-4c67-a2ee-c0ba8a545954 What can I do to solve the issue? Thanks5.1KViews0likes5Commentscontent migration
Hi Community, I am looking to migrate SharePoint online site pages to another site collection. The source is a SharePoint online team site and destination is SharePoint online communication site. I have tried using the SharePoint migration tool and the site page is successfully migrated however on clicking it's throwing error and not opening the site page. Can someone guide me how can i resolve this issue or any other way that you would like to suggest based on your past experience ? Regards, Tayyab649Views0likes0CommentsSharePoint Migration Tool - Full Control permission not preserved
Hi, I'm using SPMT version 3.2.118.0 and I'm trying to migrate a folder of a file share to the root folder a doclib of a SPO site while preserving permissions. Groups or users with Read and Write permissions are well migrated with these permissions preserved (read--read, write-->contribute) but groups or users with "full control" permissions are not migrated at all! And SPMT reports it has successfully migrated the content! Example: If my local share is C:\TestDocs with -user1 having full control, -group1 Read perm, -group2 Write perm and -group3 Full control The target /TestDocs document library of the SPO site will have indeed unique permissions but with: -group1 Read perm, -group2 Contribute perm user1 and group3 which were supposed to have Full control are lost! I checked the reports and logs but cannot find any information. Any idea? Thanks Franck1KViews0likes0CommentsSharePoint Migration Tool calls are THROTTLED by O365 API
Hi, We have a customer with SharePoint 2013 environment, hosted in Azure (as a few VMs). Let's call the customer Contoso (NDA restriction), for which we are creating Migration solution, based on latest SharePoint Migration Tool v3.2.114.0 (and its PowerShell reference). We implemented a simple PowerShell script, that uses SPMT PS cmdlets to Register SPMT Migration, adds tasks and starts SPTM Migration. # -------------- MIGRATION WITH SPMT -------------- # # Register the SPMT session with SPO credentials# Register-SPMTMigration -SPOCredential $Global:SPOCredential ` -SkipSitesWithName "$($Global:subWebs -join ';')" ` -EnableMultiRound $true ` -Force # Add migration task into the session Add-SPMTTask -SharePointSourceCredential $Global:SPCredential ` -SharePointSourceSiteUrl $Global:SourceSiteUrl ` -TargetSiteUrl $Global:SPOTargetSiteUrl ` -MigrateAll # Migrate all lists and libraries! #Start Migration in the console. # Start-SPMTMigration Source sites are small sites with some documents (on test environment it is from 10 to 200 MB of documents), some members (from 5 to 50). No custom solutions migrated. No large data or large quantity of files. We are now in implementation and internal testing phase, which lasted a few months already. Everything worked good so far, until September 24, 2019. On that day we started to receive strange THROTTLING responses from O365, when SharePoint Migration Tool tried to request any info from the environment. SPMT logs are full of following (or similar) records: 2019-10-17 16:02:53.5014|INFO|WF|275|8f837fbd|Start Assessing 'https://intranet-uat.contoso.com/teamsites/Event-Sverige' 2019-10-17 16:02:53.5014|DEBUG|WF|275|8f837fbd|Scan using previous report 2019-10-17 16:02:53.5014|DEBUG|WF|275|8f837fbd|Assess source credentials... 2019-10-17 16:02:53.6734|DEBUG|WF|275|8f837fbd|Assess target credential... 2019-10-17 16:02:53.6734|DEBUG|WF|275|8f837fbd|Getting schema for site https://contoso.sharepoint.com/teams/Event-Sverige 2019-10-17 16:02:53.8434|DEBUG|WF|275|8f837fbd|Scanning full web /teams/event-sverige under site https://contoso.sharepoint.com/teams/Event-Sverige 2019-10-17 16:02:54.5004|DEBUG|WF|275|8f837fbd|Successfully fetch navigation setting for web https://contoso.sharepoint.com/teams/Event-Sverige 2019-10-17 16:02:54.7384|ERROR|WF|275|8f837fbd|Csom call with TraceCorrelationId 42c30e9f-4052-1000-0076-4b5ecedef351 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-10-17 16:02:54.7554|ERROR|WF|275|8f837fbd|Failed to load web navigation trees layer by layer 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) at Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPClientContext.RunWithRetry(Action logicToRetry, Int32 retryCount, Int32 retryIntervalMiliSeconds, Func`2 exceptionHandler, String errorMessage, Boolean resetContextIfRetry) 300 times for this migration session (as an example). Error, marked blue , is different for each occurrence – SPMT makes different requests to Target environment (both on Scanning and Migration phases), and sometimes O365/SPO API refuses these requests with “Too many requests” response. As a result of that throttling, we often (often!) get “INVALID CREDENTIALS” Fatal Error during migration. "Invalid credentials","ACTION_STOP","0x0201000C" 2019-10-17 16:03:02.6755|ERROR|WF|275|8f837fbd|Got a fatal exception during scan Microsoft.SharePoint.MigrationTool.MigrationLib.Assessment.Exceptions.InvalidCredentialsException: Invalid credentials ---> Microsoft.SharePoint.Migration.Common.Exceptions.WebCredentialException ---> System.Net.WebException: The remote server returned an error: (401) Unauthorized. at System.Net.HttpWebRequest.GetResponse() at Microsoft.SharePoint.MigrationTool.MigrationLib.Common.Net.HttpWebRequestProxy.GetResponse() --- End of inner exception stack trace --- at Microsoft.SharePoint.Migration.Common.Exceptions.WebExceptionBase.Create(WebException e) at Microsoft.SharePoint.MigrationTool.MigrationLib.Common.Net.HttpWebRequestProxy.GetResponse() at Microsoft.SharePoint.Migration.Common.Utilities.RunWithRetry[T](Func`1 logicToRetry, Int32 retryCount, Int64 timeOutSeconds, Int32 retryIntervalMiliSeconds, String errorMessage, Type[] retryExceptionTypes, Type[] nonRetryExceptionTypes) We say “often”, but not “always”. Sometimes our Migration Sessions ends well, and everything is migrated, despite a lot of “Too many requests” responses (because of Retry Policy in SPMT – it repeats requests). Approximate quantity – 50% failed sessions, 50% successful sessions. But even though we are lucky to see “COMPLETED” status – it takes AN HOUR or more to migrate 50-100 MB package. Credentials of SPO Admin account are verified - and they are correct, because Migration Script creates a new Target site before launching SMPT Migration session. And, of course, credentials of SPO Admin are NOT CHANGED during Migration Session. We also tried to CHANGE SPO Admin account, which makes the migration. It helps for some small period (a few migrations), and then throttling comes back. Of course, we know about https://docs.microsoft.com/en-us/sharepoint/dev/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online - but I stress out, that we don't use any custom solutions for migration, we rely only on SPMT (latest version). All users’ requests are not throttled. End-user experience is completely fine. Our test CSOM requests are NOT throttled as well. Everything is fine, when we are, for example, uploading several PDFs to Target site with CSOM, with the same credentials. Regarding tenant usage: Customer has a few active users for now: DEV team and test team. They have 17 active sites only (and the traffic on that is VERY low). SharePoint Online services are completely healthy (based on Admin Center reports). We have an important question: We are migrating almost empty sites from UAT environment now. The sites, that have 20, 30, 100 MB of documents. We are doing it from a single Azure machine. Single user does it. We are using latest, out-of-the box SPMT. Why it is getting throttled?7.1KViews0likes4CommentsURGENT! SharePoint Migration Tool Error: "Package Engine has stopped because Azure queue failed"
Hi, I'm trying to migrate some files from a local drive to OneDrive for Business and I keep getting this error. I have tried it with different folders as well. It's quite urgent as I need to have these migrated by tonight! Screenshot attached below in this post. How can I fix this issue? ThanksSolved21KViews0likes10CommentsSharePoint Migration Tool - Role permission
I am a site owner to a site. I want move 90 GB size of data including folders using SharePoint Migration tool. Question : What kind of role and permission need SharePoint migration utility. Can "Site Owner" migrate data from file share to sharepoint online using SharePoint migration utility? Or SharePoint Administrator can migrate data ? To update metadata using CSOM , what kind of role is needed.1.1KViews0likes1Comment