Content Deployment Job Error - 404
Hi all, I'm quite new to this stuff and having an issue with content deployment from staging to production. The job fails as follows: SharePoint event: Content deployment job 'PR Content Deployment' failed.The remote upload Web request failed. Windows events: 5322 Failed to communicate with destination server for Content Deployment job 'PR Content Deployment'. Exception was: 'System.Net.WebException: The request failed with HTTP status 404: Not Found. 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 Microsoft.SharePoint.Publishing.Internal.Administration.ContentDeploymentRemoteImportSoapClient.CreateJob(String description, String sourceId, String destinationServerUrl, String destinationSiteCollection, SPIncludeSecurity includeSecurity, SPImportUserInfoDateTimeOption includeUserInfoDateTime, Boolean enableEventReceivers, Boolean fileCompression) at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.DoServerToServer()' 4958 Publishing: Content deployment job failed. Error: 'System.Net.WebException: The request failed with HTTP status 404: Not Found. 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 Microsoft.SharePoint.Publishing.Internal.Administration.ContentDeploymentRemoteImportSoapClient.CreateJob(String description, String sourceId, String destinationServerUrl, String destinationSiteCollection, SPIncludeSecurity includeSecurity, SPImportUserInfoDateTimeOption includeUserInfoDateTime, Boolean enableEventReceivers, Boolean fileCompression) at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.DoServerToServer() at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.ExecuteJob() at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.Run(Boolean runAsynchronously)' 4958 Publishing: Content deployment job failed. Error: 'System.Net.WebException: The request failed with HTTP status 404: Not Found. 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 Microsoft.SharePoint.Publishing.Internal.Administration.ContentDeploymentRemoteImportSoapClient.CreateJob(String description, String sourceId, String destinationServerUrl, String destinationSiteCollection, SPIncludeSecurity includeSecurity, SPImportUserInfoDateTimeOption includeUserInfoDateTime, Boolean enableEventReceivers, Boolean fileCompression) at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.DoServerToServer() at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.ExecuteJob() at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.Run(Boolean runAsynchronously) at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJobDefinition.Execute(Guid targetInstanceId)' 6398 The Execute method of job definition Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJobDefinition (ID 1331b35f-d35c-46b5-a0ca-f9a9fcad3072) threw an exception. More information is included below. The request failed with HTTP status 404: Not Found. I've restarted the servers (the path goes from the staging server to 1 of 2 CA servers) but no luck. Googled all over the place but cannot find a solution. Stumped - any help is greatly appreciated. Thanks
July 28th, 2010 5:32pm

Hi MCPSSPA, Did you install the following hotfixs? If not, please install them. Then check the effect. http://support.microsoft.com/kb/956057 http://support.microsoft.com/kb/956056 Next, check whether the central administration on both the source and destination servers are using host headers. If so, change to alternate access mappings of central admin , provide default zone as http://servername:port ,and intranet zone to use central admin original host header. After that, make some changes in IIS ,so that you can browse the central admin by server name and also with the host header. Do the same on destination server. Finally create a new content deployment path and job, check the effect. Regards, Rock Wang Microsoft Online Community Support
Free Windows Admin Tool Kit Click here and download it now
August 1st, 2010 6:49am

Thanks for the reply! Can you please elaborate? Niether of the hotfixes seem to apply to the 404 errors above. Can you go into more detail regarding the alternate access mappings and how they relate to the host headers. Confused, Thanks
August 10th, 2010 12:14am

** Bump ** Still trying to resolve this, anyone have ideas? More info: both the staging and production farms are FBA for the web apps and Windows auth for the CAs
Free Windows Admin Tool Kit Click here and download it now
August 19th, 2010 5:44pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics