We have a different issue pertaining to SolidWorks.
Our issue occurs if a change happens to SolidWorks file within Vault where then the viz file needs to be updated. If we attempt to update either to the job queue or update locally, we the "A visualization file cannot be generated for a non CAD file". One specific instance happens if we need to update properties inside Vault. Sure, we can do this in SolidWorks and check the file(s) back in but this can be time consuming if we need to update multiple properties across multiple files.
I believe I was involved with the creation of the Autodesk knowledge post below. I worked with my resellers tech support team as well as Autodesk Tech Support.
"A visualization file cannot be generated for a non CAD file" when trying to generate DWF from file ...
All of the boxes are checked so to speak in our scenario when you apply all of the items suggested under the solutions given. The first bullet point stating "Check out the file, rebuild, and check back in using the appropriate CAD tool.", does in fact work, however, I do not see this as a solution. It is not efficient to do this and requires a huge effort when working with a large number of files.
What I find odd is, viz files will successfully generate all day long as files are pushed through our lifecycles and as long as we don't disrupt the state of the file after it has been checked in. What is cause the SolidWorks files to be seen as a "CAD" file from its initial check in, but as soon as it's modified within the context of Vault, it is now no longer recognized as a CAD file.
What's more unfortunate, is we did not see this issue until we upgraded from Vault 2023 to Vault 2025. This may have been an issue with Vault 2024 but was not seen by us as we typically upgrade in 2 version year increments.
I would love to see a solution to this issue that once again allows for the viz files (dwf's) to be updated locally or via the job queue. This is a constant frustration.