Autodesk Vault 2017 Products

This file contains information that became available prior to releasing Autodesk Vault 2017 or that you will find useful while using Autodesk Vault 2017.

For the latest version of this file please see the Autodesk Vault Products Release Notes Page

System Requirements for all Vault products are accessible through the Vault install and www.autodesk.com/vault-system.

DISCLAIMER: Migrating data from a Beta product to the released product is not supported.

Autodesk Data Management Server Install Information

• If you have previous Beta Vault products installed on your machine, you will need to uninstall them prior to installing this release.

1. Uninstall the client software from all machines.
2. Open the Beta ADMS Console.
3. Delete all vaults and libraries.
4. Delete the master vault.
5. Uninstall ADMS.
   

• If Vault 2017 has been downloaded from the web, ensure that the extracted files from the previous releases have been removed before extracting Vault 2017.
• Vault 2017 ADMS requires ASP.NET 4.6 be enabled when installing IIS on the system. If you encounter an error during ADMS installation, go to Start > Control Panel > Programs > Turn Windows features on or off > .NET Framework 4.6 Advanced Services and enable ASP.NET 4.6.
• Autodesk Vault 2017 installs .NET 4.6 to your operating system.
• To avoid potential install failure when installing Autodesk Vault 2017, make sure the following Microsoft updates are installed on your machine before starting the installation.
  Windows 2012 R2: KB2919442; KB2919355
• Removing Autodesk Data Management Server will not remove vault data. If you remove Autodesk Data Management Server, the SQL server directory and file stores will remain intact. However, Autodesk strongly recommends backing up all databases and necessary files prior to removing Autodesk Data Management Server.
• By default, Autodesk Data Management Server communicates using port 80. Some installed software running on port 80 can cause conflicts with Autodesk Vault communication. To avoid conflicts when installing the ADMS console, configure ADMS to use an open port between 1 and 65535.
• If you are planning on using Windows authentication within Vault Professional when using Windows Server Operating Systems, the "Windows Authentication" service for IIS must be installed.
• When installing the ADMS console on a machine that uses a custom default web site and port 80, one of the following steps is recommended:
  • Change the port of the Default Web Site to another number and restart the server installation.
  • Remove the default web site and restart the server installation.
• When using a remote SQL server, you will have to configure the Remote SQL settings during the installation process.
• It is recommended that you allocate the recommended or higher system requirements when running Autodesk Vault 2017 in virtual environments. As virtual environments could cause unexpected consequences, Autodesk reserves the right to ask that any customer reported problems be reproduced on a physical machine outside of the VMware environment. Autodesk Vault 2017 was tested on VMware ESXi version 5.0 and VMware Workstation versions 9.0.1 and 10.​​
• For information on certified virtualization vendors and their respective solutions, see Microsoft’s products list at Server Virtualization Validation Program home page.
  • Microsoft’s support policy for Microsoft software running in non-Microsoft hardware virtualization software can be found here.
  • Microsoft’s support policy for Microsoft SQL Server products running in a hardware virtualization environment can be found here.
    

SQL Server Install Information

• Vault Workgroup and Vault Professional ADMS install 64 bit SQL Express 2012 SP2.
• An issue has been discovered with SQL access after .NET 4.6 has been installed on the same machine. The issue found is that the Vault Server will be unable to connect to the SQL Database Engine using the TCP protocol when the Vault Server and the SQL database engine are installed on the same machine. Until a Microsoft fix is available, it is recommended that you edit the protocol priority in the SQL Configuration manager. In the manager, place Shared Memory first followed by TCP then Named Pipes. Make sure the that Shared Memory protocol is enabled for this to work properly.​
• When installing Vault Server using Local Language on Local O/S, the following message may appear: "This SQL Server setup media does not support the language of the OS, or does not have the SQL Server English-language version installation files. Use the matching language-specific SQL Server media; or install both the language specific MUI and change the format and system locales through the regional settings in the control panel." Reference Microsoft Link for more information.
  

• Autodesk Vault functions in a SQL failover cluster configuration in which it is unaware of the cluster and does not require reconfiguration of Vault if and when a failover occurs. This is known as the AlwaysOn Failover Cluster Instances (FCI). More information about this configuration can be found at AlwaysOn Failover Cluster Instances. Before configuring this feature, Windows Server must be configured for Windows Server Failover Clustering (WSFC). When using Vault within a SQL failover cluster environment, workflows occurring during a failover may be interrupted and require repeating the workflow. ​
  

• If your computer/domain is set up to require strong/complex passwords, you will not be able to use the default SQL SA password used by the Autodesk installer. Please use the Configuration pagestin the Autodesk Data Management Server install to specify an appropriate SA password. Check with your IT administrator to get the requirements for a strong/complex password.
• When using a non SQL SA account to install Vault 2017 Server, ensure that the user has been granted sysadmin privileges.
• When using the Default SQL Express 2012 SP2 in the Vault 2017 Server installer, it is not possible to use a non SQL SA account to install.
• When using SQL Server 2014, all databases must remain at the SQL 2012 compatibility level. New databases created using the ADMS Console will be set for 2012 compatibility level automatically.
• Installing SQL onto a computer that has the Program Files folder compressed is not supported and will cause the install to hang.
• Autodesk Vault 2017 installs SQL Express 2012 SP2 using the Network Service account for SQL services. SQL Express 2012 SP2 cannot be installed on a domain controller under a local service account or a network service account.
• For security reasons, Microsoft recommends that you do not install SQL Server on a domain controller http://msdn.microsoft.com/en-us/library/ms143506.aspx.

