Cracking the Vault

Jobs in Jobserver failed with Error 205

You noticed when working with Jobserver for Autodesk Vault that some jobs always failing with the following error:

"Results: This file is only available from the following sites which are not accessible at this time: MYVAULTSERVERNAME"

In the vlogfile you have noticed an error 205 about problems to access a file in the Filestore of the Vault :

Could not validate or replicate resource 'Inaccessible' version 0. Located in the filestore at C:\Vault\Filestore\Vault\000\000\000\000\000\000\655\655_285155_0..
*******************************************************************
Error: Soap Exception ( mesg-id = 634523628978768865 )
Exception: CouldNotReplicate [205] (MYVAULTSERVERNAME)
Stacktrace:
Server stack trace:
at Connectivity.Core.Operations.Replicator.a(Enum A_0, Resource A_1, List`1 A_2)
at Connectivity.Core.Operations.Replicator.ReplicateResource(Resource res)
at Connectivity.Core.Services.KnowledgeVaultService.GetNonlocalResource(Resource res)
at System.Runtime.Remoting.Messaging.Message.Dispatch(Object target, Boolean fExecuteInContext)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

In this case the issue is not related to Vault replication. It will even show up if you are not using Vault Replication.

Resolution: the problem is caused by insufficient permissions on the user which is running the jobserver.

Make sure that the Jobserver user has read/write permissions on the file(s) which you want to submit to the Jobserver.

Everything is going to change

Everything’s changing this year at AU! www.autodesk.com/everythingchanges #AU2011

Service Packs and Hotfixes

In the past Autodesk would release a Vault Hotfix for each issue that is discovered. This was a good strategy to get Hotfixes released to address specific issues that were affecting production. But the feedback we received from Administrators was that it was practically very difficult to roll these individually over multiple systems.

So lately you may have noticed that many of the Hotfixes being released now for Vault x 2011 and 2012 are now cumulative. So a "Multi Issue Hotfix" should contain most (if not all) of the hotfixes that preceded it. There will still be Hotfixes released to address hot issues, but these should be consumed with the next Multi Issue Hotfix.

There may also be the situation where a specific hotfix is released immediately prior to a Multi Issue Hotfix, but is not consumed within it. In that case, we just couldn't get it in, in time but didnt want to delay a big patch that could help most users. You should look at the readme of the Multi issue Hotfix to see if the issue is listed or not. If it is not listed, it should be consumed in the next Multi Issue Hotfix.

So as a rule, always install the latest Multi Issue Hotfix, and any other relevant hotfixes between that and the preceding Multi Issue Hotfix.

The feedback we have received so far is that this method is far easier to implement than lots of individual Hotfixes.

So.. now you know. :-)

Web Client Error

We have limited reports of this error but if you see this message:-

"Vault has detected tampering with the security subsystem. Unlicensed client access is currently prohibited."

 

This error indicates that someone has modified some permissions in the database which is not allowed as it violates licensing restrictions.

If you run a b2bmigrate it should resolve the issue.

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.

After this restart the web service by running an IISREST.

 

 

Dont Forget... To Run a Maintenance Plan

Every now and then, Support is contacted to help a customer who is in trouble. Maybe their Vault is running slowly or they get an error they dont understand.

There have been a couple of cases reported recently that have been resolved merely by running an SQL Maintenance plan. To even the old hands, this simple practice can sometimes be forgotten. So I thought it worthwhile to broadcast a friendly precautionary reminder to all readers of this blog to ensure that they are running SQL Maintenance plans for any Vault systems that they are responsible for.

As a best practice this should be run weekly.

The instructions for running the SQL Maintenance plan can be found in the Advanced Configuration Guide posted here

http://wikihelp.autodesk.com/Vault/enu/2012/Help/03._Installation_and_Configuration/Vault_2012_Advanced_Configuration_Guide/1008SQL_Maintenance_Plans

A Downloadable version can be found here

http://usa.autodesk.com/adsk/servlet/ps/dl/index?siteID=123112&id=2334440&linkID=9261341 

"Error initializing the Knowledge Vault in database"

When trying to check files into the Vault you can sometimes see this error message occur

  
 

"A problem occurred while attempting to add '<filename>' to "<virtualpath>". Would you like to continue adding any remaining files?

The server returned the following information: Error initializing the Knowledge Vault in database."

 

This is a generic error and can indicate that there is a problem with some properties that the file contains. In this instance the root cause was that the file being vaulted had exceedingly long property values. Once these Custom properties had been deleted or the "Export Parameter" tick was removed, it was possible to Vault the file.

  

So, in Inventor, Manage>Paramaters, You have the "Export Paramater" column. You can "Order By" that column and untick until they are all unticked.

 

 

It is worth noting that this same file in Vault Professional 2011 was causing an Error 1200 when trying to assign Item.

No License available when Connecting with Autodesk Vault Office 2012

You have successfully installed Autodesk Vault Office 2012 on the ADMS Server and on the Clients where an office application (such as MS Office 2010) is installed.

If you try to login from the office client (for example Excel 2010) to the Vault 2012 Server inside the Office application you get the error message:
"Failed to acquire a license.":

Please check the following:

1. Make sure you have configured the licpath.lic file properly on the ADMS Server inside the Vault Office 2012 program location which usually can be found here:
C:\Program Files (x86)\Autodesk\Vault Office 2012 (Server)

2. Make sure that you have a separate license for Autodesk Vault Office 2012 on your license Server.

It is not enough if you have already licenses for Vault Workgroup, Vault Collaboration, Vault Professional on your license Server.
An office client will only use an office license.

On your license Server the office license should look like this if you perform Status Enquiry on your LMTOOLS:

Users of 85843PCOFFI_2012_0F: (Total of X licenses issued; Total of Y license in use)