In a continuing effort to provide high quality products, Autodesk has released this cumulative hotfix which provides multiple updates for Autodesk Vault 2016 SP0.

This README file highlights how to install this hotfix and other important information regarding this update.

Cumulative Hotfix 1 Updates

1. When selecting historical revisions of Items, the vertical property pane was not updating to display properties for the current revision selection.
2. When "Include Plot Stamp" or "Watermark" is turned on for a plot, the resulting plot would not contain relative path xrefs.
3. Document Change State has been updated to apply to revision specific children instead of the latest children.
4. Certain characters in a path (ex. apostrophe or ampersand) would cause Copy Design to fail with the message, "Illegal characters in path".
5. Autodesk Exchange Apps were not loading properly with Vault Basic.
6. In some cases, BOM data is not preserved properly resulting in an “Unknown Server Error” during check in or result in an Item update failure.
7. Logging into Vault from Inventor as a "Content Center library read only user" would result in an object reference error message.
8. Solved a Revit add in issue where linked projects could overwrite user changes.
9. In certain circumstances, while it is possible to go to an Item from a file, the Item cannot be found in an Item search or may not be listed in the Items details pane.
1. NOTE: Once this update is applied, the affected Item must be edited and saved to completely resolve this issue.
10. Exporting a Vault configuration, when Category rules for file and item exists with the same name, would result in a message containing, "An error occurred when applying configuration".
11. Creating a new lifecycle state using an ampersand would result in error 1420, "Could Not Retrieve Watermark Definition" when accessing Vault Settings.
12. This update includes the Vault Configuration Administrator which enables setting the File Item link Behavior to always create a standard component link for each sub-component created using the Assign/Update Item command. See the installation instructions for usage.
13. CER (Crash Error Reports) Resolved
1. Resolved Inventor CERs during the loading and unloading of the Vault add-in.
2. Enhancements to avoid CERs for some Vault add-in startup crashes.
3. Additional enhancements to avoid more general CERs.

Client

Server

CLIENT INSTALLATION

1. Download the hotfix to a temporary directory on the workstation.
2. Extract the 'DM2105910_Client.msp' file to the temporary directory.
3. Double-click on 'DM2105910_Client.msp' to install the hotfix.
4. Install the hotfix on each applicable workstation.

SERVER INSTALLATION

WARNING: Failure to follow these instructions properly may result in unusable sites.

NOTE: Always ensure that a successful backup has been performed before applying any hotfixes.

SINGLE SITE

Hotfix Installation

1. Reset the web service on the Autodesk Data Management Server (ADMS) by typing 'iisreset' at a command prompt.
2. Run 'DM2105910_Server.msp' on the server to install the hotfix.
3. Open the ADMS Console and migrate all un-migrated databases and libraries before proceeding.
1. NOTE: It may be necessary to detach an un-migrated database if the update addresses a migration problem.
4. Close the ADMS Console application.

Database Update

5. Open a command prompt and navigate to the installed location of Connectivity.ADMSConsole.exe.
6. Run ADMS b2bmigrate operation in command line mode:
1. Example: Connectivity.ADMSConsole.Exe -Ob2bmigrate -VUadministrator -VPadmin_password -DBUsql_user -DBPsql_password
2. NOTE: Replace 'admin_password' with the appropriate administrator password for the -VP switch.
3. The last two command line parameters are required only if the 'sa' password is not the default password.
7. A 'migration successful' dialog will display when the b2bmigrate operation has completed.
8. If necessary, open ADMS Console and attach any previously detached databases.

MULTI SITE (file replication)

Hotfix Installation – applied to every Autodesk Data Management Server (ADMS).

1. Reset the web service by typing 'iisreset' at a server command prompt.
2. Run 'DM2105910_Server.msp' on an ADMS server to install the hotfix.
3. Repeat the preceding steps for every ADMS server.
4. Open one ADMS Console and migrate all unmigrated databases and libraries before proceeding.
1. NOTE: It may be necessary to detach an un-migrated database if the update addresses a migration problem.
5. Close the ADMS Console application.

Database Update – applied ONCE from ONE Autodesk Data Management Server (ADMS).

