Uploading bigger files using CSOM

Question

Hi,

whenever i try to use this code

var myFile = new FileCreationInformation();
myFile.ContentStream = doc.ContentStream;
            
            using (ClientContext ctx = TokenHelper.GetClientContextWithAccessToken((string)request.Properties[hW], (string)request.Properties[aT]))
            {
                Folder destionationFolder = ctx.Web.GetFolderByServerRelativeUrl(destinationPath);
                ctx.Load(destionationFolder);
                ctx.ExecuteQuery();

                File uploadedFile = destionationFolder.Files.Add(myFile);
                ctx.Load(uploadedFile);
                ctx.ExecuteQuery();
            }

 I get the following error message:

"Specified argument was out of the range of valid values.\r\nParameter name: bytesToCopy"

Maybe there is another way to upload a file which is bigger than 2MB using the CSOM in combination with OAuth (SharePoint 2013/Office365?

best regards

Joerg

Answer 1

Maybe there is another way to upload files greater than 3 MB to Office 365 instances using the client object model?

Can somebody help me please?

regards

Joerg

Answer 2

Hi, You can try:

        public static void UploadFile(SP.ClientContext context, SP.Folder folder, string name)
        {
            using (FileStream fileStream = new FileStream("C:\\NewDocument2.docx", FileMode.Open))
            {
                SP.FileCreationInformation flciNewFile = new SP.FileCreationInformation();

                flciNewFile.ContentStream = fileStream;
                flciNewFile.Url = name;
                flciNewFile.Overwrite = true;

                SP.File uploadFile = folder.Files.Add(flciNewFile);

                context.Load(uploadFile);
                context.ExecuteQuery();    
            }
        }

Answer 3

Normally you can circumvent the 3MB limit by setting the MaxReceivedMessage size property that is described in http://gallery.technet.microsoft.com/The-Migration-Dragon-for-628acae0 That piece of code uses the server object model and you're not allowed to change this setting in Office 365. On premises, in 2013, you could use that. I built the tool for 2010, but here's the piece of sample code:

private void IncreaseMaxReceivedMessageSize()
 {
   int increaseSize = Convert.ToInt32(txtBatchSize.Text) * 1024 * 1024;
  
  SPWebService contentService = SPWebService.ContentService;    
  contentService.ClientRequestServiceSettings.MaxReceivedMessageSize = increaseSize;
  contentService.Update();  
}
 

---

Kind regards,
Margriet Bruggeman

Lois & Clark IT Services
web site: http://www.loisandclark.eu
blog: http://www.sharepointdragons.com

Answer 4

You can use SaveBinaryDirect instead of file.add("File");

using (ClientContext clientContext = TokenHelper.GetClientContextWithAccessToken((string)request.Properties[hW], (string)request.Properties[aT]))
            {
                
                Web web = clientContext.Web;
                
                List documentsList = null;

                
                    documentsList = clientContext.Web.Lists.GetByTitle(pstrListTitle);
                

                clientContext.Load(web, website => website.ServerRelativeUrl);
                clientContext.Load(documentsList, DocList => DocList.ForceCheckout);
                clientContext.ExecuteQuery();

             

                var fileCreationInformation = new FileCreationInformation();

                // Assign to content byte[] i.e. documentStream
                fileCreationInformation.Content = System.IO.File.ReadAllBytes(filePath);

                // Allow owerwrite of document
                fileCreationInformation.Overwrite = true;

                // Upload URL
                fileCreationInformation.Url = fileURL;
                
                using (FileStream fs = new FileStream(filePath, FileMode.Open))
                {
                    Microsoft.SharePoint.Client.File.SaveBinaryDirect(clientContext, strServerRelativeURL, fs, true);
                }

                clientContext.ExecuteQuery();
            }

Answer 5

I found a solution - it was a Problem with the MemoryStream:

               var myFile = new FileCreationInformation();
               using (var stream = content)
                {
                    stream.Seek(0, SeekOrigin.Begin); <-- The missing statement
                    myFile.ContentStream = stream;
                    myFile.Url                   =  FileName;
                    myFile.Overwrite         = true;

                    using (ctx)
                    {
                        Folder destionationFolder = ctx.Web.GetFolderByServerRelativeUrl(options.SPDestinationPath);
                        ctx.Load(destionationFolder);
                        ctx.ExecuteQuery();
                        File uploadedFile = destionationFolder.Files.Add(myFile);

                        ctx.Load(uploadedFile);
                        ctx.ExecuteQuery();
                    }
                }

Answer 6

SaveBinaryDirect() does not work with Office 365 / SPO.

It uses HTTP DAV and does not support Claims Authentication.