DuplicateVaultGuid [217]

You are trying to attach a database to a Vault Server and you get this message in the ADMS Console Log.

30/01/2012 10:21:59 Connectivity.Application.VaultManager.ServiceException: DuplicateVaultGuid [217] (Vault, VaultX) ---> Connectivity.Core.Exceptions.CoreException: DuplicateVaultGuid [217] (Vault, VaultX)

Server stack trace:
at Connectivity.Core.Operations.AttachVault.AttachToMaster()
at Connectivity.Core.Operations.Attach.Execute(Boolean markForMigration)
at Connectivity.Core.Services.KnowledgeVaultService.AttachKnowledgeVault(String name, String datafile, String logfile, String filestore, Boolean markForMigration)
at System.Runtime.Remoting.Messaging.Message.Dispatch(Object target, Boolean fExecuteInContext)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Connectivity.Core.Services.KnowledgeVaultService.AttachKnowledgeVault(String name, String datafile, String logfile, String filestore, Boolean markForMigration)
at Connectivity.Application.VaultManager.KnowledgeVaultService.AttachKnowledgeVault(String name, String datafile, String logfile, String filestore, String dbUser, String dbPass)
--- End of inner exception stack trace ---
at Connectivity.Application.VaultManager.ProgressCommand.Execute()
at Connectivity.Application.VaultManager.AttachVaultCommand.OnExecute(ExplorerCommandContext context)

 

This can happen when the Database GUID already exists in the KnowledgeVaultMaster database. One scenario for this would that an ADMS Console backup was restored to two machines. Then the Administrator detaches the Vault from one machine and attempts to Attach it to the other Vault Server. It is maybe better depicted by this diagram.

 

Vault does not support attaching Vaults with duplicate ID's. The only solution to this issue is to use the bulk loading tool called the "Data Transfer Utility". The process would be to Export the data from the source server to a package folder, Create a new Vault data base on the destination server and then import the package folder.

Given the complexity of the data loading and the problems that could be faced the "Data Transfer Utility" is currently only availble from Autodesk Consulting or your Autodesk Value Added Reseller.

 

 

Comments

[Johannes Bauer]

I would rather like to change the vaultguid in the database ;-)

[Richard]

Yes I know, but thats not allowed. It wouldnn't be tested by QA and Autodesk cannot offer quick and dirty solutions to these sorts of unsupported issues. Wags finger ;-)