Content Deployment – 404 error

With my 2nd post I want to tell you the story of a content deployment problem running on Windows Server 2008 with IIS 7.

In a simple description content deployment runs in these phases:

1. Data export
2. Compressing data
3. Transmit data to target
4. Import data

In SharePoint UI I get the following error in the third phase “Transmitting”

“The remote server returned an error: (404) Not Found.”

On the source server I found in the application event log:

Event ID: 5323
Content Deployment
DESC: Failed to transfer files to destination server for content deployment job ‘test 1’.
Exception was ‘System.Net.WebException: The remote server returned an error: (404) Not Found.

Event ID: 4958
Content Deployment
Publishing: Content deployment job failed. Error: ‘System.Net.WebException: The remote server returned an error: (404) Not Found.

Event ID: 6398
Windows Sharepoint Services
The Excecute method of job definition Microsoft.SHarepoint.publishing.administration.contentdeploymentjobdefination threw an exception.
To get more details let’s take a look in the ULS logs:

ULS Logs:
47:25.0 OWSTIMER.EXE (0x0778) 0x079C CMS Content Deployment 1gfb Verbose Uploaded file ‘C:\Windows\TEMP\ContentDeployment\30ab9ac4-9d6a-4674-a6d3-a4c95b482786\’ to ‘http://mossapp01:1976//_admin/Content Deployment/DeploymentUpload.aspx?filename=””&remoteJobId=”ab4d501b-a691-4278-aa8b-4d09c75d430a”‘

47:25.0 OWSTIMER.EXE (0x0778) 0x079C CMS Content Deployment 1gfa Verbose Uploading file ‘C:\Windows\TEMP\ContentDeployment\30ab9ac4-9d6a-4674-a6d3-a4c95b482786\’ to ‘http://mossapp01:1976//_admin/Content Deployment/DeploymentUpload.aspx?filename=””&remoteJobId=”ab4d501b-a691-4278-aa8b-4d09c75d430a”‘

Source: 47:25.3 OWSTIMER.EXE (0x0778) 0x079C CMS Content Deployment 0 Unexpected ContentDeploymentJob.DoServerToServer: Remote connection failed while uploading files for source-Job ‘Test 1’ with exception ‘The remote server returned an error: (404) Not Found.’

As result of the ULS logs we see the error is not inside the SharePoint, it’s here:

Exception was: ‘System.Net.WebException: The remote server returned an error: (404) Not Found. at System.Net.HttpWebRequest.GetResponse() at

That means it’s one layer below of sharepoint. As next step we need to focus on the target server.

Let’s check the IIS logs on the target server: (central admin web application)

200X-XX-XX 08:55:08 POST /_admin/Content+Deployment/DeploymentUpload.aspx 1976 – – 404 13 0 62

Ok, in the IIS logs we have the http 404.13 that means “CONTENT_LENGTH_TOO_LARGE”.

Mhnnn, now we need to know the package size, is the package really to large?

Answer: all file have a size between 10 until 13 MB but the 17th file is 35 MB.

Ok, now let’s find the solution.

On the source server, the whole content will be exported and compressed into cab-files. Default setting is 10 MB per package. Our “bad” package a size of 35 MB.
Why the package get a 404.13 on IIS 7?


IIS 7 has as default upload size of 28 MB. That means we need to increase the upload size in IIS 7.


Go to the target content deployment server. Modify the web.config from central admin web application. I would suggest setting the upload size to 52 MB.

Add in the tag configuration the lines:



      <requestLimits maxAllowedContentLength=”52428800″/>

Ok, lets answer the best question: Why can this happen?

In the phase 2 “compression data”. MOSS does not split single exported files into multiple CAB files. So in case that the MOSS site contains single documents which cannot be compressed to less than 10 MB then the cab file can be bigger then 10 MB. Lets check the files on the content source: I have a ppt file with a size of 43 MB with many pictures inside. That means this file cannot be compressed to 10 MB, and in my result not under the size of 28 MB.

For the future be aware of your biggest file size when using content deployment. Lets focus on file which can not be compressed like mp3, bmp, jpeg…



Comments (0)

Skip to main content