Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
When using Courier 2.5 to push content from staging to live we are getting the following error during Extraction, anyone else had something similar and know what the problem may be?
Does the extraction complete even when this error is there?
Basicly it looks like it was trying to roll back a transaction but the transaction had already ended before it could do that.
Transactions can complete in 2 ways, either they complete and are committed to the DB, or they fail and are rolled back, if they time-out, connection is dropped etc, they should also rollback, or get dropped by the destination database.
Very bizarre, the transfer was definitely failing as these were new content nodes that were being migrated across and nothing was being created on live.
We carried out a manual package, copy, and extraction on one of the content nodes that was failing and this succeeded however since then everything is working fine! Each content node with sub pages that was originally failing is now migrating across without problem.
Obviously we will update you if it happens again but for the time being everything is working ok (hate intermittent problems).
Ok, keep me posted, if you see it happening again,
Nic also wrote me via email, my reply below for future reference:
"So from the top of my head, an issue could be the destination servers application pool restarting, as that will kill the transaction and the session nhibernate is using Basicly when you start a deployment from one location to another Courier creates 2 session tokens, one on each site, so it can ping status's back and forth and resumea nhibernate session, instead of having one long running request, it splits things into smaller chunks So if your destination site looses it's app pool or state in some way, Courier looses the transaction and session it was using. This is what I suspect is happening here, as ityou said it appears it works fine when doing a local deploy"
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted