Table of Contents
Recently, some readers have informed us that they are facing a bug when releasing Moss 2007 content.
PC running slow?
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.
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
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
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!PC running slow?
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
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.
Yesterday, a colleague (Patrik Heide) resolved an interesting content delivery situation with MOSS 2007 and IIS 7.
Some background information: When deploying content in MOSS 2007, all blog posts are first exported to save the system in XML format, not to mention binaries, and then these personal data records are concatenated into CAB files, which are then sent to target via http MOSS Internet, computers are sent, from where they are then retrieved and sent.
The preconfigured maximum size of the pick CAB files that are generated during content deployment is ten MB, as in this class = “” Article . IIS 7, on the other hand, has a pre-configured download limit of 29MB, as described in the KB article 925083 .
With these many restrictions (maximum taxi report size = 10 MB and maximum article size in IIS 7 = 29 MB), we don’t expect any problems.
The existing problem is closed.This is because MOSS does not split the main exported files into multiple files. In the event that the MOSS site provides individual documents that cannot be compressed, so that they are less than 10 MB, the CAB file may grow larger than 10 MB. Will
This becomes critical if the CAB file is larger than 29 MB.
As soon as Content Deployment tries to load a CAB file larger than twenty-nine MB, the Content Deployment Workstation crashes, and you will find these entries specifically in the export server application event tree:
Event ID: 5323
Source: Content Delivery
Description: Uploading electronic files to the target server for content delivery after Test 1 fails. The exception was’ System.Net.WebException: Some remote servers returned error: (404) not found.
Event ID: 4958
Source: Content Message: Deploying
Description: The content deployment job failed. Error: “System.Net.WebException: remote, exact server returned error: (404) not found.
Event ID: 6398
Source: Windows Sharepoint Services
Description: An exception was thrown while executing the job definition method Microsoft.Sharepoint.Publishing .Administration.ContentDeploymentJobDefination. The remote server returned a specific “Not (404) Found” error.
You will also find similar entries in the ULS log on the origin server:
OWSTIMER.EXE (0x0778) Content 0 Deployment Deployment 0 Unexpected deployment while downloading remote ContentDeploymentJob.DoServerTo files available for original “Test” job, except … Remote website returned error: No (404) found “.
To see if the issue is really due to the download size, you need to check the IIS log on the target server to see if the response is actually the last one 404.13
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 13 0 Mce_keep = “true”> Up to 62
52428800 means 50 MB in this example. You will most likely need to change this to suit the specific needs of your business.
Improve the speed of your computer today by downloading this software - it will fix your PC problems.
Så Här åtgärdar Du Enkelt Moss Content Delivery Error 2007
Oto Jak łatwo Naprawić Błąd Dostarczania Treści Moss 2007
Aquí Se Explica Cómo Solucionar Fácilmente El Error De Entrega De Contenido De Moss 2007
So Beheben Sie Den Moss Content Delivery Error 2007 Ganz Einfach
Ecco Come Correggere Facilmente Moss Content Delivery Error 2007
Voici Comment Corriger Facilement L’erreur De Livraison De Contenu Moss 2007
Veja Como Corrigir Facilmente O Erro De Entrega De Conteúdo Do Moss 2007
Moss Content Delivery Error 2007을 쉽게 수정하는 방법은 다음과 같습니다.
Hier Leest U Hoe U Moss Content Delivery Error 2007 Gemakkelijk Kunt Oplossen