Courier 2.5 Extraction Error - Response is not well-formed XML
When using the Courier item from the content context menu, we are receiving conflicting messages. It says the item sucessfully transfered, but then later it says that there is an error Extracting an item. The message is as follows:
System.InvalidOperationException: Response is not well-formed XML. ---> System.Xml.XmlException: '', hexadecimal value 0x13, is an invalid character. Line 6, position -702.
However, as you read through the list of items is said it was packaging, it is including a package from a previous test in which case we were doing the same process, right clicking the context menu and using courier to package, extract and deploy new content onto the QA server. I cannot understand why when going to another section of the content tree (in our case a different website), and using the courier tool from the context menu is it still picking up the previous content push (which apparently had this error). I am missing how this works?
When you finish a task such as packaging or extraction, the task will stay in the taskmanager as a recently completed task, so if had a error 10 actions ago, those will still be in the list of processed tasks, the most recent packaging and extraction will be at the top of the list
Thank you for your response that makes more sense. However, we have another pressing issue with Courier where macros that contain content pickers as parameter which are embedded inside of the rich text editor do not transfer properly. I have seen in some of your courier change notes that this is fixed. Could you explain how this works. Perhaps we are not using the Courier tool as intended and thus causing this issue. Please advise. Thank you again.
Well facing the same Extraction error with Courier 2.5, tried setting folder permissions etc, didnt help.Here is stack trace, it does not help much though.Any clue on what im doin wrong?
System.InvalidOperationException: Response is not well-formed XML. ---> System.Xml.XmlException: '', hexadecimal value 0x13, is an invalid character. Line 6, position -710. at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args) at System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, Boolean expand, StringBuilder internalSubsetBuilder, Int32& charCount, EntityType& entityType) at System.Xml.XmlTextReaderImpl.ParseCharRefInline(Int32 startPos, Int32& charCount, EntityType& entityType) at System.Xml.XmlTextReaderImpl.ParseText(Int32& startPos, Int32& endPos, Int32& outOrChars) at System.Xml.XmlTextReaderImpl.ParseText() at System.Xml.XmlTextReaderImpl.ParseElementContent() at System.Xml.XmlReader.ReadElementString() at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadSoapException(XmlReader reader) 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) --- End of inner exception stack trace --- at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Umbraco.Courier.RepositoryProviders.WebServiceProvider.RepositoryWebservice.TransferResources(String sessionKey, ResourceTransfer[] resources, String user, String pass) in c:\Program Files (x86)\teamcity\buildAgent\work\2d3247b08adc3338\Umbraco.Courier.RepositoryProviders\WebserviceProvider\webservice.cs:line 1171 at Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.TransferResources(ResourceTransfer[] resources) in c:\Program Files (x86)\teamcity\buildAgent\work\2d3247b08adc3338\Umbraco.Courier.RepositoryProviders\WebserviceProvider\CourierWebserviceRepositoryProvider.cs:line 323 at Umbraco.Courier.Core.Extraction.RevisionExtraction.(Item item, Boolean isDependency, ResourceExtractionOrder order) at Umbraco.Courier.Core.Extraction.RevisionExtraction.() at Umbraco.Courier.Core.Extraction.RevisionExtraction.Extract() at Umbraco.Courier.Core.Tasks.ExtractionTask.Run() at Umbraco.Courier.Core.TaskManager.(IRevisionTask value) 28-11-2012 16:40:4
Courier 2.5 Extraction Error - Response is not well-formed XML
When using the Courier item from the content context menu, we are receiving conflicting messages. It says the item sucessfully transfered, but then later it says that there is an error Extracting an item. The message is as follows:
System.InvalidOperationException: Response is not well-formed XML. ---> System.Xml.XmlException: '', hexadecimal value 0x13, is an invalid character. Line 6, position -702.
However, as you read through the list of items is said it was packaging, it is including a package from a previous test in which case we were doing the same process, right clicking the context menu and using courier to package, extract and deploy new content onto the QA server. I cannot understand why when going to another section of the content tree (in our case a different website), and using the courier tool from the context menu is it still picking up the previous content push (which apparently had this error). I am missing how this works?
Hi Brittany
When you finish a task such as packaging or extraction, the task will stay in the taskmanager as a recently completed task, so if had a error 10 actions ago, those will still be in the list of processed tasks, the most recent packaging and extraction will be at the top of the list
Per,
Thank you for your response that makes more sense. However, we have another pressing issue with Courier where macros that contain content pickers as parameter which are embedded inside of the rich text editor do not transfer properly. I have seen in some of your courier change notes that this is fixed. Could you explain how this works. Perhaps we are not using the Courier tool as intended and thus causing this issue. Please advise. Thank you again.
Well facing the same Extraction error with Courier 2.5, tried setting folder permissions etc, didnt help.Here is stack trace, it does not help much though.Any clue on what im doin wrong?
Tks for the update,
Version 2.7.3 has a fix to this.
is working on a reply...