SharePoint 2013 Foundation Migration to SPO

Question

SharePoint 2013 Foundation Migration to SPO

Michel AL HAYEK 187

Hello everyone. I am trying to migrate SP13 Foundation (not SP13 Server one) to SPO using the SPMT tool but after logging in and updating the source URL a blank white screen appears and I cannot proceed. I tried also to do the migration using PowerShell or by CSV file but the same errors pops-up. Any idea?

Michel AL HAYEK 187

Cannot get tenant setting for user ******@xxx.onmicrosoft.com Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPTransportException: Web Issue when doing SP Query ---> Microsoft.SharePoint.Migration.Common.Exceptions.WebTransportException ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
   --- End of inner exception stack trace ---

Michel AL HAYEK 187 Reputation points

2022-01-15T13:06:32.527+00:00

Powershell error

Accepted answer

0 additional answers

Your answer

Michel AL HAYEK 187 Reputation points

2022-01-15T11:40:48.577+00:00

Cannot get tenant setting for user ******@xxx.onmicrosoft.com Microsoft.SharePoint.MigrationTool.MigrationLib.SharePoint.MigSPTransportException: Web Issue when doing SP Query ---> Microsoft.SharePoint.Migration.Common.Exceptions.WebTransportException ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) --- End of inner exception stack trace ---
Michel AL HAYEK 187 Reputation points

2022-01-15T13:06:32.527+00:00

Powershell error

Answer 1

Hi @michelalhayek-6561 ,

Please perform the following troubleshooting:

1.Test with a Global Administrator account

2.Please run the below script as an admin

#Define SharePoint 2013 data source#  

$Global:SourceSiteUrl = "https://YourOnPremSite/"  
$Global:OnPremUserName = "Yourcomputer\administrator"  
$Global:OnPremPassword = ConvertTo-SecureString -String "OnPremPassword" -AsPlainText -Force  
$Global:SPCredential = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $Global:OnPremUserName, $Global:OnPremPassword  
$Global:SourceListName = "SourceListName"  


#Define SPO target#  
$Global:SPOUrl = "https://contoso.sharepoint.com/sites/sitename"  
$Global:UserName = "******@contoso.onmicrosoft.com"  
$Global:PassWord = ConvertTo-SecureString -String "YourSPOPassword" -AsPlainText -Force  
$Global:SPOCredential = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $Global:UserName, $Global:PassWord  
$Global:TargetListName = "TargetListName"  

#Define File Share data source#  
#$Global:FileshareSource = "YourFileShareDataSource"  

#Import SPMT Migration Module#  
Import-Module Microsoft.SharePoint.MigrationTool.PowerShell  

#Register the SPMT session with SPO credentials#  
Register-SPMTMigration -SPOCredential $Global:SPOCredential -Force  

#Add two tasks into the session. One is SharePoint migration task, and another is File Share migration task.#  
Add-SPMTTask -SharePointSourceCredential $Global:SPCredential -SharePointSourceSiteUrl $Global:SourceSiteUrl  -TargetSiteUrl $Global:SPOUrl -MigrateAll  
#Add-SPMTTask -FileShareSource $Global:FileshareSource -TargetSiteUrl $Global:SPOUrl -TargetList $Global:TargetListName  

#Start Migration in the background.#  
Start-SPMTMigration -NoShow  
Show-SPMTMigration

3.Uninstall SPMT and delete all caches, then reinstall SPMT to test.

caches:

C:\Users{account}\AppData\Roaming\Microsoft\MigrationTool

C:{account}\spsetup\AppData\Roaming\Microsoft\MigrationToolStorage

Thanks,
Echo Du

============================
Updated Answer ========================

Hi @michelalhayek-6561 ,

According to your description, I have the following points to clarify:

1.Modify/Rename those documents with long URLs to limit URLs to 255 characters. Note:The URL fields in a SharePoint list or library have a 255 character limit.

2.It is recommended that you create a new site collection and then backup/restore the source site collection to this new blank site collection.

Please follow the steps:

1.Please run the below PowerShell to backup the source site collection

Add-PSSnapin “Microsoft.SharePoint.PowerShell”  
Backup-SPSite http://sp -Path C:\Backup\SP-Home.bak -UseSqlSnapshot

2.Create new site collection

#Add-PSSnapin “Microsoft.SharePoint.PowerShell”  
New-SPSite http://sp/sites/testsite -OwnerAlias "domain\username" -Language 1033 -Template STS#0

3.Restore the backup file to the new blank site collection
Note: -Force will overwrite all the content of the original site, so it is recommended that you create a new site in advance to replace.

#“SQL” is SQL Server name and "WSS_Content" is Datebase name  
Restore-SPSite http://sp/sites/testsite -Path C:\Backup\SP-Home.bak -Force -DatabaseServer SQL -DatabaseName WSS_Content

4.Finally use the SPMT to migrate SharePoint 2013 Foundation site content(http://sp/sites/testsite) to SharePoint Online

Thanks,
Echo Du

=======================================

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Michel AL HAYEK 187 Reputation points

2022-01-17T06:45:33.057+00:00

Hi @Echo Du_MSFT ,

The 2 screenshots above are the results of this migration script. I already tried to test this but no luck. What I have noticed so far is that the migration tool is working only on SP sites with format http://contoso/sites/department. But the site that I want to migrate is http://contosto, and it keeps showing me a white blank screen or site doesn't exist. I am trying now to backup/restore to a new site with URL format http://contoso/sites/department so I can migrate using SPMT, but also the Restore script is throwing an error "cannot rename old site". After many hours of debugging, I found out that I have some documents with long relative URLs (>260 characters) and that was the main reason that the restore task is failing. Trying now to duplicate the site using Sharegate. Any helpful advice or what is the fastest way to change a site URL without taking risks of losing data?

p.s: some people faced this before and they have deleted the document library with the long relative URL. they backed up the site. deployed to a new site. then they restored back the doc lib from the recycle.
Echo Du_MSFT 17,316 Reputation points

2022-01-21T10:01:40.37+00:00

Hi @michelalhayek-6561 ,

Thanks for your reply.

I have updated answer under initial My Answer. Hope this can help you to solve issue. Have a nice day!

Thanks,
Echo Du
Echo Du_MSFT 17,316 Reputation points

2022-01-24T09:07:31.077+00:00

Hi @michelalhayek-6561 ,

Is there anything else I can help with regarding this issue?

You can comment us at any time and we will continue to follow up.

Thanks,
Echo Du
Michel AL HAYEK 187 Reputation points

2022-01-24T12:13:46.937+00:00

@Echo Du_MSFT yup that's correct. The update that you did on your answer is the steps that I did to fix my problem.

Share via

SharePoint 2013 Foundation Migration to SPO

0 additional answers

Your answer