We have been using Courier.v2.52.14 successfuly, until it stopped working all of a sudden, after a deploy.
Then, we have updated to Courier.v3.0.4 to see if that helps, but unfortunately it did not.
The errors we get are:,
2017-02-02 18:43:42,172 [34] ERROR Umbraco.Courier.Core.Extraction.RevisionExtraction - [Thread 8] There was a problem with extracting database information for the item: Name:**censored** | Id:**cencored** | Provider:Dictionary items
System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> A call to SetContextId must occur before getting/setting a context
And
2017-02-02 19:46:48,723 [66] ERROR Umbraco.Courier.Core.TaskManager - [Thread 74] Error ExtractionTask with id: 4364d761-1515-4370-9a70-ac95303ce754
System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Tried setting Core.ContextId to 3e2e784e-5cf1-47e3-9916-2ad8a29d783d - There is already an active global execution context with id: 55ccf5c2-8601-47b4-808c-5ebc86d06d0e and there can only be one
We are getting these after the comparison between the environments, i.e., we get the list of items that will be sent, and sometimes we are able to see the progress bar (Deploying xyz). After all, instead of the success message, we get the error.
We have tried restarting the sites, clearing App_Data, reinstalling Courier after a fresh deploy, adding the assembly redirect mentioned here, none of which worked.
We are not using NHibernate ourselves, and we have checked that the NHibernate related dlls only get created upon Courier installation. We are not using any other package that might cause conflicts.
Our site is running on Umbraco v7.5.6, and we are trying to move data from a single server (no load balancing) to a load-balanced environment's master server. Both environments are Azure WebApps (paas) with Azure sql server connections.
There is a warning before the "tried setting Core.ContextId" error, as the following:
Found out the reason for this was that the load-balanced setup on the target environment was wrong. Anyone that runs into similar issues, make sure that the url to which you are sending data is served by only one instance (duh!)
I guess this might go as a subcategory for rubber duck debugging.
Courier Failing with ContextId issues
Hey there,
We have been using Courier.v2.52.14 successfuly, until it stopped working all of a sudden, after a deploy.
Then, we have updated to Courier.v3.0.4 to see if that helps, but unfortunately it did not.
The errors we get are:,
And
We are getting these after the comparison between the environments, i.e., we get the list of items that will be sent, and sometimes we are able to see the progress bar (Deploying xyz). After all, instead of the success message, we get the error.
We have tried restarting the sites, clearing App_Data, reinstalling Courier after a fresh deploy, adding the assembly redirect mentioned here, none of which worked.
We are not using NHibernate ourselves, and we have checked that the NHibernate related dlls only get created upon Courier installation. We are not using any other package that might cause conflicts.
Our site is running on Umbraco v7.5.6, and we are trying to move data from a single server (no load balancing) to a load-balanced environment's master server. Both environments are Azure WebApps (paas) with Azure sql server connections.
There is a warning before the "tried setting Core.ContextId" error, as the following:
One note, though the dll has the name
The logs contain V6 source, such as the following:
But I guess that is just an old naming of the namespace still lingering.
Thanks in advance,
Found out the reason for this was that the load-balanced setup on the target environment was wrong. Anyone that runs into similar issues, make sure that the url to which you are sending data is served by only one instance (duh!)
I guess this might go as a subcategory for rubber duck debugging.
I am having similar issues, with a single server that is behind a ELB.
is working on a reply...