Posted on 25/11/2016 17:49:21
I have a few more updates. I have managed to get past the error above by Updating all Core packages and recycling the application pool a few times.
I also noticed that the control for saving the destination node for the new pages is not working properly. No matter what you choose, it will save a 0 value as PageID.
I have managed to edit the xml Job manually and it displays correctly in the Job definition.
But now I get a different error for both export and import of items.
2016-11-25 18:30:40.518: Starting job - ImportArticole.
2016-11-25 18:30:40.627: Job Failed with the following message: Object reference not set to an instance of an object.
at Dynamicweb.Environment.ExecutingContext.GetCulture(Boolean frontEnd) at Dynamicweb.Content.Items.ItemManager.CreateValueConverter(Boolean frontend) at Dynamicweb.Content.Items.Queries.Repository..ctor(ItemType metadata) at Dynamicweb.Content.Items.Queries.StorageFactory.CreateRepository(ItemType metadata) at Dynamicweb.DataIntegration.Providers.ItemDestinationWriter.GetExistingItemIdsDictionary() at Dynamicweb.DataIntegration.Providers.ItemDestinationWriter..ctor(Job job, Int32 rootPageId, Boolean importItemsAsParagraph, ItemList itemList, ILogger logger) at Dynamicweb.DataIntegration.Providers.ItemProvider.ItemProvider.RunJob(Job job)
2016-11-25 18:30:40.627: Finished job - ImportArticole.
2016-11-25 18:30:40.627: Batch failed.
Someone, please help me get past this one too.
Thanks,
Adrian