When trying to permanently delete the "EN" (empty) folder from my local SnWebApplication.Api.Sql.TokenAuth with the admin-ui, the following error was thrown. Any other delete operations were successful. The content is available on the direct OData API. The server restart fixed this problem.
Message: An item with the same key has already been added. Key: Description
Category: General
Priority: -1
EventId: 1
Severity: Error
Title:
Machine: SNPC016
Application Domain: SN
Process Id: 32884
Process Name: SnWebApplication.Api.Sql.TokenAuth
Managed Thread Id: 85
Thread Name: .NET ThreadPool Worker
Extended Properties: Messages - ArgumentException: An item with the same key has already been added. Key: Description
at System.Collections.Generic.Dictionary`2.TryInsert(TKey key, TValue value, InsertionBehavior behavior)
at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
at SenseNet.ContentRepository.Storage.NodeData.GetAllValues() in D:\dev\github\sensenet\src\Storage\NodeData.cs:line 1061
at SenseNet.ContentRepository.Storage.Node.CollectAllProperties(NodeData data) in D:\dev\github\sensenet\src\Storage\Node.cs:line 2785
at SenseNet.ContentRepository.Storage.Node.ForceDeleteAsync(CancellationToken cancel) in D:\dev\github\sensenet\src\Storage\Node.cs:line 4307
at SenseNet.ContentRepository.TrashBin.ForceDeleteAsync(GenericContent n, CancellationToken cancel) in D:\dev\github\sensenet\src\ContentRepository\TrashBin.cs:line 223
at SenseNet.ContentRepository.GenericContent.DeleteAsync(Boolean bypassTrash, CancellationToken cancel) in D:\dev\github\sensenet\src\ContentRepository\GenericContent.cs:line 1684
at SenseNet.Services.Core.Operations.ContentOperations.DeleteBatch(Content content, HttpContext httpContext, Boolean permanent, Object[] paths) in D:\dev\github\sensenet\src\Services.Core\Operations\ContentOperations.cs:line 601
=====================
When trying to permanently delete the "EN" (empty) folder from my local SnWebApplication.Api.Sql.TokenAuth with the admin-ui, the following error was thrown. Any other delete operations were successful. The content is available on the direct OData API. The server restart fixed this problem.