Hi folk, Im looking for some help or guidance to why im seeing this problem. I have a rather basic setup of umbraco V12, where we are currently using Nested Content. We are trying to convert these into Block Lists using the uSycn.Migrations tool. We don't have any custom types and everything is purely made using the UI, so no need for custom handlers etc. The problem im facing rigt know, is that when i run the import step after creating my migration (Nested content to blockList), it stops right after the import of DocTypes and gives me this error: This SqlTransaction has completed; it is no longer usable. I have tried to find the root cause, but i just can't seem to find the source of the problem. I have already gotten our SQL team to check if there are any issues on the database part, but they don't see any issues. Hopefully someone knows what to do. Thanks in advance. @Kevin Jump

Hi, i would say run this away from the database (e.g locally). if you take the 'normal' uSync files from the v12 site, and then use them to run the migration on a local site running v13 and uSync.Migrations you can remove the db as an issue and see if it still happens.

This is the full error message: "ContentTypeHandler": Import Failed : "System.InvalidOperationException: This SqlTransaction has completed; it is no longer usable. at Microsoft.Data.SqlClient.SqlTransaction.ZombieCheck() at Microsoft.Data.SqlClient.SqlTransaction.get_IsolationLevel() at Umbraco.Cms.Infrastructure.Scoping.Scope.get_Database() at Umbraco.Cms.Infrastructure.Persistence.Repositories.Implement.EntityContainerRepository.PerformGetAll(Int32[] ids) at Umbraco.Cms.Core.Cache.NoCacheRepositoryCachePolicy`2.GetAll(TId[] ids, Func`2 performGetAll) at Umbraco.Cms.Core.Services.ContentTypeServiceBase`2.GetContainers(Int32[] containerIds) at Umbraco.Cms.Core.Services.ContentTypeServiceBase`2.GetContainers(TItem item) at uSync.Core.Serialization.SyncContainerSerializerBase`1.GetFolderNode(TObject item) at uSync.Core.Serialization.Serializers.ContentTypeSerializer.SerializeCore(IContentType item, SyncSerializerOptions options) at uSync.Core.Serialization.SyncSerializerRoot`1.IsCurrent(XElement node, SyncSerializerOptions options) at uSync.Core.Serialization.SyncSerializerRoot`1.Deserialize(XElement node, SyncSerializerOptions options) at uSync.BackOffice.SyncHandlers.SyncHandlerRoot`2.ImportElement(XElement node, String filename, HandlerSettings settings, uSyncImportOptions options)"

Thanks Kevin, the problem is just that getting the data locally is not an option currently, as we can't share files with out Datacenter, as they are changing infrastucture.

(there is a download export button in uSync 😃 - i think its in v12)

Okay, then i im actually not sure if the problem itself lies in the migration or the import. The migration goes well and i have verfied the files to be fine, so it seems just to be the actual import part. My guess is that "import" is the original uSync.complete import operation as normal, and that is where the problem might be ?

yeah it might be - but i've not seen that error before 😦 it might be possible that when the content type is updates that it is triggering a larger content update inside umbraco (and for a lot of content that could be large)

That sounds possible. I will dig deeper. If i find the cuase of the problem, i will let you know for future references 😄