다음을 통해 공유


Content Deployment with MOSS2007: Remote Upload Request failed - Http 502 Proxy Error

This post is about a specific situation that may happen when doing Content Deployment with MOSS2007: Remote Upload Request failed - Http 502 (aka bad gateway)

The HTTP 502 Proxy Error

The content deployment job fails with: Content deployment job '<job name>' failed.The remote upload Web request failed.

The ULS log shows an entry

01/28/2009 09:58:09.07 OWSTIMER.EXE (0x0984) 0x0500 CMS Content Deployment 6p00 Critical

Failed to communicate with destination server for Content Deployment job '<job name>'. Exception was: 'System.Net.WebException: The request failed with HTTP status 502: Proxy Error ( The host was 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()'

How I could resolve it ?

On the server:

1. net stop sptimerv3

2. Interactively log-on as the Service Account.

3. Launched Internet Explorer, menu Tools \ Internet Options \ Connections \ LAN Settings : clear all check-boxes, including the “Automatically detect settings”

4. Logoff

5. Logon on as Admin

6. Net start sptimerv3

7. Start the Content Deployment job again

 

Blog4_IEProxySettings.jpg