I'm getting an "The event manager has been stopped." error after about 15 minutes of running an import job.
Message=One or more errors occurred.
at Mediachase.Data.Provider.TransactionScope.ExecuteActions(IEnumerable`1 actions)
at EPiServer.Commerce.Catalog.Provider.CatalogContentCommitterHandler.SaveVersionInternal(CatalogContentBase content, SaveAction action, String currentUser)
at EPiServer.Commerce.Catalog.Provider.CatalogContentCommitterHandler.Save(CatalogContentBase content, SaveAction action, String currentUser)
at EPiServer.Commerce.Catalog.Provider.CatalogContentProvider.Save(IContent content, SaveAction action)
at EPiServer.Core.Internal.DefaultContentRepository.Save(IContent content, SaveAction action, AccessLevel access)
at ETL.ProductImporter.ProductImporter.<>c__DisplayClass68_1.<UpsertCustomProduct>b__0() in C:\Projects\ETL\ProductImporter\ProductImporter.cs:line 887
Inner Exception 1:
InvalidOperationException: The event manager has been stopped.
Anyway to avoid this error? It's running from inside a Hangfire task instead of a scheduledJob.
error is throw when i call this code:
return contentRepo.Save(productToChange, SaveAction.Publish, AccessLevel.NoAccess);
You can try set this setting to false
<add key="episerver:DisableCatalogEventDrivenIndexing" value="true" />
If you do not need the event driven indexing
Quan, shouldn't that be set to true to disable event driven indexing? :)
Thanks @Quan I'm trying your solution but as you can imagine, it's a long import.
I'm getting a new, equally cryptic message now, so perhaps the app config flag is working, but now this... (still on 'contentRepo.Save')
System.AccessViolationExceptionHResult=0x80004003Message=Attempted to read or write protected memory. This is often an indication that other memory is corrupt.Source=<Cannot evaluate the exception source>StackTrace:<Cannot evaluate the exception stack trace>
Message=Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Source=<Cannot evaluate the exception source>
<Cannot evaluate the exception stack trace>
I may need a new forum post for this one :-S
Yes you should. I think you might try on a different machine to make sure it's not hardware related