Getting this error when transferring nodes after 7.24 upgrade. Any suggestions?
error:System.TypeInitializationException: The type initializer for 'Nested' threw an exception. ---> System.NullReferenceException: Object reference not set to an instance of an object. at Umbraco.Courier.Persistence.V6.NHibernate.Persisters.DocumentItem.AvailableItems(ItemIdentifier itemId) at Umbraco.Courier.ItemProviders.DocumentItemProvider.AvailableSystemItems(ItemIdentifier itemId) at Umbraco.Courier.RepositoryProviders.Local.GetChildren(ItemIdentifier itemID) at Umbraco.Courier.Core.Packaging.RevisionPackaging.AddToQueue(ItemIdentifier itemId, Boolean includeChildren, Int32 maxDependencyLevel) at Umbraco.Courier.Core.Packaging.RevisionPackaging.AddToQueue(List`1 items, Int32 maximumDependencyLevel) at Umbraco.Courier.Core.Packaging.RevisionPackaging.AddToQueue(RevisionManifest manifest) at Umbraco.Courier.Core.Tasks.PackagingTask.Run() at Umbraco.Courier.Core.BackgroundTaskRunner`1.ConsumeTaskInternal(T task) --- End of inner exception stack trace --- at Umbraco.Courier.Persistence.V6.NHibernate.NHibernateProvider.CloseSession(String key) in f:\TeamCity\buildAgent\work\dd6b32efd8e6a004\Core\Umbraco.Courier.Persistence.V6.NHibernate\NHibernateProvider.cs:line 50 at Umbraco.Courier.RepositoryProviders.Local.Dispose(Boolean disposing) at Umbraco.Courier.RepositoryProviders.Local.Dispose() at Umbraco.Courier.Core.Repository.Dispose(Boolean disposing) at Umbraco.Courier.Core.BaseRevisionHandler.Dispose(Boolean disposing) at Umbraco.Courier.Core.BaseRevisionHandler.Dispose() at Umbraco.Courier.Core.Tasks.PackagingTask.Run() at Umbraco.Courier.Core.BackgroundTaskRunner`1.ConsumeTaskInternal(T task) 4/1/2015 2:46:53 PM
The type initializer for'Nested' threw an exception
So curious what 'Nested' actually is? In other words, could it be of a type that you don't have a data resolver for? I.e. Archetype or Nested Content? That would explain the error you see.
Not sure how else to say this. Whatever 'Nested' is is where you'll want to look. So investigate what you have that is named 'Nested' and verify it has an associated resolver if it's not a core type.
You say you have successfully deployed Archetype before, so you must have the custom resolver for that already.
Courier error after 7.24 upgrade
Hello,
Getting this error when transferring nodes after 7.24 upgrade. Any suggestions?
@jeff
What type of object is "Nested" in your revision?
Not sure I know what you mean Paul. I am trying to send a single node.
@Jeff
This line:
So curious what 'Nested' actually is? In other words, could it be of a type that you don't have a data resolver for? I.e. Archetype or Nested Content? That would explain the error you see.
I do use archetype but have not an issue before when transferring content nodes before the upgrade.
@jeff
Not sure how else to say this. Whatever 'Nested' is is where you'll want to look. So investigate what you have that is named 'Nested' and verify it has an associated resolver if it's not a core type.
You say you have successfully deployed Archetype before, so you must have the custom resolver for that already.
is working on a reply...