VaultBCP tool error on import

VaultBCP tool error on import

mark.cloyed
Collaborator Collaborator
1,239 Views
1 Reply
Message 1 of 2

VaultBCP tool error on import

mark.cloyed
Collaborator
Collaborator

I am working in Vault Professional 2013 SP1 with the corresponding VaultBCP tool.  I have a production vault that resides in Japan on a server running a Japanese OS and an English version of Vault Pro.  I have taken a backup of that vault and restored it onto an English OS server with an English version of Vault Pro (no Japanese language pack installed).  I export the vault configuration successfully and I am successful running the VaultBCP to export the vault.  My destination server is an English OS with an English Vault Pro (no Japanese language pack installed).  I am successful importing the vault configuration.  When I compare the source and destination vaults, I see that both have UDPs having Kanji names.  The property definitions look to be correct in both vaults.  When I try to import using the VaultBCP, I receive an error of a property definition not found, and the error is displayed in a stack trace error.  I have listed the error below.  I note the file specified in the error.  When I look up that file in the export, I believe it is the first file that includes those property definitions in Kanji. 

 

I need to find a solution to this problem so that the vault merge can be completed.  Does anyone have experience here that can comment as to whether this is simply a language pack issue, of does the tool lack some sort of understanding of the destination environment?

 

Thanks,
Mark

 

Error below -----------------

 

Error: Cannot add file to vault ('69657.dwg'): Prop Def not found.

Exception: Prop Def not found.

Stacktrace:

Server stack trace:

   at Connectivity.Core.BusinessLogic.PropertiesCache._GetPropertyDefinitionsByIds(Int64 entityClassId, Int64[] propertyDefIds, Boolean throwIfNotFound)

   at Connectivity.Core.BusinessLogic.PropertiesBL.AddProperties(String entityClassName, Int64[] entityIds, Int64[] propDefIds, Object[] values, Boolean overwriteExisting, Boolean allowWriteToSystemPdef, Boolean catchValueConversionExceptions)

   at Connectivity.Document.Services.FileService.CommitHistoricalFile(Int64 fileMasterId, String comment, Int64 checkinUserId, DateTime checkinDate, DateTime lastWrite, FileClassification classification, Int64 categoryId, Boolean hidden, IDictionary`2 udps, Int64 revisionDefId, String revisionLabel, Int64 lcDefId, Int64 lcStateId, Stream fileStream, BOM bom)

   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)

   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.Document.Services.FileService.CommitHistoricalFile(Int64 fileMasterId, String comment, Int64 checkinUserId, DateTime checkinDate, DateTime lastWrite, FileClassification classification, Int64 categoryId, Boolean hidden, IDictionary`2 udps, Int64 revisionDefId, String revisionLabel, Int64 lcDefId, Int64 lcStateId, Stream fileStream, BOM bom)

   at VaultBCP.Vault.ImportUtil.AddFileIteration(Context ctx, Folder parent, IIteration iiteration, File& currentIteration)

   at VaultBCP.Vault.ImportUtil.AddFile(Context ctx, Folder parent, ICollection`1 iterations)

Regards,
Mark Cloyed
IMAGINiT Technologies
0 Likes
Accepted solutions (1)
1,240 Views
1 Reply
Reply (1)
Message 2 of 2

drobbie98
Advocate
Advocate
Accepted solution

I recently had a similar issue while using the VAULTBCP tool. I found there was a property from a vault many release older (2008 or 2009) and it would not transfer usinng the BCP tool.

To over come the issue I manually created the property in the new vault using the same parameters that existed in the old vault. I then re-ran the tool and it recognized the nnew property and populated it correctly.

 

Not sure if this is the same error you have but it might be worth a try.

 

Regards,

 

Douglas Robbie  

M2 Technologies | www.m2t.com | [email protected]

Main: 877.311.6284 | Support: 781-419-8163

 

facebook | twitter | linkedin | blog | youtube

 

Autodesk Gold Partner | Simulation Specialized | Consulting Specialized | PLM Specialized | Support Specialized

Edgecam Partner