IIS Install Information

• If intending to use Windows Authentication when logging into Vault, the Windows Authentication checkbox in IIS must be enabled. See Technical Solution TS15739768 for more information.

Migration - Working with Legacy Vault Data

• If you are migrating from any previous release, Autodesk strongly encourages reviewing and understanding the readme of each version of Vault being skipped, including this readme.
• When upgrading from a previous release of Vault Server, it is strongly recommended that you perform a backup first.
  • In order to create the backup in a connected workgroup environment, all files should be replicated to the publisher. To do this, log in to the ADMS Console on the publisher and select each site one at a time and select “Replicate Site Now” via a Right Mouse Button click. This may take time to complete and the backup should be done after all replication is complete.
• Detaching a Vault and attaching it to a new server installation without also attaching the KnowledgeVaultMaster is not supported and will lose all non-default users and corresponding data. All detach and subsequent attach cases should include all Vaults as well as the KnowledgeVaultMaster.
• When migrating large vaults, there may be a long delay before the progress dialog is shown. The delay can exceed 10 minutes depending on the configuration of the vault.

• Migrating from one OS to another OS when OS formatting (Regional Settings) is different between the two is NOT supported. Prior to upgrading to ADMS 2017, OS formatting on the target server must be changed to match that of the originating server.

• When performing an in-place upgrade from previous releases of ADMS with Content Center Libraries, the existing Content Center Libraries must be migrated prior to installing the new Content Center Libraries.

Support for Prior Vault Clients and Add-Ins

• The Vault 2017 ADMS supports the use of any Vault 2015 release, Vault 2015 R2, and Vault 2016 release clients which match the Vault edition of ADMS.
• The Vault 2017 ADMS supports the use of any Vault 2015 release, Vault 2015 R2, and Vault 2016 release Add-Ins.
  
• It is not recommended to administer Vault or Global settings through an older client. All administration of Vault and Global settings should be done through ADMS Console or a Vault client of the same release as the Vault server.
• New functionality available in Vault 2017 will not be available in prior releases of Vault clients and add-Ins.

• Some functionality in a Vault 2017 client may not work when only an older version of the CAD application is installed or if an older version of the CAD application was last run. Running Inventor View 2017 or the 2017 version of the CAD application and then retrying the operation may resolve the issue.

ADMS Information

• Property indexing for AutoCAD file types may not work if the AutoCAD based product is installed on the same machine as the Vault Server (ADMS). If indexing problems are encountered, a repair on the ADMS Console installation should resolve the issue.
• ​There are some instances whereby the Content Index Service does not work after an Upgrade/Migration has been performed. Ensure that the Autodesk Job Dispatch Service is restarted and running after an Upgrade/Migration has been performed.

• When the Vault Server (ADMS) and Vault Client are installed on the same x64 machine, the Client should be installed after the Server (ADMS) install. Otherwise certain Vault client operations (e.g., Batch Plot, Update View) may result in an error.

• In order to view PDF thumbnails an iFilter must be installed on the server. A PDF viewer such as PDF-Xchange Viewer may be used to enable PDF thumbnails. Any viewer should be installed after Adobe Reader on the server machine. A reboot and Re-Index of File Properties is also required after the viewer is installed.
• Units of Measure conversion factors are now processed and stored as double precision values. Previously Units of Measure conversion factors were processed and stored as single precision values. As a result migrated vaults containing custom Units of Measures will have their conversion factors displayed as double precision and may not show the exact same value as displayed in previous releases. For example, an existing custom Units of Measure with a conversion factor displayed as 3 in a previous release will now be displayed as 2.99999991059304. However a newly created custom Units of Measure with a conversion factor of 3 will be displayed as 3.
  System Units of Measure conversion factors will be migrated to have the correct double precision conversion factor.
• In Vaults being migrated from previous releases where lifecycle states did not have a control bit set, the states will now have a control bit set for first and last iterations moving forward (e.g., Item Release Process, Work in Progress, and In Review States).
  Users migrating from 2015 R2 who have explicitly set no control bit on specific states will need to re-apply this configuration after migration.​
• The IBM Sizing Guide is no longer available. The IBM Sizing Guide topics in the installation help are incorrect.

• Please refer to this page for Vault File Server Installation and configuration instructions www.autodesk.com/help-vault-install-download-fileserverexe-2017-enu
• The Autodesk Vault File Server (AVFS) 2017 installer may crash when upgrading from Autodesk Vault File Server 2015/2016 using a custom (non-default) port. To proceed, add the following key into the server’s Windows Registry before starting the upgrade procedure:
  
  Registry Key:
      On servers with Autodesk Vault File Server 2015 installed: HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\PLM\Autodesk Vault File Server 19.0\Install
      On servers with Autodesk Vault File Server 2016 installed: HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\PLM\Autodesk Vault File Server 21.0\Install
  Registry Value(String): IISWEBSITENAME
  Registry Data: Autodesk Data Management

Return to Top

Vault Client

Vault Client Install Information

