For some reason started getting the following message and pakaging stage:
Message: Internal Server Error
Exception Message: Server was unable to process request. ---> Tried
opening session with id: 8b02a8b1-adea-444a-9d54-dafbc4157e51. - There
is already an active session with id:
99f560a4-de72-4aed-9d14-c97f813e3d93 and there can only be one
Stack Trace: at
Umbraco.Courier.Core.TaskManager.GetSuccessfulProcessedTasks() at
Umbraco.Courier.UI.Dialogs.CommitItem.GetTask(String id)
The app recycling on the target server helped as a temporary solution.
What is the reason for this and can a permanent fix be applied? The current Courier instability (even after the latest patch applied) makes our content team frustrated.
I'm getting this after a succesfull test i'm kinda lost here, some help would be great, trying to convince my customer of the advantages but these bugs don't help
We have a client running Umbraco 7.5.9 and Courier 3.0.6 that just reported this problem. Looks like COU-332 was supposedly fixed with Courier 3.0.0? Has anyone else experienced this with a courier 3+ site?
We are running into this again with an Umbraco 7.10.4 site running Courier 3.1.6. Any ideas? We are able to reproduce errors when two different people courier nodes at the same time. The errors vary. This is one of them that comes up.
Getting error "There is already an active session with id" when trying to courier any content
For some reason started getting the following message and pakaging stage:
The app recycling on the target server helped as a temporary solution.
What is the reason for this and can a permanent fix be applied? The current Courier instability (even after the latest patch applied) makes our content team frustrated.
Also getting this error.
Does your page have a Umbraco Form on it?
Mine does, and it could be related to that. Did you find out what the problem is here?
I'm getting this after a succesfull test i'm kinda lost here, some help would be great, trying to convince my customer of the advantages but these bugs don't help
Hit the same problem. And yes, the site has umbraco forms on it.
Did you manage to resolve it?
We have a client running Umbraco 7.5.9 and Courier 3.0.6 that just reported this problem. Looks like COU-332 was supposedly fixed with Courier 3.0.0? Has anyone else experienced this with a courier 3+ site?
We are running into this again with an Umbraco 7.10.4 site running Courier 3.1.6. Any ideas? We are able to reproduce errors when two different people courier nodes at the same time. The errors vary. This is one of them that comes up.
is working on a reply...