In a continuing effort to provide high quality products, Autodesk has released this hotfix which provides the following updates;

1. A security setting update for file status changes.
2. Category creation resulted in Error 3507.
3. Error 227 when performing a search.
4. Index block attributes update.
5. A server performance enhancement.
6. A correction for the usage of double byte characters.
7. Update to resolve a data migration issue.
8. New item creation on item update.
9. Improvements to the Customer Involvement Program reporting.
10. Cumulative updates.

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

Description of the Issues
System Requirements
Related Hotfixes and Utilities
Known Issues
Warnings
Files Affected
Update Verification
Installation Instructions
Legal Notice

New Updates

1. When multiple security settings are enabled on a folder, the settings would incorrectly prevent a user from performing a state change on a file.
2. When selection a custom Category an error 3507 would occur with the message 'Invalid Behavior 'Flexible Release Process'.
3. Performing a search would sometimes result in an error 227.
4. When performing an index block attribute, properties were not being extracted correctly.
5. A server performance update for operations that get relationships for parent assemblies with subassemblies that have many of the same children.
6. Attempting to use a double byte character for folder or file names would result in the error "Some items in original selection set are no
   longer available in Vault. Please refresh and try performing the operation again."
7. A new migration issue has been resolved for error messages containing the following;
1. "The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.ItemBOMLink' and the index name 'IX_ItemBOMLink_8'."
8. Performing an Item Update incorrectly creates a new item.
9. Improvements to the Customer Involvement Program reporting.

Cumulative Updates

1. This update will enhance Vault check in performance for models with extensive parent-child references.
2. Migration issues have been resolved for error messages containing the following;
1. Error converting data type nvarchar to float.
2. Cannot insert duplicate key in object 'dbo.ContentSourcePropertyDef'
3. Cannot insert the value NULL into column 'ParentItemIterationID'.
4. The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.ItemBOMLink' and the index name 'IX_ItemBOMLink_8'.
3. When attempting to create more than one custom numbering scheme, only the first numbering scheme created was retained.
4. When performing a search on entities that contain Greek characters, the characters were acting like wild card characters.
5. Exporting Items to a DWF package would fail with the error message, "The underlying connection was closed: An unexpected error occurred on a receive."
6. Viewing the Item BOM or the 'Where Used' tabs resulted in an error 1313.
7. In rare cases, migration may result in the SQL TempDB table growing excessively large and causing a migration failure.
8. Multiple item update operations were resulting in improper updates to items.

Vault Server

This cumulative update contains all of the updates from the following hotfixes (see Cumulative Updates);

NOTE: It may be necessary to perform a SQL database shrink if the TempDB table has grown excessively large. This may
also be accomplished by restarting the SQL service or rebooting the server.

It is strongly recommended to perform a back up prior to the application of this update.

This hotfix cannot be uninstalled. To revert to a pre hotfix state, a restore of a previous back up must be performed.

WARNING: Failure to follow these instructions properly may result in unusable sites. This procedure applies to
Single Site, Multi Site and Connected Workgroup deployments.

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

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

1. Reset the web service by typing 'iisreset' at the command prompt.
2. Run ts17313115.msp on the ADMS server to install the hotfix.
3. Repeat the preceding steps for every ADMS server.
4. Open ADMS Console and migrate all unmigrated databases and libraries before proceeding.
1. NOTE: It is sufficient to utilize a single ADMS Console on;
1. Multi Site (file replication)
2. Connected Workgroup (file and SQL replication) on a Publisher Workgroup ONLY
5. Close the ADMS Console application.

Database Update – applied ONCE from one Autodesk Data Management Server (ADMS) as specified.

6. WARNING: DO NOT PROCEED until the hotfix has been successfully applied on ALL ADMS servers.
7. It is sufficient to utilize a single ADMS server on;
1. Multi Site (file replication)
2. Connected Workgroup (file and SQL replication) on a Publisher Workgroup ONLY
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' dialog will display when the b2bmigrate operation has completed.
11. Open the Autodesk Data Management Server console and begin a Rebuild Search Indexes.

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.