Sign in
 
HomeOnline20132010Other VersionsRelated ProductsLibraryForumsGallery
Note: Forums will be making significant UX changes to address key usability improvements surrounding search, discoverability and navigation. To learn more about these changes please visit the announcement which can be found HERE.
TechCenter >
> 
> 
Content deployment job failed. The remote upload Web request failed.

Unanswered Content deployment job failed. The remote upload Web request failed.

  • Wednesday, March 31, 2010 10:48 AM
     
     
    Sign In to Vote
    0

    Error in Content Deployment

    Farm Topology

    Staging  Envirnment

    OS - Windows Server 2008 64 bit Edition
    MOSS Stand alone system - 64 bit with SP2

     

    Production Farm Environment 

    1 Moss WFE Server(64 bit with SP2)
    1 Moss App Server(64 bit with SP2),
    1 Sql Server
    OS - Windows Server 2008 64 bit in all the three servers


    Error Scenario

     

    Im doing a full content deployment from the staging environment to the production environment. The staging environment and the production environment are in different domains.

    I made entries in the host file in the source server(staging) and Iam able to browse the central admin in app server and blank site in webserver via browser by this I assume that the ports are opened and the host names are verified.

    In destination server (prod env)
    In centraladmin -> operations -> Content Deployment Settings I made, Accept incoming content deployment jobs
    I chose app server to be the import server as in the drop down it showed me only the app server name
    I chose not to encrypt option
    I Created the blank site using central admin and the blank site was created in the webserver.


    In Source Server (staging env)
    I chose Export server to be the source server, and I chose not to encrypt

    I create path, chose webapplication, I typed in destination(app) server url and entered username and password, clicked connect and connection succeeded

    I chose destination(webserver) webapplication that has blank site where the content will be deployed.

    Then I created job for the path to be the full deployment.

    I tested the job which was successful

    When I run the job Im getting the error

    Content deployment job <job name> failed. The remote upload Web request failed.

    When i see the event log it gives

    The Execute method of job definition Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJobDefinition (ID 991c5d6e-ddf4-4365-93bb-66b114cdbd53) threw an exception. More information is included below.

    The request failed with HTTP status 503: Service Unavailable.


    I checked and restarted the SharepointAdmin service and Timer service - both are running in sharepoint admin account (note : staging admin login is different production admin login)

    Note : I tested with the reverse scenario by doing content deployment from prod to staging, it worked... but staging to production is not working

    • Edited by Mike Walsh FIN Wednesday, March 31, 2010 11:58 AM Massive use of Bold for entire text after Error Scenario completely unnecessary and thus removed. Use Bolds sparingly.
    •  
     

All Replies

  • Wednesday, March 31, 2010 12:05 PM
     
     
    Sign In to Vote
    0

    Never post the same question to two or more forums. It wastes everyone's time.

    I have deleted your post made to the Setup..Admin forum.

    Please in future choose the forum you post to carefully and post any one question only once.

    (Moderator)

     

    FAQ sites: (SP 2010) http://wssv4faq.mindsharp.com; (v3) http://wssv3faq.mindsharp.com and (WSS 2.0) http://wssv2faq.mindsharp.com
    Complete Book Lists (incl. foreign language) on each site.
     
  • Tuesday, March 22, 2011 5:18 AM
     
     
    Sign In to Vote
    0

    Mike,

    In the past, I've followed a few posts from a google search where you have commented on someone posting twice but failed to find the second post on where there may be a possible answer,  In the future, I think it would be best if you also link the second post to the first one.

     

    Thanks,

    Troy

     
  • Tuesday, March 22, 2011 10:24 AM
     
     
    Sign In to Vote
    0

    Troy,

    It would be difficult to find the second post because I have deleted it at the same time I said not to post the same thing twice.

    It also would be pretty pointless looking for that second post because it has the identical text as the post I have left (although sometimes the Title was changed)

    Note that where time permits (and when merge works) I do try to Merge threads with identical starter posts when both the threads already have replies when I spot the duplication (so that no potentially valuable information is lost as would be the case if simply (and much quicker) one of the two threads was deleted).

    (Often after a merge, the original poster has later deleted the second copy of his post in a merged thread - so it might still look as if the second thread was not merged but deleted. Moderators can see that this has happened but you can't!)

    Mike

    SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx
    WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx
    Both also have links to extensive book lists and to (free) on-line chapters
     
  • Wednesday, August 31, 2011 5:51 PM
     
     
    Sign In to Vote
    0
    Content deployment uses both FQDN and NetBIOS name of destination computer for communications purposes.
    check if there was a problem accessing the destination NetBIOS name from the source farm due a non-applied proxy policies.