Courier 2 error - The type initializer for 'Nested' threw an exception
Hi,
I want to evaluate 'Courier 2' plugin on my local IIS.
I have copied all files from an existing working site onto my local. This site is in umbraco 7.2.8 and uses local .sdf files to store data.
With this, I have created 2 umbraco websites on my IIS with different names and separate app pools (.net 4.0 Integrated). Both these websites are currently identical and placed in 2 separate physical folders. I have also installed courier 2 on both sites and provided domains of the other site in each site.
However, when I made a small text change in one of the content page, published it and then clicked on 'Courier' icon, I get this message:
"This will deploy the selected node to http://site2.com
Should all pages below this one be included in the deploy, or is it only this single node you want to deploy?"
On that screen, when I click on 'Continue' button, I get this error:
Message: Internal Server Error
Exception Message: The type initializer for 'Nested' threw an exception.
Exception Type: System.TypeInitializationException
Stack Trace: at Umbraco.Courier.Core.TaskManager.GetSuccessfulProcessedTasks() at Umbraco.Courier.UI.Dialogs.CommitItem.GetTask(String id)
I have a test server and live, courier 2 installed and configured correctly, Umb v7.2.8, express licence.
Create a plain text page, publish with courier:
Message: Internal Server Error Exception Message: The type initializer for 'Nested' threw an exception. Exception Type: System.TypeInitializationException Stack Trace: at Umbraco.Courier.Core.TaskManager.GetSuccessfulProcessedTasks() at Umbraco.Courier.UI.Dialogs.CommitItem.GetTask(String id)
Do you, perhaps, have Nested Content in use? If so, you'll need to make sure your have the appropriate Courier Resolver present to handle the specific data for that type. You can find a community created resolver here:
Courier 2 error - The type initializer for 'Nested' threw an exception
Hi, I want to evaluate 'Courier 2' plugin on my local IIS.
I have copied all files from an existing working site onto my local. This site is in umbraco 7.2.8 and uses local .sdf files to store data. With this, I have created 2 umbraco websites on my IIS with different names and separate app pools (.net 4.0 Integrated). Both these websites are currently identical and placed in 2 separate physical folders. I have also installed courier 2 on both sites and provided domains of the other site in each site.
So, what I have done seems to be in line with this url: https://umbraco.com/follow-us/blog-archive/2011/11/17/how-to-evaluate-courier-25/
However, when I made a small text change in one of the content page, published it and then clicked on 'Courier' icon, I get this message: "This will deploy the selected node to http://site2.com Should all pages below this one be included in the deploy, or is it only this single node you want to deploy?"
On that screen, when I click on 'Continue' button, I get this error:
Message: Internal Server Error Exception Message: The type initializer for 'Nested' threw an exception. Exception Type: System.TypeInitializationException Stack Trace: at Umbraco.Courier.Core.TaskManager.GetSuccessfulProcessedTasks() at Umbraco.Courier.UI.Dialogs.CommitItem.GetTask(String id)
Can someone please help to resolve this?
hi
i'm getting the same thing.
I have a test server and live, courier 2 installed and configured correctly, Umb v7.2.8, express licence.
Create a plain text page, publish with courier:
turned on debug, nothing of note in the trace
Bumping this, anyone?
Do you, perhaps, have Nested Content in use? If so, you'll need to make sure your have the appropriate Courier Resolver present to handle the specific data for that type. You can find a community created resolver here:
https://github.com/display/Umbraco-courier-providers
Same approach applies if you are using Archetype, MultiUrl Picker and other "nested" types/
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.