• If Vault 2017 has been downloaded from the web, ensure that the extracted files from the previous releases have been removed before extracting Vault 2017.
• Please visit the Vault Online Help for the full list of applications for which there are supported Vault Add-ins.
• Sample files are now available at www.autodesk.com/vault-samples
• Autodesk Vault 2017 installs .NET 4.6 to your operating system.
• If you encounter any error during .Net 4.6 installation on Windows 8.1, reboot your machine and try the installation again. For more information, please refer to Microsoft support page.
• To avoid potential install failure when installing Autodesk Vault 2017, ensure following Microsoft updates are already exist on your machine before starting the installation.
  Windows7: KB 2533552
  Windows8.1/Windows 2012 R2: KB2919442; KB2919355
  
• It is recommended that you start Autodesk Design Review after installation and check for any updates.
• Autodesk Vault 2017 supports side-by-side client installations with Autodesk Vault 2015, Autodesk Vault 2015 R2, and Autodesk Vault 2016.
• To install Vault 2017 add-ins, ensure add-ins are checked during the installation. By default they are not checked.
• Vault Add-Ins for supported CAD applications can only log into the edition of the Vault Server that matches with the edition of the Vault Client from which the Add-Ins are installed. For example, if you have a Vault Basic Client installed on your workstation, you cannot log into Vault Workgroup or Vault Professional Server from Inventor. You will have to install the Vault Client that matches with the edition of the Vault Server in order to log in successfully.
• This scenario assumes that the Vault 2017 CAD Add-Ins are installed on top of the Vault 2016 CAD Add-Ins. In this situation while uninstalling the Vault 2017 CAD Add-Ins, the Vault 2016 CAD Add-Ins must be removed from the Vault 2016 Add/Remove Features in order to completely uninstall the Vault 2017 CAD Add-Ins.
• If the install directory is a non-English directory structure you will not be able to view the help file.
• Before installing a Vault client, make sure the Beta version of DWG TrueView has been removed, otherwise the required version of DWG TrueView cannot be installed by the Client.
• Performing “Checkout” on a folder which contains user restricted files may not check out all of the files available for checkout.
• It is recommended that you allocate the recommended or higher system requirements when running Autodesk Vault 2017 in virtual environments. As virtual environments could cause unexpected consequences, Autodesk reserves the right to ask that any customer reported problems be reproduced on a physical machine outside of the VMware environment. Autodesk Vault 2017 was tested on VMware ESXi version 5.0 and VMware Workstation versions 9.0.1 and 10.​​
• For information on certified virtualization vendors and their respective solutions, see Microsoft’s products list at Server Virtualization Validation Program home page.
  • Microsoft’s support policy for Microsoft software running in non-Microsoft hardware virtualization software can be found here.
  • Microsoft’s support policy for Microsoft SQL Server products running in a hardware virtualization environment can be found here.

Vault Client Information

• ​Borrowing of Vault licenses is possible with Vault 2017, however, there may be situations where this will result in unexpected errors. If that occurs or if you want to block user(s) from borrowing Vault licenses altogether, you can do so by referring to the INCLUDE_BORROW section (under Options File Syntax) of the LicenseAdministration.pdf that can be found under the install directory for Network License Manager. The sample syntax for the options file for blocking users from borrowing Vault licenses may look like this: INCLUDE_BORROW 86646VLTM_2017_0F USER noname​​
• ​File and Folder Move confirmation prompt is off by default. To enable the confirmation, please change the frequency from 'Never Prompt' to your desired behavior under Tools -> Options -> Manage Prompts from the Vault Client.
• Mapping Text with Number or Text with Date: Works well when all clients and the server are in the same language-locale. With mixed locales values may convert in a manner that is not intuitive and may produce an undesirable result. Therefore, mapping Text with Number or Text with Date is only recommended when the server and all clients are working in the same locale.
• Copy Design

• The last run version of Inventor on your machine will be used for operations in the Vault Client, such as Copy Design. If the last run version of Inventor is older than the version of the files you are changing through the Vault client, then the Vault client will display an error. For example, if you last ran Inventor 2016 on your computer and try to do a Copy Design on files last saved in Inventor 2017 the Copy Design will fail.
• Copy Design on a substitute part results in the new part referencing the original derived assembly.
• When using Copy Design on an assembly that uses derived components, if you attempt to change the master sketch on one file, it will replace the master sketch on all files referencing the master sketch. It is recommended that you copy all instances. Copying one derived part but reusing another referencing the same master sketch is not supported.
• All library files may easily be set to Reuse by right-clicking on the main assembly and selecting Reuse Library Files.

• Purge
• Reference Repair Utility is no longer available from Autodesk Vault 2017.
• If you are upgrading from earlier releases of Vault to Vault 2017 please run the Reference Repair Utility on the earlier releases and fix the issues before upgrading to Vault 2017.

• Rename
• Renaming a Folder containing a large number of files may take longer to complete the operation.
  
  

• AutoCAD LT and Inventor LT

• Batch plot is not supported with AutoCAD LT or Inventor LT.
• Update view is not supported with Inventor LT. This includes jobs sent to a Job Server on a machine running Inventor LT.
• Revision table functionality for assemblies is not supported with Inventor LT. This includes jobs sent to a Job Server on a machine running Inventor LT.

• Lifecycle

• When modifying the state transition criteria of a lifecycle definition, the "Check that dependent child files are released" option can now be found on the Actions tab.

• Revise

