Docs
Search K

Appearance

Autodesk Vault ​

This check confirms the server can connect to Autodesk Vault. The Autodesk Vault Client must be installed and correctly licensed so the Automations engine can open a connection to Vault and perform Vault operations. The Vault client is also what provides Inventor export.

Readiness check

On the engine home page, the Autodesk Vault check confirms a supported Vault Client is installed. It must show Passed before Vault tasks will run. See Server Readiness.

Supported versions ​

ApplicationAutodesk Vault Client, 64-bit
Supported versions2025, 2026, 2027

Only Vault Client 2025, 2026 and 2027 are supported. The engine uses the newest installed supported version. Earlier versions are not supported.

Concurrency ​

Vault tasks are not serialised — multiple Vault connections can run at the same time, so Vault operations execute in parallel across concurrent workflows. (Note that Inventor export, which also uses the Vault client, is limited to one at a time.)

Setup ​

  1. Install the Autodesk Vault Client (a supported version) on the automation server, 64-bit.
  2. License the Vault client correctly. The client must be activated/licensed so it can sign in to your Vault server. Without a valid licence, the engine cannot open a connection and Vault tasks will fail.
  3. Configure the Autodesk Vault service account that workflows use to connect (server, vault name, credentials). See Service Accounts.
  4. Re-run the readiness check (restart or reload the engine home page) and confirm Autodesk Vault shows Passed.

The Autodesk Vault readiness check showing Passed

Troubleshooting ​

SymptomCause & resolution
Check fails: Vault Client was not detectedThe Vault client is not installed. Install a supported version (2025/2026/2027), 64-bit.
Check fails: version X is installed, but 2025 or higher is requiredAn unsupported, older Vault client is installed. Upgrade to 2025, 2026 or 2027.
Check passes but Vault tasks fail to connectThe Vault client is installed but not licensed correctly, or the service account credentials are wrong. Confirm the client is activated and the Vault service account details are correct.
Vault tasks are slow under loadVault connections run in parallel — review the Hardware Readiness recommendation and the job queue concurrency setting.

Tentech