Inventor Vault Project vs Single User Project

[bguillory2]

Afternoon,

We have been using a .Net app to generate Family of Parts components for a number of years to generate ipt/idw files without any issue. Recently we extended the support to also generate assemblies that consume the Family member ipt docs. 

Our issue is when we generate some assemblies with our eng team's standard Vault Project activated, Inventor will randomly crash when initially opening the assembly. However if we activate a Single-User project (with the same settings for workspace, templates, content center..etc ... as in the eng standard Vault project) the assemblies are generated without any issues. The only difference between the Single-User project and the standard Vault Project are the properties related to Vault.

Could someone explain exactly what different behavior a Vault Project has with Inventor vs using a Single-User project. Looking at the Vault Project xml  I see a reference to the Vault Server. My question is what interaction/ activity occurs using a Vault Project?

Any suggestions/insights into what may be causing our problem with generating assemblies with a Vault Project selected would be much appreciated.

Thanks

[bguillory2]

We are currently using Inventor 2020.1.1 build 239 with Vault 2020.1 build 25.1.55.0

[bguillory2]

Also thought it might help to describe the overall activity the app is performing. Basically it copies the a Master.iam document to a target folder assigning the new assemblies name. Then opens this copy and updates the parameters/features/components/mates as defined in our properties table. After applying all properties will Update and Save the new member .iam file.. Then repeats for next row in the table.

We have found our issue appears to be related to the Inventor Project's setting for Using Unique FileNames... In our company's standard Vault Project the option "Using Unique FileNames = Yes".

In our testing.. it appears if we set Using Unique Filenames = No ...then we are able to generate the assemblies as expected without any errors.

Possibly the issue may not be really related to Vault Projects and maybe related to only Using Unique Filenames settings.

Thanks

[WCrihfield]

Our organization has been using a common Vault type project for years, without actually having Vault installed yet.  We just didn't fill out the Vault area of the specs.  This way we can all share common settings, and libraries, because all files are stored on the network, and so are the libraries, Design Data, Catalog, external rules, VBA Project, etc.. We also do not allow duplicate file names within our entire directory.  Very rarely have any problems.  But we don't do alot of Database driven Automated design as of today.