This presentation details the process of getting files from a Vault server. It goes on to describe the same process in an environment where there are multiple Vault servers. The basic scenarios described, assume that the viewer understands the major components that comprise a Vault Server, namely the database, filestore and Vault Server itself. The process described applies to both Vault servers (ADMS) and File Servers (AVFS).
FIPS (Federal Information Processing Standard) is a standard for computer system cryptography. The framework includes best practices for encryption compliance and can be enabled within Windows Systems.
Enabled needs to be set to 0. Please check also with IT if they do not set this setting via Group Policy, because then it would be reset at the next reboot and you will be puzzled why Vault is not working as expected.
Example where FIPS does prevent Vault from working properly:
Vault Workgroup Client was working as expected (on a different machine) The login error from Vault Office thick client was "failed to acquire a license" Licenses were all fine and installed on the same server.
Thin Client error was: "The type initializer for 'DataManagement.Application.Web.VaultUtils.SecurityUtils' threw an exception" when using read only check box.
Unchecking read only checkbox gets you a 500 Page "Server Error in /AutodeskTC Application with error message: "This Implementation is not part of the Windows Platform FIPS validated cryptographic algorithms"
After disabling FIPS with method above it was working fine.
Vault Professional and Workgroup 2016 are now available to download via Autodesk Account.
Before Installing the latest version of Vault, please refer first to the System Requirements to ensure that your planned implementation is supported and also the Readme\Release Notes for any known issues.
If migrating from an earlier release, please also refer to the Upgrade Autodesk Vault Documentation in the Help.
Vault Professional 2015 has an Item and Change Order (CO) Unlock command. It can be found in the Actions pulldown in Vault Explorer.
To make this feature function properly, the user whose Item or CO locks during their edit will be the one to select the locked item or CO, and go to Actions>Unlock Item and CO command.
Please note, this feature does not work in cases where a user gets locked out of their CO or Item, and someone else tries to unlock it.
Why do items and CO's get locked?
Well to be frank, we are still trying to uncover the full reason. However, we have found it is due to IIS or the IIS worker process either restarting or recycling while the item or change order is in the edit mode. You can replicate the behavior for yourself by editing an item, and while the item is in edit, restart IIS on your Vault server and you will get the item to lock. The same steps will force a CO to lock. Now logically, we are not here to advocate you doing this, but if you feel the need to test it out for yourself, this is one way to do it.
How can we try to stop the worker process from recycling on its own in 2015 or prior releases?**(UPDATED)**
Some ways you can try to reduce the worker process from restarting are:
Modify application pools to one service each
Open IIS manager
Go to the Application Pools
Review the applications pools to see that they are only servicing one application.
If you see AutodeskDM running Services and Filestores websites, you will want to fix the filestores site to use the AutodeskFS application pool.
If you see that the WebClient service is being used by AutodeskDM, you can create a new Application Pool following the steps in the Advanced Configuration guide, or set it to use the DefaultAppPool.
Note: We've also found that adjusting the Regular Time Intervals does help keep the worker process from crashing out, but the number to which you will set is dependent on your environment.
You will also set IIS_IUSRS to full control over your websites
Go to Default Web Site and add the security permissions.
Go to lower level folders and ensure the permission propagated
Although we cannot guarantee these settings will resolve the item/co locking issue, we have seen a reduction in the occurrences.
When will the unlock feature be backported to prior releases?
The necessary actions to backport this feature are not architecturally feasible in previous releases, due to the many changes added to the 2015 product that allow this feature to work in 2015. Therefore, the recommendation is if the steps noted above do not reduce the occurrences of item/co locking, upgrade to Vault Professional 2015.