Error on Export Config

[MUM_dloew]

Hello,

I Have on vault Server 2012 a problem.

I tried to export the config of an Vault wich results with an Error.

08.11.2012 09:36:45 Reading configuration 'C:\ExpTempRoot\ExpTemp'
08.11.2012 09:36:45 Saving configuration 'C:\ExpTempRoot\ExpTemp'
08.11.2012 09:36:45 Saving configuration 'C:\ExpTempRoot\ExpTemp' - section 'PublishOptions'
08.11.2012 09:36:45 Saving configuration 'C:\ExpTempRoot\ExpTemp' - section 'UDP'
08.11.2012 09:36:45 Saving configuration 'C:\ExpTempRoot\ExpTemp' - section 'Lifecycle'
08.11.2012 09:36:45 Saving configuration 'C:\ExpTempRoot\ExpTemp' - section 'Revision'
08.11.2012 09:36:45 Saving configuration 'C:\ExpTempRoot\ExpTemp' - section 'Category'
08.11.2012 09:36:47 Saving configuration 'C:\ExpTempRoot\ExpTemp' - section 'EntityClassSupportedBehavior'
08.11.2012 09:36:47 Saving configuration 'C:\ExpTempRoot\ExpTemp' - section 'ContentSourcePropDefMapping'
08.11.2012 09:36:47 Saving configuration 'C:\ExpTempRoot\ExpTemp' - section 'EntityClassCategoryRuleSet'
08.11.2012 09:36:47 Fehler beim Anwenden der Konfigurationseinstellungen. Weitere Informationen finden Sie in der Protokolldatei.
08.11.2012 09:36:47 Connectivity.Application.VaultManager.ServiceException: ConfigurationError [232]  ---> Connectivity.Core.Exceptions.CoreException: ConfigurationError [232]  ---> System.ArgumentException: Das Element wurde bereits hinzugefügt. Schlüssel im Wörterbuch:ID_RULESET_DISPLAYNAME_PART. Hinzuzufügender Schlüssel: ID_RULESET_DISPLAYNAME_PART.
   bei System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)
   bei System.Collections.Hashtable.Add(Object key, Object value)
   bei Connectivity.Core.Configuration.SectionHandlers.EntityClassCategoryRuleSetSectionHandler.SaveHandler(IConfigSection section)
   --- Ende der internen Ausnahmestapelüberwachung ---

Server stack trace: 
   bei Connectivity.Core.Configuration.SectionHandlerUtil.InvokeHandler(IConfigSection section, ConfigurationContext context)
   bei Connectivity.Core.Configuration.Configuration.Save()
   bei Connectivity.Core.Services.KnowledgeVaultService.ExportConfiguration(String fullPathToExportFile)
   bei System.Runtime.Remoting.Messaging.Message.Dispatch(Object target, Boolean fExecuteInContext)
   bei System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]: 
   bei System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   bei System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   bei Connectivity.Core.Services.KnowledgeVaultService.ExportConfiguration(String fullPathToExportFile)
   bei Connectivity.Application.VaultManager.KnowledgeVaultService.ExportConfiguration(String fullFilePath)
   --- Ende der internen Ausnahmestapelüberwachung ---
   bei Connectivity.Application.VaultManager.KnowledgeVaultService.ExportConfiguration(String fullFilePath)
   bei Connectivity.Application.VaultManager.ExportConfigurationCommand.a(Vault A_0, String A_1)
   bei Connectivity.Application.VaultManager.ExportConfigurationCommand.OnExecute(ExplorerCommandContext context)

 can anyone help me?

[Olaf.Górski · Accepted solution]

Hello Daniel,

I assume, in your configuration there are two rules with same name for files and item respectively. Even you rename one of them, the GUID (in SQL) is still same, so will get this error.

Possible Workaround: Delete those roles and recreate it in ADMS and then export CFG file again. 

If it doesn’t help let us know It.

[scottmoyse]

---

@Olaf.Górski wrote:

Hello Daniel,

I assume, in your configuration there are two rules with same name for files and item respectively. Even you rename one of them, the GUID (in SQL) is still same, so will get this error.

Possible Workaround: Delete those roles and recreate it in ADMS and then export CFG file again. 

If it doesn’t help let us know It.

---

How hasn't this been fixed yet? It's been a known issue with importing and exporting configurations for years now, but it's still a problem!! Even with default Vault configurations its a problem. It's still happening in the latest build of 2016 come on guys!!