6. WARNING: DO NOT PROCEED until the hotfix has been successfully applied on ALL ADMS servers.
7. Open a command prompt and navigate to the installed location of Connectivity.ADMSConsole.exe.
8. Run ADMS b2bmigrate operation in command line mode:
1. Example: Connectivity.ADMSConsole.Exe -Ob2bmigrate -VUadministrator -VPadmin_password -DBUsql_user -DBPsql_password
2. NOTE: Replace 'admin_password' with the appropriate administrator password for the -VP switch.
3. The last two command line parameters are required only if the 'sa' password is not the default password.
9. A 'migration successful' dialogue will display when the b2bmigrate operation has completed.
10. If necessary, open ADMS Console and attach any previously detached databases.

CONNECTED WORKGROUP (file and SQL replication)

Hotfix Installation – applied to every Autodesk Data Management Server (ADMS) in all workgroups.

1. Reset the web service by typing 'iisreset' at a server command prompt.
2. Run 'DM2105910_Server.msp' on an ADMS server to install the hotfix.
3. Repeat the preceding steps for every ADMS server in all workgroups.
4. Open one ADMS Console on the Publisher workgroup and migrate all un-migrated databases and libraries before proceeding.
1. NOTE: It may be necessary to detach an un-migrated database if the update addresses a migration problem.
5. Close the ADMS Console application.

Database Update – applied ONCE from ONE Autodesk Data Management Server (ADMS) on the Publisher workgroup ONLY.

6. WARNING: DO NOT PROCEED until the hotfix has been successfully applied on ALL ADMS servers in all workgroups.
7. Ensure that all workgroups are online and accessible before proceeding. Do not proceed until the Replication Status | Merge Information dialog
   shows "Waiting 60 second(s) before polling for further changes." for each replicated vault and library.
8. Open a command prompt and navigate to the installed location of Connectivity.ADMSConsole.exe.
9. Run ADMS b2bmigrate operation in command line mode:
1. Example: Connectivity.ADMSConsole.Exe -Ob2bmigrate -VUadministrator -VPadmin_password -DBUsql_user -DBPsql_password
2. NOTE: Replace 'admin_password' with the appropriate administrator password for the -VP switch.
3. The last two command line parameters are required only if the 'sa' password is not the default password.
10. A 'migration successful' dialogue will display when the b2bmigrate operation has completed.
1. NOTE: A successful migration may take some time as the database updates must be consumed by the subscriber workgroups.
11. If necessary, open ADMS Console and attach any previously detached databases.

Vault Configuration Administrator

1. The Vault Configuration Administrator is now able to set the File Item link Behavior to always create a standard component link for each sub-component created using the Assign/Update Item command.
1. Administrator may run the utility and set the option to always create standard component links for NEW sub-component during the Assign/Update item process.
2. As a result of this configuration change, Assign/Update Item command will set all NEW sub-component links to be standard component links. The resulting link behavior will be the same as standard component link. Assign/Update Item will NOT update existing sub-component links.
3. All NEW sub-component links will NOT honor the auto-select first duplicates flag.
4. Vault Configuration Administrators may enable this configuration change by running a utility (via command line, no User Interface) and passing the proper arguments such as Vault Server Name, Vault name, Administrator ID (sa), etc. There will be no end-user level configuration setting to allow individual users to overwrite the Administrative setting (e.g. this is a Global Vault environment setting).
5. To enable this configuration change:
1. Download the configuration change utility provided with this cumulative hotfix.
2. Unzip the configuration change files into a Vault Server local drive.
3. Browse to the 'SetCreateStdComponentLinkSwitch' folder to find the 'fix.bat' script.
4. Open the 'fix.bat' configuration script to configure the parameters according to your Vault environment.
5. Execute the 'fix.bat' configuration script to set the designated server flag.
6. To undo this change, repeat the above steps using the 'RemoveCreateStdComponentLinksSwitch' files provided with this Service Pack.
6. In replicated Vault environments, run the configuration change script on the Publisher only. Running it on Subscribers may cause conflicts.

Autodesk does not guarantee that you will be able to successfully download or implement any hotfix, utility, service pack or workaround, or any of the tips, tricks, examples or suggestions outlined in any Autodesk product support technical documents. Technical documents, hotfixes, utilities, service packs and workarounds are subject to change without notice to you. Autodesk provides technical documents, hotfixes, utilities, service packs and workarounds "as is" without warranty of any kind, whether express or implied, including warranties of merchantability and fitness for a particular purpose. In no event shall Autodesk or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of data, or loss of business profits or special damages, that may occur as a result of implementing any hotfix, utility, service pack or workaround, or any suggestion outlined in any Autodesk product support technical document, even if Autodesk or its suppliers have been advised of the possibility of such damages.