This is my 3rd attempt in as many years to give Courier a chance, not once have I ever had a working installation. This time I really need it and quick so I have the following setup:
development
staging
live
All 3 are in sync with regards to content.
I installed courier in dev and staging - no problems.
I setup locations in dev and staging - no child nodes have ever displayed
under the locations node in courier in any of my attempted installations
I create a new content node in dev and attempt to send to staging and get a timeout error for just one node! I scoured the documentation and find that I need to add a <timeout>30000</timeout> node to the settings node which I do on both ends and increase to 90000 and try again.
Next attempt results in the following exception
Error during packaging:
error:System.InvalidOperationException: Client found response content type of '', but expected 'text/xml'. The request failed with an empty response. 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.WebServiceProvider.RepositoryWebservice.OpenSession(String sessionKey, String username, String password) at Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.OpenSession(String sessionKey) at Umbraco.Courier.Core.Packaging.RevisionPackaging.openSessions() at Umbraco.Courier.Core.Packaging.RevisionPackaging.Package() at Umbraco.Courier.Core.Tasks.PackagingTask.Run() at Umbraco.Courier.Core.TaskManager.manageTask(IRevisionTask value) 18/03/2014 09:47:45
The logs are about as much use as a chocolate teapot because they only show the same exceptions you get on screen. So once again I hit a wall with no information to go on with regards to where the problem might lie. A third client has paid for a license for a product they cannot use.
So...I excluded the path to the webservice from any rewrite rules and Courier started packaging up a whole lot more content than just the node I selected but it didn't complete because I got another exception the same as the one in the original post which basically means another underlying exception was thrown somewhere, anyone's guess where. Unfortunately this time there was no 500 error in Fiddler however after a few attempts at running the deployment it then decided not to show an error any more and progressed to the next screen listing what will be deployed.
I thought I'd treat this as a dry run and accept the defaults even though there was much more in the package than I expected. It took some time and was looking promising until...
'Extracting [PageName]' was not completed, as it returned an error
Great - another error and no feedback as to what the problem was or what state my remote install has been left in as a result. So I tried running it again, this time there were less items in the package, presumably because it left it in an incomplete state the first time however the good news is that this time it completed successfully!
Whilst its great that I've finally completed my first deployment I have no confidence in what it actually has done or the fact that if I ask the customer to go ahead with their content updates on staging that they will be able to push them to the live server successfully.
I hope that something in this thread at least helps someone else in the same situation towards a solution to their problem.
Courier - 3rd Time Unlucky
This is my 3rd attempt in as many years to give Courier a chance, not once have I ever had a working installation. This time I really need it and quick so I have the following setup:
All 3 are in sync with regards to content.
<timeout>30000</timeout>node to the settings node which I do on both ends and increase to 90000 and try again.The logs are about as much use as a chocolate teapot because they only show the same exceptions you get on screen. So once again I hit a wall with no information to go on with regards to where the problem might lie. A third client has paid for a license for a product they cannot use.
Any help would be appreciated!?
Thanks
Having to dive into my toolbox now and inspect the traffic going back and forth to see if it turned anything up and found the following in Fiddler:
Request
Response
So at least that is something to go on now.
So...I excluded the path to the webservice from any rewrite rules and Courier started packaging up a whole lot more content than just the node I selected but it didn't complete because I got another exception the same as the one in the original post which basically means another underlying exception was thrown somewhere, anyone's guess where. Unfortunately this time there was no 500 error in Fiddler however after a few attempts at running the deployment it then decided not to show an error any more and progressed to the next screen listing what will be deployed.
I thought I'd treat this as a dry run and accept the defaults even though there was much more in the package than I expected. It took some time and was looking promising until...
Great - another error and no feedback as to what the problem was or what state my remote install has been left in as a result. So I tried running it again, this time there were less items in the package, presumably because it left it in an incomplete state the first time however the good news is that this time it completed successfully!
Whilst its great that I've finally completed my first deployment I have no confidence in what it actually has done or the fact that if I ask the customer to go ahead with their content updates on staging that they will be able to push them to the live server successfully.
I hope that something in this thread at least helps someone else in the same situation towards a solution to their problem.
Simon
is working on a reply...