Cracking the Vault

Autodesk Vault 2012 Data Reuse

Autodesk Vault 2012 Concurrent design

Autodesk Vault 2012 Best-in-class CAD Integration

Nothing To Do With Data Management but Entertaining Nevertheless

I did not know anything could be more entertaining than Data Managment until I saw this short movie trailer about Mr McCluskey's Method from a director called "Otto Deschk"

Renaming Parts Using Vaults Document Revision Management

The following workflow process demonstates how the Revision Management within Vault Workgroup 2011 works when renaming a child component that has been released.

 1) Here we have a simple Parent\Child relationship.

 

2) Assign Category = Engineering. Both files becomes RevA. A new file version is created. (v2)

Migration Error from Vault 2009 to Vault 2011

A partner kindly shared this solution with us today when they encountered this migration error found in the ADMS Console Log.

23/03/2011 13:18:23 Migrating "<vaultname>" database... 0/7
23/03/2011 13:20:24 ScriptMigrationOperation: Connectivity.Core.Database.Sql.Migration.CoreVault_9.0.5_to_9.0.6.sql
23/03/2011 13:37:03 Connectivity.Application.VaultManager.ServiceException: The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.ContentSourceProperties' and the index name 'PK_ContentSourceProperties'. The duplicate key value is (7, IMG.SRC!{C82BF597-B831-11D0-B733-00AA00A1EBD2}!ntext, 168917).
Could not create constraint. See previous errors.
The statement has been terminated. ---> System.Data.SqlClient.SqlException: The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.ContentSourceProperties' and the index name 'PK_ContentSourceProperties'. The duplicate key value is (7, IMG.SRC!{C82BF597-B831-11D0-B733-00AA00A1EBD2}!ntext, 168917).
Could not create constraint. See previous errors.

Are Vault 2011 & 2010 Supported On Windows 7 SP1

No Autodesk Vault application is currently supported on Windows 7 SP1.

If an issue is encountered on Windows 7 Service Pack 1, it would be necessary to test to see if the issue also occurs on Windows 7 (no service pack).

The reason for this is that both Vault 2010 and Vault 2011 were both released before Windows 7 SP1 and no testing has currently been done.

SQL Agent Is Timing Out Due To High Latency

You might see the followng error message in the Replication Monitor or Error Logs during replication.

 

 

"Unable to decide if MakeGeneration is needed. (Source: MSSQL_REPL. Error number: MSSQL_REPL-2147199360) Get Help: http://help/MSSQL_REPL-2147199360

Query timeout expired (Source: MSSQLServer, Error Number 0) Get help://help/0

The merge process failed to execute a query because the query timed out. If this failure continues, increase the query timeout for the process. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to whichto write (Source: MSSQLServer, Error number: 0)"

 

OR

"Replication-Replication Merge Subsystem: agent NOV-DEPOT\AUTODESKVAU-Project_Mayhem-ADMS_Project_Mayhem-ACRD-DEPOT\AUTODESKVA-25 failed. The process failed to get information about the Custom Resolver Component for article 'SchemePattern' from the registry."

 

This indicates that either the -LoginTimeOut or -QueryTimeOut values need to be increased.

These values can be specified on the merge agent command line, but it would need to be done per-subscriber, per-database
    http://msdn.microsoft.com/en-us/library/ms151326.aspx
    http://msdn.microsoft.com/en-us/library/ms147839.aspx

Log File Configuration

Researching an earlier post, I noticed a handy little feature that I had forgotten about. I have seen a number of systems lately where the amount of Free Disk space had really become a problem. Although, not the root cause of the problems being investigated, in one case, we found that the space consumed by several years of ADMS Console and server logs had exceeded 8GB!

A feature in Vault Server 2011 and possibly 2010 as well, is the ability to "Limit the number of log file before they are recycled. Vault must be between 6 and 99"

 

Tools>Administration>Advanced Settings>Advanced Configuration settings>Settings.

 Under "Log File Configuration", is the ability to limit the

"Maximum number of console logs"

"Maximum number of server logs logs"

"Maximum number of emai logs"

 

I am sure this is a very popular feature, I just hadn't seen it for a while :-)

 

 

 

 

Permissions Required For the SQL Snaphot Folder\Share Path

The correct permisions required to access the SQL Snapshot folder are as follows

SQL Server Agent (AUTODESKVAULT).

    By default this service uses the "Network Service" windows account. If configured differently or a mix of Domain\workgroup environments are being used, the SQL Server Agent account must have (read for Subscribers and read-write for publisher)

 

SQL Server (AUTODESKVAULT)

By Default this is the "Network Service" account. if different than the default, it needs read-write permsissions.

 

Vault Impersonating Account

    By Default this is the "AutodeskVault" user account. In Vault Collaboration\Professional 2011, this account must have read-write.