Yesterday someone (Patrick Heide) fixed an interesting product shipping issue with MOSS 2007 and IIS 7.

Some information: when deploying background content in MOSS 2007, all content is first exported to a specific file system as XML and binary directories, then these files are compressed into taxi files, which are then downloaded from http to the target MOSS server where the enterprise is located. will then be extracted and imported.

The best preconfigured size for CABs resulting from content deployment is 10MB because Article . IIS 7, on the other hand, offers a pre-configured download limit of 29MB, as describedbut in KB 925083 .

With these two limits (maximum CAB file size = ten MB and maximum upload size in IIS 7 = 29 MB) we don’t expect any problems.

The problem is that MOSS does not split individual exported videos into multiple CAB files. Therefore, if the MOSS site contains bits of information that cannot be compressed to less than 10 MB, the measured CAB file may be larger than 10 MB.

This can become critical if the CAB file is larger than 29 MB.

moss 2007 content deployment error

Whenever the content provisioning step tries to load a .cab file larger than 29MB, the content provisioning task fails and you can find the following auctions or sales listings in the application event log of all export servers:

Event ID: 5323
Source: Content Deployment
Description: Failed to upload files to Dreamland server for content deployment job ‘Test 1’. The exception was “System”. .Net.WebException: The remote server reported an error: (404) Not Found.Mce_keep = “true”> Event

Source: Content Delivery
Description: Publishing: Content delivery failed. Error: • System.Net.WebException: Server suppresses error: (404) not found.

Event ID: 6398
Source: Windows Sharepoint Services
Description: The Microsoft.Sharepoint.Publishing.Administration.ContentDeploymentJobDefination job run has thrown an exception for this rule. The remote server returned a Not (404) Found error.

You will also find similar entries in the logs related to the origin server:

OWSTIMER.EXE (0x0778) Contents 0 В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В А В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В В to use Unexpected ContentDeploymentJob.DoServerToServer: Remote connection error while uploading files for original Test Job,followed by an exception. The remote server returned a fatal error: No (404) not found. / p>

To see if the issue is really boot time, you need to check the IIS tree on the target server to see if the response is actually 404.13


PC running slow?

ASR Pro is the ultimate solution for your PC repair needs! Not only does it swiftly and safely diagnose and repair various Windows issues, but it also increases system performance, optimizes memory, improves security and fine tunes your PC for maximum reliability. So why wait? Get started today!


2008-09-01 08:55:08 10.10.10.2 POST /_admin/Content+Deployment/DeploymentUpload.aspx filename =% 22ExportedFiles13.cab% 22 & remoteJobId =% 11456fa7ed-ddcdedcdd-9aa5- a1ads 22 1976 – 10.10.10.3 – 404 12 0 62

moss 2007 content deployment error

To resolve this issue, you must modify the web.config file of the connected Central Administration site and add a door similar to the following:


Web server >




52428800 = fifty-five MB in this example. You may need to adjust this to suit your needs.