Copied to clipboard

Flag this post as spam?

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


  • Nate 143 posts 184 karma points
    Jun 26, 2011 @ 00:23
    Nate
    0

    Courier 2 Bug - Problem with extracting database information

    I get the following error all the time using courier 2 on 4.7.  It always seems to be a different node when this happens, but it happens a lot.

    There was a problem with extracting database information for the item: Name:Huffaker | Id:d4e8a947-12fd-4b0b-a817-c673994c02f4 | Provider:Documents

    Error details

     

    Umbraco.Courier.Core.Exceptions.ExtractionManagerException: There was a problem with extracting database information for the item: Name:Huffaker | Id:d4e8a947-12fd-4b0b-a817-c673994c02f4 | Provider:Documents ---> System.Threading.ThreadAbortException: Thread was being aborted. 
    at Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.ExtractItem(Item item, Boolean overwrite) 
    at Umbraco.Courier.Core.ExtractionManager.ExtractItemRevision(Item item, Boolean isDependency) 
    at Umbraco.Courier.Core.ExtractionManager.extractReadyRevisionBatch() 
    at Umbraco.Courier.Core.ExtractionManager.extractReadyRevisionBatch() 
    at Umbraco.Courier.Core.ExtractionManager.extractReadyRevisionBatch() 
    at Umbraco.Courier.Core.ExtractionManager.extractReadyRevisionBatch() 
    at Umbraco.Courier.Core.ExtractionManager.extractReadyRevisionBatch() 
    at Umbraco.Courier.Core.ExtractionManager.extractReadyRevisionBatch() 
    at Umbraco.Courier.Core.ExtractionManager.extractReadyRevisionBatch() 
    at Umbraco.Courier.Core.ExtractionManager.extractReadyRevisionBatch() 
    at Umbraco.Courier.Core.ExtractionManager.extractReadyRevisionBatch() 
    at Umbraco.Courier.Core.ExtractionManager.extractReadyRevisionBatch() 
    at Umbraco.Courier.Core.ExtractionManager.extractReadyRevisionBatch() 
    at Umbraco.Courier.Core.ExtractionManager.extractReadyRevisionBatch() 
    at Umbraco.Courier.Core.ExtractionManager.extractReadyRevisionBatch() 
    at Umbraco.Courier.Core.ExtractionManager.extractReadyRevisionBatch() 
    at Umbraco.Courier.Core.ExtractionManager.extractReadyRevisionBatch() 
    at Umbraco.Courier.Core.ExtractionManager.extractReadyRevisionBatch() 
    at Umbraco.Courier.Core.ExtractionManager.extractReadyRevisionBatch() 
    at Umbraco.Courier.Core.ExtractionManager.extractReadyRevisionBatch() 
    at Umbraco.Courier.Core.ExtractionManager.ExtractRevisions() 
    --- End of inner exception stack trace --- 
    at Umbraco.Courier.Core.ExtractionManager.ExtractRevisions() 
    at Umbraco.Courier.UI.Dialogs.CommitItem.TransferAndExtractOnSelectedRepo(String repo) 
    at Umbraco.Courier.UI.Dialogs.CommitItem.oneSteptransfer(Object sender, EventArgs e) 
    at System.Web.UI.WebControls.Button.OnClick(EventArgs e) 
    at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) 
    at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) 
    at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) 
    at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) 
    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

  • ossie 4 posts 24 karma points
    Jun 27, 2011 @ 16:18
    ossie
    0

    I'm having the same issue, any ideas how to resolve this?

     

    Thanks

  • Per Ploug 865 posts 3481 karma points MVP admin
    Jun 30, 2011 @ 13:06
    Per Ploug
    0

    its a thread time-out because courier is running in a web-app context, you can either increase the asp.net request timeout

    or do your deploys from a console client instead

    We're working on moving the deployment and packaging into a seperate process so it can't time-out

    /Per 

  • Scott McCown 15 posts 37 karma points
    Sep 27, 2011 @ 23:49
    Scott McCown
    0

    Hey Per,

    Thanks for the response (and for creating an awesome CMS). Is there any update on moving the deployment and packaging into separate processes? We're having this issue constantly and it's causing a significant amount of instability on the destination server. 

Please Sign in or register to post replies

Write your reply to:

Draft