Description

When uploading media items selecting the Overwrite existing media items and Make uploaded media items versionable check boxes, the fields from the unversioned template are not removed from the SharedFields table. As a result, the duplicate fields are stored in the SharedFields table and the VersionedFields table.

The issue might lead to:

• An unhandled exception when accessing the Folder tab of the parent media folder in the Content Editor:

  Exception: System.ArgumentException
  Message: An entry with the same key already exists.
  Source: System
     at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
     at System.Collections.Generic.TreeSet`1.AddIfNotPresent(T item)
     at System.Collections.Generic.SortedDictionary`2.Add(TKey key, TValue value)
     at Sitecore.Data.Items.MediaItem.GetMetaData()
     at Sitecore.Shell.Applications.Media.MediaFolder.MediaFolderForm.RenderItem(HtmlTextWriter output, Item item)
     at Sitecore.Shell.Applications.Dialogs.Folders.FolderBaseForm.RenderItems(HtmlTextWriter output, Item item)
     at Sitecore.Shell.Applications.Dialogs.Folders.FolderBaseForm.Render()
     at Sitecore.Shell.Applications.Media.MediaFolder.MediaFolderForm.OnLoad(EventArgs e)

• Versioned media items using the workflow defined in the unversioned template.

Solution

To resolve the issue, consider one of the following options:

• Upgrade your solution to Sitecore XP 10.4.0.
• For Sitecore XP 10.2.0, upgrade your solution to Sitecore XP 10.2.1.
• For Sitecore XP 10.3, download and install the pre-release as specified in KB1002844.

To mitigate the issue:

• Delete the unversioned media items manually in the Content Editor, and then upload those media items as versioned by selecting the Make uploaded media items versionable check box.
• Remove the duplicate fields by running the following SQL query: DeleteDuplicatesFromSharedFields.sql. You need to uncomment the DELETE statement, run the entire query against the Master database, and then restart the CM instance.

  Note: Make sure that you back up the Master database before running the query.