• When revising a file, it is not possible to revise from a previous revision.

• Custom Objects

• When creating or editing existing Custom Object definitions, the changes will not populate in the Vault client until the following login.

• Items

• It is now possible to remove tertiary links from an item. However, if the primary link which caused the tertiary to be created remains on the item then the tertiary link will be recreated the next time the item is updated. For instance: if an .IPT with an .IDW is assigned to an item, the .IPT will get a primary link and the .IDW will get a tertiary link. If the tertiary link to the IDW is removed from the item, but the primary link to the .IPT is not, then on the next update of the item the tertiary link to the .IDW will be recreated.
• Updating an item will only update the unpinned file attachment versions for the item being updated. Any child items being updated as a result will not have their file attachment versions updated. You will need to update those items individually.
• ​For ACADM BOM rows that are merged, the group icon is not displayed. Instead the item icon is shown.
• Items with a value of "Not Effective" for Effectivity properties will not be migrated and will appear as an empty string​.
• ​For rows that are added manually, the units of measure won’t change automatically if the item’s units are changed after the row was added. As a workaround, those rows have to be removed and added again to show the current units of measure of the item.
• ​BOM Reports are always off the top level of BOM tab. Hence it is not right-click context menu sensitive.
• ​BOM Reports does not support thumbnail.
• Set Effectivity on a Change Order with an older Vault client will not release the Item listed on the Records tab.
• Set Effectivity of Items has been removed. Migrated vaults have the set Effective date value stored as a UDP.
• While an item is at pending creation state, 'Assign To' is not allowed to another existing item of Released state. As a workaround, turn off the row and perform Assign To again.
• Item and BOM functionalities are disabled when accessing from older supported Vault clients and Add-ins.
• Configuration factories (iFactory) cannot be assigned to items. However, the error message that appears when performing Turn Row On, Turn Branch On, or Assign To on configuration factories, is not accurate. Checking out and checking the file back in will not work in this case even though that’s what the error message suggests. A member of the factory must be used in place of the factory in order for the component to be promoted to an item.
• Sometimes the setting Group BOM rows as per the design BOM is not honored especially when Part Numbers are modified after the components have been inserted. If this happens, check out the assembly, uncheck the checkbox for the BOM setting, Enable Row Merge on Part Number Match, check it back again, save the assembly, check it into Vault and update the item.
• Vault doesn’t allow inserting an item into the same item (due to circular reference restriction). And when a user tries to assign item to a parent file that has a child with the same equivalence value, Vault displays a circular reference error. However, in some cases, instead of displaying this error message, Vault makes the child file a secondary link to the existing parent item. To get out of this situation, edit the parent item, remove the secondary link for the child, save the item, turn off the option “Auto-select first duplicate item," and update the parent item. The child should now have a new item assigned to it.
• ‘Assign/Update Item’ from file only updates the related item if the file has been modified since the last item assignment or update. If the file has not been modified, it is possible that items may be created for BOM children but the root item is not updated to include these new items. The solution to this is to ‘Update’ the item itself (from the item view) – this forces the item to be updated regardless of whether the file itself has changed.
• Item update may fail and result in Error 1455 or item links remaining stale on old data where vault edits have versioned the file​. To resolve this, version the file through the CAD application and perform the item update again.​​

• Change Orders

• The Set Effectivity command has been replaced by the Close Change Order command.
• If Items are part of a Change Order, users have the option of modifying the state of items during the Change Order Close command.
• Properties.
  • A custom UDP for an Inventor DWG cannot be mapped to an Item Entity Type. The workaround is to create and map the UDP to a File Entity Type, and then change the File Entity type to an Item Entity type.

Return to Top

Supported Language Configurations for Autodesk Vault Products

Supported Client Language Configurations

Any client meeting the following criteria can work with any server of any language meeting the server criteria below. Client language and server language do not need to match.

• The Autodesk Vault client is supported on operating systems of the following languages: Brazilian Portuguese, Czech, English, French, German, Hungarian, Italian, Japanese, Korean, Polish, Russian, Simplified Chinese, Spanish, and Traditional Chinese.
• An English language Vault client is supported on all supported non-English language operating systems.
• A non-English Vault client must match the language of the operating system.
• The Vault Basic client and add-ins are localized into Brazilian Portuguese, Czech, English, French, German, Hungarian, Italian, Japanese, Korean, Polish, Russian, Simplified Chinese, Spanish, and Traditional Chinese.
  • The language of the Autodesk Vault Basic CAD add-in must be the same language as the CAD application.
• Vault Workgroup and Vault Professional are localized into Brazilian Portuguese, Czech, English, French, German, Hungarian, Italian, Japanese, Korean, Polish, Russian, Simplified Chinese, Spanish, and Traditional Chinese.
  • The language of the Autodesk Vault CAD add-in must be the same language as the CAD application. To use Vault Workgroup or Professional with Hungarian and Spanish CAD applications, first install the correct language of Vault Basic. This will install the correct language of the Vault add-in to the CAD applications. Then install the Vault Workgroup or Professional client.

Other client language notes:

• The Vault client does not support runtime language switching.
• It is not supported to switch a CAD application's language to a configuration which does not meet the criteria outlined in the section above.
• An English version of Autodesk Design Review 2013 is included in Vault client products for Russian, Polish, Czech, Hungarian, and Traditional Chinese.
• An English version of Autodesk DWG TrueView 2017 is included in all Vault client products for all languages except Japanese and French.

