problem when working with drawing views

problem when working with drawing views

adam_krugG5YNQ
Contributor Contributor
273 Views
4 Replies
Message 1 of 5

problem when working with drawing views

adam_krugG5YNQ
Contributor
Contributor

Observed on Vault Professional 2026.

 

In my Vault setup the automatic generation of views is disabled. Recently my team started to use these views in a drawing review process (we annotate them). Users generate the views on demand, locally (not using the job processor).

 

Side note: a view is basically a hidden DWF file, that is generated and saved by Vault right next to the source file (DWG file in our case).

 

We noticed such problems:

1. Sometimes Vault says there's no view for specific file (although the DWF exists), we click "update" to generate it, Vault fails with the below message. The only workaround I found is to manually delete the DWF and regenerate the view in Vault

adam_krugG5YNQ_0-1777903735460.png

2. Sometimes Vault says there's no view for specific file (although the DWF exists), we click "update" to generate it, and surprisingly Vault succeeds to create the view.

 

Side note: I noticed, that files that have such problems are the ones that have the 'Visualisation attachment' set to 'None', and the ones for which Vault recognizes their view properly they have it set to 'System'. Thus far I don't see any difference between the ones for which Vault can regenerate the view vs the ones for which it fails.

 

A. Does anyone know why such situations happen?

B. And why sometimes Vault manages to generate the view once again and sometimes it doesn't?

C. Is there any other workaround than deleting the DWF file?

 

0 Likes
Accepted solutions (1)
274 Views
4 Replies
Replies (4)
Message 2 of 5

ihayesjr
Community Manager
Community Manager

When you get the error again, please click the Details button in the error message to see what it states as the restriction.

That would help.




Irvin Hayes Jr
Principal Product Manager
Autodesk, Inc.

Vault - Under the Hood Blog
0 Likes
Message 3 of 5

Andrew.WardDZPCJ
Contributor
Contributor

A. Does anyone know why such situations happen?

I occasionally have this issue also, and ask my Vault admin to delete the file. It appears to happen when the file is renamed.

 

https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/DWF-Create-FILE-is...

0 Likes
Message 4 of 5

adam_krugG5YNQ
Contributor
Contributor

The constraint is the file name constraint. Such file already exists.

0 Likes
Message 5 of 5

adam_krugG5YNQ
Contributor
Contributor
Accepted solution

I think I figured this out.

 

1. For the files that have the DWF file existing and targeting exact the current version, Vault successfully recognizes them as the preview

2. For the files that have the DWF file existing and NOT targeting exact the current version, Vault lets the user create the latest preview and it succeeds

3. For the files that have the DWF file existing, regardless of its version, but when the file was moved to different location since the preview was created, Vault will let user create the preview but will fail doing so due to the unique-file-name constraint.

4. Unfortunately DWF files cannot be moved using Vault UI, following popup emerge:
File XXXXXX.dwg.dwf cannot be moved directly because it is a Design Visualization file created by the system. Moving the associated parent file will move this file.

That implies that when DWG files are moved by drag-n-drop the DWFs get orphaned, but if they'd be moved using 'Move to folder' they'd most likely moved along.

 

 

"It's not a bug, it's a feature" sort of thing in Vault.

0 Likes