Cannot Check In Assembly File - Unknown Server Error

[Lobos8403]

Noticing this error on some of my files.  I recently updated to Vault Server 2021. 

The message reference above is coming from the workstation that has vault server installed and is acting as the server.

My laptop will not allow me to open the same files when attempted to open from the Vault.

Was there a step i missed somehow when updating?  This only occurs with a seemingly random files, others can be checked in/out with no issue.

-David

[Kevin.Jaufmann-Ludwig]

Hi @Lobos8403 ,

the error tells that the .dwf files cannot be checked in. What if the dwf creation during checkin is disabled?

Will it check in fine?

Also: please also take a look at the Vault server logs on the time where this error occurred.

This might give us more details on the issue.

[Lobos8403]

This is what the server logs are saying.

[Kevin.Jaufmann-Ludwig]

So this entry in the log occurred on the time where the checkin failed?

If so this will not really help.

What about the other question?

[Lobos8403]

Kevin,

Where can i find this option to disable the dwf creation?

[cbenner]

@Lobos8403 

Hi...  when you are checking in the assembly, this option can be found here:

It is based on the visualization settings in Vault.  See if you can check the files in with this disabled. 

[Lobos8403]

I tried this.  Only one error message appears instead of the two now. 

[Lobos8403 · Accepted solution]

I figured this out myself.  I had to give AUTODESKVAULT user access to the folder where my vault was located.  Surprised this was never an issue before, however just giving AUTODESKVAULT read and write access to the directory where my vault files were located fixed it..

[jakub_d]

I have similar issues few times. I believe it can be related to Windows updates.

[jason_stephens]

This error message can also be related to a full drive where the filestore is located. I had this problem adding new files or checking in existing files. The dwf is the first file it tries to add. If you click Yes, the same message comes up with the .ipt or .iam and so on. After checking the server I noticed the drive was full so I deleted some old backups and everything started working again. Just an FYI for others that come across this post.