Supported ADMS Language Configurations

Any server meeting the following criteria can work with any client of any language meeting the client criteria above.

• The Autodesk Data Management Server (ADMS) is supported on operating systems of the following languages: Brazilian Portuguese, Czech, English, French, German, Hungarian, Italian, Japanese, Korean, Polish, Russian, Simplified Chinese, Spanish, and Traditional Chinese.
• An English language ADMS is supported on all supported non-English language operating system.
• A non-English ADMS must match the language of the operating system.
• Any case-insensitive collation and/or language of SQL may be used with any language ADMS.
• Migrating from one Language of Vault Server to a different language of Vault Server is only supported if it is to or from an English Language Vault Server.
  

Other ADMS language notes:

• Restoring a backup from a different SQL collation other than the collation currently being used will result in the backup's collation being used.

Supported Connected Workgroup Server Language Configurations

Any server meeting the above criteria can work with any other server of any language meeting the above criteria.

Other replication-related language notes:

• The publisher's SQL collation/language determines collation/language in a replicated environment regardless of the installed SQL language at subscribers.
• Autodesk recommends all SQL installations in a replicated environment be the same language.

Return to Top

Vault for AutoCAD Products

AutoCAD Add-in Install Information

Please see the system requirements and installation instructions specific to your AutoCAD product.

• After uninstalling and reinstalling the Vault client, the Vault tab in the AutoCAD ribbon may not be available. This can be corrected by switching workspaces in AutoCAD.

• The Vault ribbon and toolbar may be missing when launching AutoCAD and AutoCAD-based products from the same installation but using different profiles. To restore the Vault ribbon and toolbar, enter CUILOAD and load the "VaAc.cuix" file from C:\Users\ [username] \AppData\Roaming\Autodesk\ [product name] \ [version] \ [lang] \Support
• Files with point cloud attachments are not supported. If checked in, the file will lose its association to the point cloud attachment.
• Files with PDF attachments are not supported. If checked in, the file will lose its association to the PDF attachment.
• The Change Category command is available in AutoCAD. It is not available in AutoCAD Electrical or AutoCAD Mechanical.
• Image reference of a DWG file will not be loaded correctly if the DWG file had been moved.
• Creating a New Part reference via Open from Vault will not update the Parts list if the Part Reference is not available in the part list already.
• File reference ID will be provided only when the file is checked in from AutoCAD Electrical 2016 or newer release​. ​
  
• ​Refresh an Electrical project file (wdp) may not download the related configuration files. Use Open Project from Vault to download the newer or missing configuration files.
• After Electrical files are renamed in the Vault client or with the new Copy Design, invoking "​Refresh All Files" with the AutoCAD Electrical addin causes an unexpected exit. Use Open Project from Vault instead of Refresh All Files to get the newer files.

• When using Vault Workgroup or Professional with AutoCAD Civil 3D, a configuration file must be imported into every vault database which will be accessed from a Civil 3D client. The configuration file Civil3D_Vault_Configuration.cfg can be found at
  [ADMS Install directory]\Custom Configuration.
• For more information on the Vault Add-In for AutoCAD Civil 3D, please refer to the AutoCAD Civil 3D Readme and Help.

• The following methods may be used with Folder Check In on large folders if problems occur:
  • Add sub-folders individually. To do this, first break down the main folder into sub-folders, then set the working folder to the top most folder. This will maintain the folder structure and file relationships after check-in.
  • Increase the number of GDI handles. Please see this Microsoft article for instructions. Seek assistance from your Administrator if you are not familiar with Registry settings.
• The following are restrictions on Folder Check In of DXF files from within AutoCAD based products:
  • DXF files with attachments cannot be checked into the Vault (be it within or outside the working folder).
  • Only single DXF files without attachments can be checked into the Vault if they are placed within the working folder. The user will be prompted to save the DXF file upon every Check-in.
  • DXF files will not be checked into the Vault when checking in a folder containing DXF files from outside the working folder.
  • DXF files will be checked into the Vault when checking in a folder containing DXF files from within the working folder. In this case, DXF files with attachments will be checked in but all file relationships will be lost.

• ​Vault 2017 add-in for AutoCAD no longer supports the interoperability between Inventor and AutoCAD within a 32-bit (x86) environment.
• To check in files with model documentation drawing views, a default Inventor project file must be set in the Vault options.
• To ensure synchronization with Vault, it is recommended that you set the Inventor project file in AutoCAD to be the same as the default Inventor project file in the Vault options.

• The Check in Folder command does not support sheet sets.
• Property write-back is not supported on sheet set files.
• The Vault sheet set manager integration does not support offline editing of sheet set files.
• The sheet set property 'Sheet set data file' cannot be mapped as a Vault user-defined property. Instead use the 'File Name' Vault system property.
• Renaming a sheet set in Sheet Set Manager will not update corresponding folder and file names in Vault, though all folders and files will resolve correctly.
• Renaming or moving sheet set data files or folders in Vault is not supported and will result in Sheet Set Manager not reflecting the changes.
• To convert vaulted DST files to DSS format:
  1. Download the DST file to your working folder.
  2. Open the DST file in Sheet Set Manager from your working folder.
  3. Check the file into Vault.

  The DST file will be converted to DSS format upon check-in.

