• Locked Locked
  • Replies 2 replies
  • Subscribers 11 subscribers
  • Views 2296 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

PowerShell Migration Error: The source of the copy is null, please initialize a proper source node.

steckedk
over 5 years ago

​We are migrating many hundreds of intranet sates to SharePoint Online. We have found that we need an initial Master Page Gallery migration followed by a full content migration for each site. We are now a the point where we wish to script the migration in PowerShell. We generate the PS1 for same user and machine, which we have done before. We make the appropriate changes in the source and target URL's in the script and run it. We get the attached error. See attached for full but it says... "The source of the copy is null, please initialize a proper source node."

 

The source is present. The Content Matrix console connects to the source on the same box but the PS1 can't see it???

 

Any help appreciated. See attachment.

 

 

  • over 5 years ago

    Hi Doug,

     

    The "The source of the copy is null, please initialize a proper source node" error message usually indicates an incorrect URL being passed to the -SiteUrl property. To isolate the issue, please perform the following:

     

    • Ensure that the correct URL is being passed to the -SiteUrl parameter in the PowerShell script.
    • Connect to the source using the database adapter, then re-generate the PowerShell script.
    • Run the job migration through the Content Matrix console.

     

    Let me know what happens so I can assist you further.

     

    Regards,

    Cyrus

  • over 5 years ago

    Hi Cyrus,

     

    A few clarifications.

     

    There is no SiteURL property anywhere in the generated script. This is the initial script for Master Page Gallery. The relevant lines seem to be the following. They only have "Location Path" and "DisplayURL"

     

    # Load source

    $SourceCollection = New-MetalogixSerializableObjectCollection "<IXMLAbleList IXMLAbleType=`"Metalogix.Explorer.NodeCollection, Metalogix.Explorer, Version=8.7.0.3, Culture=neutral, PublicKeyToken=3b240fac3e39fc03`"><NodeCollection><Location Path=`"/https:%2F%2Fintranet.int-sp.apci.com%2Fsites%2Fwcmstoolkit`" DisplayUrl=`"intranet.int-sp.apci.com/.../wcmstoolkit`"><Connection NodeType=`"Metalogix.SharePoint.SPServer, Metalogix.SharePoint, Version=8.7.0.3, Culture=neutral, PublicKeyToken=3b240fac3e39fc03`" SharePointVersion=`"15.0.5023.1000`" UnderlyingAdapterType=`"WS`" ShowAllSites=`"False`" AdapterType=`"WS`" Url=`"root.int-sp.apci.com`" UserName=`"america\Blah`" SavePassword=`"True`" Password=`"Blah`" ReadOnly=`"True`" AuthenticationType=`"Metalogix.SharePoint.Adapters.Authentication.WindowsInitializer`" /></Location></NodeCollection></IXMLAbleList>"

     

    # Load target

    $TargetCollection = New-MetalogixSerializableObjectCollection "<IXMLAbleList IXMLAbleType=`"Metalogix.Explorer.NodeCollection, Metalogix.Explorer, Version=8.7.0.3, Culture=neutral, PublicKeyToken=3b240fac3e39fc03`"><NodeCollection><Location Path=`"/https:%2F%2Fapintg.sharepoint.com%2Fsites%2Fwcmstoolkit`" DisplayUrl=`"apintg.sharepoint.com/.../wcmstoolkit`"><Connection NodeType=`"Metalogix.SharePoint.SPTenant, Metalogix.SharePoint, Version=8.7.0.3, Culture=neutral, PublicKeyToken=3b240fac3e39fc03`" SharePointVersion=`"2147483647.0.0.0`" UnderlyingAdapterType=`"CSOM`" ShowAllSites=`"True`" AdapterType=`"CSOM`" Url=`"apintg-admin.sharepoint.com`" UserName=`"Blah@apinteg.com`" SavePassword=`"True`" Password=`"Blah`" ReadOnly=`"False`" AuthenticationType=`"Metalogix.SharePoint.Adapters.Authentication.Office365StandADFSInitializer`" /></Location></NodeCollection></IXMLAbleList>"

     

    Also... we can look at connection type and change to change to DB adapter. When you say run the Migration through the Content Matrix console, not sure what you mean. We need to migrate hundreds which is why we need to run PowerShell.

     

    Thanks,

    Doug