Wednesday, March 16, 2016

ContentDeploymentJob issue : The remote server returned an error: (404) Not Found

This issue occures if your Export file size get increased. By default the allowd size is arround 52 Mb. If your export file size get increased with this limit then it will start problem with the content deployment job.

This issue mainly occures while Timerjob Transporting the Exported File to Deployment folder.

Error In ULS
ContentDeploymentJob.DoServerToServer(): caught exception 'System.Net.WebException: The remote server returned an error: (404) Not Found.  

Error in Event Viewer

Publishing: Content deployment job failed. Error: 'System.Net.WebException: The remote server returned an error: (500) Internal Server Error.

Here are steps to get rid of this issue

Note : Before doing any operation with the config file please take a backup of it.

Open the Config File of your central Admin
Search for
<requestLimits maxAllowedContentLength="52428800"/>
Change it to
<requestLimits maxAllowedContentLength="2147483647" />

Now Search for
<httpRuntime maxRequestLength="51200" requestValidationMode="2.0" />
Change it to
<httpRuntime maxRequestLength="1048576" requestValidationMode="2.0" />

Save the Config File of Central Admin

Now Open the Config File for Content Deployment Job

Path : C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\ADMIN\Content Deployment

Change the entries here as well for maxRequestLength and maxAllowedContentLength

Save the config file and try to run the content deployment job again. This time you will not get any error.




No comments:

Post a Comment