• To change the Sheet Set automatic Check In visualization attachment options:
  1. Exit AutoCAD.
  2. Open the file ‘Preferences.xml’ at ‘%appdata%\Autodesk\AutoCAD [Version] Vault AddIn\Objects’ with any text editor.
  3. Under the respective AutoCAD profile ‘CheckIn On Auto Checkin SheetSet Options’, look for ‘<Property Name="DWF Option" Value="No DWF" />'.
  4. Replace “No DWF”, the default value, with “Create DWF locally” to create visualization during Check In or “Create DWF using Job Server” to send to Job Server.

Return to Top

Vault for Inventor Products

Inventor Add-in Install Information

• Please see the system requirements and installation instructions specific to your Inventor product.

• When using Inventor LT with Vault, the user's workspace is preset to %USERPROFILE%\My Documents\Vault\Designs and mapped to the root folder “$” in Vault. The workspace mapping cannot be changed.
• ​If Vault add-in for Inventor LT fails to load, remove the Inventor LT project file "Vault_Default.ipj" from ".\users\<Current User>\Documents\Vault" and then restart Inventor LT​.
• If you desire to work with a different workspace you must first disable the Vault add-in. To stop working in a vaulted environment, unload the Inventor Vault Add-In, uncheck Load Automatically for the add-in, and restart Inventor LT. After which, the ability to change a user's workspace will be restored.
• To load the Vault Add-In manually from the Add-in Manager, all documents must be closed. Otherwise, the add-in will not load.
• Assembly files are not supported in Inventor LT. If an assembly file is opened from Vault, a warning message will not be displayed.
• Vault functionality included in Task Scheduler is disabled in Inventor LT.
• Viewing assembly files in Vault which contain Content Center parts or running Pack and Go on assemblies which contain Content Center parts will result in issues if Inventor LT was last run. If viewing an assembly with Content Center parts the view will not load. If attempting a Pack and Go on an assembly with Content Center parts, the exported Inventor project file will have the Content Center path set to [Default] and a missing file warning may be displayed upon opening the assembly. These issues can be avoided by running Inventor View immediately prior to either the View or Pack and Go operation.

• The Vault browser will show that a file has been edited in memory for iPart Factories and iAssembly Factories if any members were renamed in Vault Explorer.
• When using substitutes, it is strongly recommended that all data be created within the working folder. If the data was created outside of the working folder and then added to a Vault, it is recommended that you open the file from Vault, Edit the file, and then save and check in all assemblies before performing any other Vault operations.
• The Inventor Vault add-in does not support AutoCAD files with model documentation drawing views of Inventor references.
• If opening an AutoCAD file with model documentation drawing views of Inventor references, the Inventor add-in will prompt more than once to check out and update properties for the file.
• ​Checkout prompt is seen even before clicking 'Update' button in Inventor assembly when the 3rd party data is modified.
• Inventor Vault browser needs explicit 'Refresh' to remove 3rd party data when selecting 'Place Import CAD files' but without placing the files.
• Assembly child parts may not appear in Vault Browser when 3rd party data is 'Opened' using Inventor 'Convert model' option. Perform a Vault Browser 'Refresh' to resolve this issue.

• The ‘Create DWF Job’ for Inventor files (and AutoCAD files with model documentation drawing views of Inventor references) will always use the Administrator-defined Vault Inventor project file setting. If the admin has not set a project file, a failure stating ‘The default Inventor project file is not set or could not be found.’ will be logged for the job. This error will also be displayed for updating DWFs locally if there is no administrator or user Inventor project file specified.
• When a Non-Administrative User tries to use the Default Templates for generating Reports using Data Mapping, an error comes up saying Template is not valid. To resolve the issue follow the procedure mentioned in this Blog article. 

• While working with Vault 2017 Items created from 3rd party files referenced in Inventor 2016 assemblies (i.e. Inventor 2016 AnyCAD Data) stored in Vault 2016, users must perform the following actions in Vault 2017 to properly update those Items.
  
  • Within Inventor 2017, checkout all 3rd party files related to the items you wish to update
  • Perform Inventor 2017 'Edit-Import' operation on all the 3rd party files, save, and check-in all files to Vault 2017.
  • Administrator must setup the following Vault 2017 property mappings: 
  • 'Number' Property 'Initial Value' mapped to 'Part Number' property for 'Other files'.
  • 'Equivalence Value' property mapped to 'Part Number' for 'Other Files'.
  • Perform Vault 2017 ‘Update Item’ operation on each 3rd party file.
• Detail IDs will not be created for Substitute Parts when the master assembly is uploaded to Vault using "Check In Project." The Update File References command should be executed in Vault Explorer to get Detail IDs created for Substitute Parts.

• Inventor assemblies that are checked in with an active LOD will not have Detail IDs extracted.
• ​Update Item will pull the values of the Detail ID from BOM table and update the Position Number values.
• The Item Position Number is extracted for the root component only for a structure BOM.
• Inventor assemblies that are checked in with an active LOD will not have updated Position Number. Inventor does not provide access to Structured BOM View within an active LOD. Always save and check in the assemblies with the Master LOD.

Return to Top

Vault for Revit Products

Vault for Revit Products

