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.
When using connected workgroups, you need to provide a network location for the snapshot folder on enabling the workgroup. Replication will store the initial snapshot in this folder. Up to Vault Professional 2013 you could not change this folder after enabling connected Workgroups. If you wanted to change this folder location you would have needed to reinitialize the workgroup.
As demand came for this feature we introduced it in Vault Professional 2014. You can relocate this snapshot folder to a different location now.
Here is the How-To:
Create a new folder in a network location of your choice. Provide a service account you will use for this rights for folder. In ADMS Console, go to workgroups and click right and select "Replication Properties".
After that you see the following dialogue where you can provide a new network location for the snapshot folder.
Change the snapshot folder to the new network location. Provide userid and password for the user who has access to this folder.
After changing this, Vault checks permissions and is creating a new Folder with needed information in there. Furthermore it will trigger SQL to generate new snapshots, which will be now stored in this new location.
AutodeskVault@26200Whilst Autodesk investigates a solution, I thought sharing a newly discovered issue to reduce its impact might be appreciated by our partners and customers using the Place From Vault command in Inventor.
Under certain precise circumstances Inventor 2014 appears to hang\freeze\pause for 10 minutes.
Here are the steps to reproduce this behaviour.
Insert a new ipt into that 1.IAM
Check 1.IAM into Vault (2014)
Rename the .ipt in Vault
In Inventor, create a second new IAM
Place 1.iam into 2.iam
This starts the “Connectivity.Resolve.ResolveService.exe” process
Crash Inventor (Or simulate a crash by killing Inventor.exe in Task Manager). The Connectivity.Resolve.ResolveService.exe from the first session is still running
Place 1.iam from Vault
Hang for 10 minutes
The gap between steps 8 and 10 could be immediately or several hours. The important point is that the ResolveService.exe from the first Inventor session is still running when Inventor is restarted.
The workarounds for this are as follows:-
Wait until Inventor eventually becomes responsive. OR
Kill the “Connectivity.Resolve.ResolveService.exe” process at step 11
Thanks to Erik Gilsdorf, who first reported this issue to us and helped us reproduce it when it was very difficult to isolate the precise steps to recreate this from scratch. Thanks for your patience Erik!
This issue is addressed in:-
Cumulative Hotfix 3 for Autodesk Vault 2014 SR1, SP1 (DM18101330) (download from Subscription Center)
Cumulative Hotfix 3 for Autodesk Vault 2014 SP2 (DM182230)