Is there a Maximum file size that we can Courier across from one site to another? We have updated the maxRequestLength to 2097151 (2Gb) on both web config files but it seems to bomb out if we try a 44Mb file.
Smaller files seem to work OK.
A 15-16Mb file works OK.
We have even added a executionTimeout="999".
Here is the error that we are getting:
Unhandled exception occurred.
Status: 500
Message: error
ExceptionType: System.Net.WebException
Message: The request failed with the error message: --
Object Moved
This document may be found here --.
StackTrace:
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Umbraco.Courier.RepositoryProviders.WebServiceProvider.RepositoryWebservice.TransferResources(String sessionKey, ResourceTransfer[] resources)
at Umbraco.Courier.Core.Extraction.RevisionExtraction.TransferItemResources(Item item, ResourceExtractionOrder order)
at Umbraco.Courier.Core.Extraction.RevisionExtraction.TransferPreExtractResource()
at Umbraco.Courier.Core.Extraction.RevisionExtraction.Extract()
at Umbraco.Courier.Core.Tasks.ExtractionTask.Run()
at Umbraco.Courier.Core.BackgroundTaskRunner`1.ConsumeTaskInternal(T task)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Umbraco.Courier.Core.TaskManager.GetSuccessfulProcessedTasks()
at Umbraco.Courier.UI.Pages.ViewTaskManager.GetProcessed()
System.Net.WebException: The request failed with the error message:
Object Moved
This document may be found here
--.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Umbraco.Courier.RepositoryProviders.WebServiceProvider.RepositoryWebservice.TransferResources(String sessionKey, ResourceTransfer[] resources)
at Umbraco.Courier.Core.Extraction.RevisionExtraction.TransferItemResources(Item item, ResourceExtractionOrder order)
at Umbraco.Courier.Core.Extraction.RevisionExtraction.TransferPreExtractResource()
at Umbraco.Courier.Core.Extraction.RevisionExtraction.Extract()
at Umbraco.Courier.Core.Tasks.ExtractionTask.Run()
at Umbraco.Courier.Core.BackgroundTaskRunner`1.ConsumeTaskInternal(T task)
I've had to Courier files in excess of 200 MB every couple of months and they go off without a hitch. The two instances are connected by a fairly high speed connection though, so results likely vary with connection speed/reliability. In the end, a web service like this isn't meant to move huge files, but in this day and age a 44 MB file is not at all unreasonable. Not much help to you directly I'm afraid, just letting you know that it should be possible under ideal conditions according to my experience.
Max file size Courier can transfer
Hi,
Is there a Maximum file size that we can Courier across from one site to another? We have updated the maxRequestLength to 2097151 (2Gb) on both web config files but it seems to bomb out if we try a 44Mb file.
Smaller files seem to work OK.
A 15-16Mb file works OK.
We have even added a executionTimeout="999".
Here is the error that we are getting:
Unhandled exception occurred.
Status: 500
Message: error
ExceptionType: System.Net.WebException
Message: The request failed with the error message: --
Object Moved
This document may be found here --.
StackTrace:
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Umbraco.Courier.RepositoryProviders.WebServiceProvider.RepositoryWebservice.TransferResources(String sessionKey, ResourceTransfer[] resources) at Umbraco.Courier.Core.Extraction.RevisionExtraction.TransferItemResources(Item item, ResourceExtractionOrder order) at Umbraco.Courier.Core.Extraction.RevisionExtraction.TransferPreExtractResource() at Umbraco.Courier.Core.Extraction.RevisionExtraction.Extract() at Umbraco.Courier.Core.Tasks.ExtractionTask.Run() at Umbraco.Courier.Core.BackgroundTaskRunner`1.ConsumeTaskInternal(T task) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Umbraco.Courier.Core.TaskManager.GetSuccessfulProcessedTasks() at Umbraco.Courier.UI.Pages.ViewTaskManager.GetProcessed()
The Log files show this error:
2018-06-06 14:49:07,282 [39] DEBUG Umbraco.Courier.Persistence.V6.NHibernate.NHibernateProvider - [Thread 39] Closing session, UseGlobalSession: False, key: 9ef98db9-b78e-45ae-912b-32eef049cb36 2018-06-06 14:49:07,298 [39] ERROR Umbraco.Courier.Core.TaskManager - [Thread 39] Error ExtractionTask with id: ad451154-2769-4986-891d-36e2437d6b77
System.Net.WebException: The request failed with the error message:
Object Moved
This document may be found here --. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Umbraco.Courier.RepositoryProviders.WebServiceProvider.RepositoryWebservice.TransferResources(String sessionKey, ResourceTransfer[] resources) at Umbraco.Courier.Core.Extraction.RevisionExtraction.TransferItemResources(Item item, ResourceExtractionOrder order) at Umbraco.Courier.Core.Extraction.RevisionExtraction.TransferPreExtractResource() at Umbraco.Courier.Core.Extraction.RevisionExtraction.Extract() at Umbraco.Courier.Core.Tasks.ExtractionTask.Run() at Umbraco.Courier.Core.BackgroundTaskRunner`1.ConsumeTaskInternal(T task)Thanks
Jon
I've had to Courier files in excess of 200 MB every couple of months and they go off without a hitch. The two instances are connected by a fairly high speed connection though, so results likely vary with connection speed/reliability. In the end, a web service like this isn't meant to move huge files, but in this day and age a 44 MB file is not at all unreasonable. Not much help to you directly I'm afraid, just letting you know that it should be possible under ideal conditions according to my experience.
is working on a reply...