• Vault add-in for Revit requires Autodesk Vault Professional 2017.
• When loading a large number of Revit files into the Vault server, add files in batches of less than 1000 files, enable the Revit deep index, and wait for the index to complete before loading the next batch of files.

Copy Design

• The Item BOM is not updated for files created in latest copy design. Users must open and save files in their native application to update the BOM detail.

• Replacing multiple files at the same assembly structure level with a single file will result in creation of a single reference.
• There is no restriction on replace file types. Selecting incompatible replacements may result in failure of new files.
• Any changes to Vault property settings (e.g., default values, mappings, enablement) are not captured in the Copy Design Rule set XML after creation. Users must log out and log in to the copy design application to update property behavior in the action rules.
• The new names given by the Numbering Scheme will not be seen in the Copy Design Grid even after Copy action is done.
• Copy Design Action rules do not currently apply to Inventor iProperty 'Estimated Cost'.
• While working with different Vaults on a server, users should delete the existing Copy Design Rulesets created in the %appdata% location before switching Vaults and re-create the Rulesets manually after connecting to the destination Vault.
  User migrating from older Vault releases should take a note of this too.
• Users may experience issues when performing copy design on un-replicated files.
• Copy Design leverages the user-defined default Inventor project. Resolution errors can occur if a different project is used to open the files after copy.
• New file relationships created during Copy Design are repaired on open. Users should open and update copied files before carrying out additional work on the data.
• Copy Design is delivered with Vault Workgroup and Vault Professional in 2017 and supports the copy of AutoCAD Electrical design projects. When making copies of electrical configuration files, however, the user must manually enforce the proper naming convention of the electrical project configuration files.
• Users are permitted to copy iParts and iAssemblies but it should be noted:
  
  • Factories and members can be copied together BUT there is no associative link between these files. New copied members do not reflect table entries.
  • Members can be copied and used as stand-alone components.
  • Factories can be copied and the table edited to create new members.
  • Users must open and save files after copying in order to break the relationship link between Factory and Member.
  
  

Vault Synchronization with Buzzsaw

Vault Synchronization with Buzzsaw

• Vault Synchronization with Buzzsaw requires Autodesk Vault Professional 2017.
• Vault Synchronization with Buzzsaw is part of "Configure installation" of the Vault Professional 2017 Client installer.​
• Vault Synchronization with Buzzsaw​ can be added from "Add/Remove Features" after Vault Professional 2017 Client is installed.

Return to Top

Autoloader

Autoloader Information

Supported Data Formats

• Autoloader supports Inventor R10 and newer data.
• Autoloader supports AutoCAD R14 (and AutoCAD R14 products) and newer data.

• Follow these guidelines for autoloading data in to the Vault:
  • If autoloading Inventor files and not publishing DWF files, upload in batches no greater than 30,000 files.
  • If autoloading Inventor files and publishing DWF files, upload in batches no greater than 20,000 files.
  • If autoloading AutoCAD or DWG files without publishing DWF, upload in batches no greater than 50,000 files.
  • If autoloading AutoCAD or DWG files and publishing DWF, upload in batches no greater than 30,000 files.
• Close as many applications as possible while autoloading data.
• Autoloader copies all files which will be uploaded to a temporary folder on the system that is running Autoloader. Therefore, enough free space must be available to accommodate the duplication of the files. If publishing DWF or DWFX files, enough space must also be available to accommodate the visualization files as well.

• Prior to autoloading data, it is strongly recommended that you fully back up all vaults.
• In order to use Autoloader, you must disable Enforce Unique File Names in the Vault.
• Autoloader does not support auto ownership transfer. Please ensure you are uploading to a server/folder for which you have ownership.
• The Upload Report generated after files have been uploaded can only be viewed on the machine which created the report.
• Autoloader requires that Inventor 2016 or Inventor 2017 be installed (and be the last version of Inventor run) as well as a Vault 2017 product be installed on the same system as Autoloader to upload Inventor files.
• DWF publishing is not supported when autoloading Inventor data with Inventor LT.
• AutoCAD files with model documentation drawing views of Inventor references are not supported with Autoloader.
• If Inventor needs to re-register with the operating system while Autoloader is running, Inventor's re-registration process may cause Autoloader to close. Be sure to save all Scan and Upload reports prior to starting Inventor with Autoloader running.
• In order to publish visualization files (DWF or DWFx) for Inventor iParts, Autoloader requires that Microsoft Office Excel 2007 or newer is installed.
• It is required that all Inventor files be uploaded into the same folder in the vault. By default this folder is named Designs, but you may change the name by using the Rename button. You may only change the name if you have not yet uploaded any files to the Designs folder.
• If Direct 3D 9 is installed on your machine, it is recommended that you change the Inventor hardware setting to any value other than Direct 3D prior to doing DWF or DWFX publishing in Autoloader.
• AutoCAD file types may be uploaded to any folder in the Vault.
• AutoCAD Electrical files, AutoCAD Mechanical files, and Mechanical Desktop files will all be uploaded to the vault as vanilla AutoCAD files. This may result in the loss of file relationships.
• Sheet Set Data will be uploaded to the vault as vanilla AutoCAD files. This may result in the loss of sheet set relationships. It is recommended that you use Sheet Set Manager to check in sheet set data.

Return to Top

Vault for Microsoft Office

Microsoft Office Add-in Install Information

The following versions of Microsoft Office applications are supported with Vault 2017:

