Issue while copying/moving files using Exploer

Question

While copying/moving files from site to sub-site using Explorer view, we are seeing below message from SharePoint. Pls. let us know if anyone in SharePoint community has faced this issue.

Answer 1

I'm pretty aure it's a file/folder length issue with the target folder. Check if the new subsite folder combination is longer than the old one.

Try to copy the files/folder to the root of one of your disk drives to see that the files are OK.

Answer 2

I guess you are trying to cop/paste directly from one SP library explorer to other. You need to paste the file into you local system first than only you can copy to new library.

---

though you can use below powershell referenced from another Question OR Drag and Drop option here

I would prefer to go with Powershell

    // Get your source and destination libraries
SPList source = web.GetList(web.ServerRelativeUrl + @"/SourceDocLib");
SPList destination = web.GetList(web.ServerRelativeUrl + @"/DestinationDocLib");

// Get the collection of items to move, use source.GetItems(SPQuery) if you want a subset
SPListItemCollection items = items = source.Items;

// Get the root folder of the destination we'll use this to add the files
SPFolder folder = web.GetFolder(destination.RootFolder.Url);

// Now to move the files and the metadata
foreach (SPListItem item in items)
{   
    //Get the file associated with the item     
    SPFile file = item.File;
    // Create a new file in the destination library with the same properties
    SPFile newFile = folder.Files.Add(folder.Url + "/" +file.Name, file.OpenBinary(),file.Properties,true);
    // Optionally copy across the created/modified metadata                        
    SPListItem newItem = newFile.Item;
    newItem["Editor"] = item["Editor"];
    newItem["Modified"] = item["Modified"];
    newItem["Author"] = item["Author"];
    newItem["Created"] = item["Created"];

    // UpdateOverwriteVersion() will preserve the metadata added above. 
    newItem.UpdateOverwriteVersion();                              
}

Answer 3

I found the cause. The maximum allowed size is configured in windows registry.
Apparently it's a policy put in place as a security measure to ensure a misbehaving WebDav endpoint doesn't DOS/flood the client machine.

To change this setting on the client you need to edit the registry key at HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Services -> WebClient -> Parameters called FileSizeLimitInBytes. You can set this to any legal 32-bit value you wish. You may want to click on the Decimal type to make it easier to enter a value. The max value you can use in this key (4294967295) will allow you to transfer about a ~4GB file.

Once you have saved this key, you'll need to restart the WebClient windows service (or reboot your machine if you wish).
Default is 50MB:

I referred this blog.