Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Russell McGinnis 48 posts 183 karma points
    Jul 15, 2015 @ 17:15
    Russell McGinnis
    0

    The request failed with HTTP status of 404: Not Found...

    Any time I try to deploy a tree of content from one installation to another, as defined within our license... we get a log entry of:

    2015-07-15 10:04:08,175 [15] INFO Umbraco.Courier.Core.TaskManager - [Thread 22] Added PackagingTask behind queue of : 0 2015-07-15 10:04:08,175 [15] INFO Umbraco.Courier.Core.BackgroundTaskRunner1[[Umbraco.Courier.Core.Interfaces.IRevisionTask, Umbraco.Courier.Core, Version=1.2.5040.12670, Culture=neutral, PublicKeyToken=null]] - [Thread 22] Task added Umbraco.Courier.Core.Tasks.PackagingTask 2015-07-15 10:04:08,175 [15] INFO Umbraco.Courier.Core.TaskManager - [Thread 17] Starting PackagingTask with id: 712a919c-b493-47ed-9ad2-76a0ab5c2b88 2015-07-15 10:04:08,608 [15] DEBUG Umbraco.Courier.RepositoryProviders.Local - [Thread 17] Opening session: 6274dc5a-5b8b-4d7e-a6ca-e978501b3701 2015-07-15 10:04:08,608 [15] DEBUG Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider - [Thread 17] Opening session to http://dev.<MYDOMAIN>.com/umbraco 2015-07-15 10:04:08,698 [15] DEBUG Umbraco.Courier.Core.EventManager - [Thread 17] Unloading (count: 0) 2015-07-15 10:04:08,698 [15] ERROR Umbraco.Courier.Core.TaskManager - [Thread 17] Error PackagingTask with id: 712a919c-b493-47ed-9ad2-76a0ab5c2b88 2015-07-15 10:04:08,698 [15] ERROR Umbraco.Courier.Core.TaskManager - [Thread 17] An error occurred consuming task 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 Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.CloseSession(String sessionKey) at Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.Dispose(Boolean disposing) at Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.Dispose() at Umbraco.Courier.Core.Packaging.RevisionPackaging.Dispose(Boolean disposing) at Umbraco.Courier.Core.BaseRevisionHandler.Dispose() at Umbraco.Courier.Core.Tasks.PackagingTask.Run() at Umbraco.Courier.Core.BackgroundTaskRunner1.ConsumeTaskInternal(T task)

    We are at the moment trying to export content from our staging environment to our dev environment for better unit testing. Both environments are available on the same domain, dev.mydomain.com and staging.mydomain.com and are hosted on the same server.

  • Russell McGinnis 48 posts 183 karma points
    Jul 15, 2015 @ 17:39
    Russell McGinnis
    0

    After more investigation, we found our repository configurations to include "/umbraco" in the

  • Paul Sterling 718 posts 1534 karma points MVP 9x admin c-trib
    Jul 20, 2015 @ 21:30
    Paul Sterling
    0

    @Russell

    Was it that you included or did not include "/umbraco" in the repository Url?

    Which version is this with?

  • Russell McGinnis 48 posts 183 karma points
    Jul 20, 2015 @ 21:55
    Russell McGinnis
    0

    We had our repository entry setup in courier.config as follows:

    <repository name="http://www.mydomain.com" alias="http://wwwmydomaincom" type="CourierWebserviceRepositoryProvider" visible="true">
          <url>http://www.mydomain.com/umbraco</url>;
          <user>1</user>
    </repository>
    

    It was the url element that was the problem - for some reason when initially configuring courier we managed to have the "/umbraco" included. Once this was removed, it was plain sailing.

Please Sign in or register to post replies

Write your reply to:

Draft