• The Autodesk Vault 2017 add-ins for Microsoft Office support the Microsoft Office 2013 desktop applications offered by Microsoft Office 365. Vault 2017 add-ins for Microsoft Office DO NOT support the Microsoft Office 2016 versions of the same.
  See more at: http://underthehood-autodesk.typepad.com/blog/2016/01/office-365-support-with-vault.html
• If invoking the initial Vault licensing dialogs from the Office or Outlook add-ins, the dialogs may appear behind the Microsoft Office application. To workaround, please select the "Specify Network License" dialog from the Windows Task bar to bring it to the forefront.
• For best results, Autodesk recommends installing all available updates and service packs for your version of Microsoft Office.

Return to Top

Vault for Microsoft Outlook

The Microsoft Outlook Add-in is available in Vault Workgroup and Vault Professional.

Microsoft Outlook Add-in Install Information

The following versions of Microsoft Outlook applications are supported with Vault 2017:

• Please see the Vault Help documentation for important additional details on configuring and using the Outlook add-in.
• The Microsoft Outlook add-in is not automatically installed. You must expand the client settings during installation of the Vault client and select the Outlook add-in to install.
• For best results, Autodesk recommends installing all available updates and service packs for your version of Microsoft Outlook.

Setting Up Outlook Properties

After installing the Outlook add-in, it is recommended that a Vault administrator follow these steps to map the following two properties:

1. In the Vault client go to Tools > Administration > Vault Settings.
2. Select the Behaviors tab and click on the Properties button.
3. Click New to create a new User-Defined Property (UDP).
4. In the "Name" field type in "Email Conversation Topic" select "Text"as Data Type.
5. In the "Associations" field select the category to which emails will be assigned.
   • You may want to create an Email category prior to creating the property.
6. On the Mapping tab, select "Outlook (*.msg)" as the provider and select an email file in the Vault or on disk and map the UDP to the Item Name file property.
7. Click OK.
8. Repeat steps 3 through 7 to map an "Email Sent Date" UDP to the "Sent Date" file property with "Date" as Data Type.
9. Close all Administration dialogs.
10. Start Outlook and log in to the Vault.
11. Click the Vault Settings button.
12. In the Conversation Topic Property field select the "Email Conversation Topic" UDP.
13. In the Sent On Property field select the "Email Sent Date" UDP.
14. Click OK.

With these property settings, the Outlook add-in will treat email conversations as file associations in Vault. You will be able to use the Uses and Where Used tabs in the Vault client to view the email thread for all emails checked into Vault.

Microsoft Outlook Add-in Information

• If you map a calendar folder to a Vault folder, when you accept or decline the request you may be notified that a mail item has been removed in Outlook, and that it should be removed from the Vault.
• If you notice system performance is being impacted after installing the MSG iFilter, please see the Help documentation for information on changing the indexing options to improve performance.

Return to Top

Thin Client

The Autodesk Thin Client is available in Vault Workgroup and Vault Professional.

Thin Client Install Information

The following version of web browsers are supported with Thin Client 2017:

• If ADMS is installed on a Custom IIS Port, then Thin Client cannot use that custom port as well as the Default IIS Port. It has to be installed using another IIS Port.
• If ADMS is installed on the Default IIS Port, then Thin Client can also be installed using the same Default IIS Port or on another IIS Port.
• It is not possible to configure the Thin Client IIS Port for Vault Workgroup.
• If you are upgrading Autodesk Thin Client from Vault 2015 or 2016, and need a reference of the existing web.config file, do remember to backup the original web.config file located in \Autodesk\Thin Client 2015 or 2016 folder.
• If you are upgrading Autodesk Thin Client from a previous release to the current release, you need to uninstall the previous version prior to installing the new version.
• Administrators attempting to install/upgrade Vault 2017 with a username different than the username used to install Vault 2015 or Vault 2016 on the same machine may encounter problems uninstalling those prior versions of the Vault Thin Client.
• Autodesk Design Review works only for IE x32 browsers, whereas IE x64 browsers are not supported.
• To view visualisation files in Autodesk Thin Client using Internet Explorer, Autodesk Design Review Desktop must be installed on the client machine.
• ​Autodesk Thin Client currently does not support logging into Vault Server through HTTPS binding.
  

Return to Top

Content Center Libraries

• Download the Remote Content Center Libraries for Vault 2017 from Autodesk Inventor Services & Support Page.

Vault Office

• Please refer to this page for Vault Office Installation instructions - http://www.autodesk.com/vault-office-installation-2017-enu

• For Vault Office users to use "Job Server" related functions, the "Job Server" must be enabled in the "Global Settings" dialog in the "Administration" menu. System administrators can help Vault Office users launch Vault Client in non-Office mode to enable the "Job Server" function.
  

Return to Top

Autodesk Vault Professional, Autodesk Vault Workgroup, Autodesk Vault Basic, Autodesk Data Management Server, Autodesk Vault Office, Autodesk Inventor, AutoCAD, AutoCAD Mechanical, and AutoCAD Electrical are trademarks of Autodesk, Inc. in the United States and/or other countries. Windows Server 2012, SQL Server 2012, SQL Server 2014, Windows 7, Windows 8.1, Windows 10, Microsoft Office 2013 and Microsoft Office 2016 are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. All other trademarks are the property of their respective owners.​

Return to Top