Drawing properties not updating upon check in after Vault 2025 upgrade

[Brett.Trimpe]

Recently upgraded from Vault Pro server 2023 to 2025 and noticed that changes on the mapped attributes on our DWG were not being passed along to Vault at check in. The visualizations and everything are correct but if we synchronize properties, Vault will overwrite the drawing with the previous version's values. As of now, all other functions seem to work. 

We were running SQL server 2016 SP3 and thought maybe it was because of this so we upgraded to SQL server 2022 but are still seeing the same results. We are in the process or doing a re-index just in case. 

Anyone see any similar issues when they upgraded to 2025?

[ihayesjr]

I replied to your message.

What category do the drawings get assigned to on first check-in?

[jamesY3MCP]

I can confirm that i am having the exact same issue.
however the config i am using is significantly simpler.
a single AutoCAD (Vanilla) block with just a few Attributes.
each Vault UDP only has a single mapped to the one block.

Issue

 - 1. When Checking in a drawing from AutoCAD 2025, the Vault does not read the values from the AutoCAD Title Block.
 - 2. Select Properties, then go to mapping, attempt to create a new mapping. Click "Import from Vault", Select a drawing with the desired Title Block. This results with the following error (Screenshopt).

If i use "Import from file" it works correctly.

After mapping, i can update the value in Vault and the bidirectional mapping, correctly updates value in the block

[jamesY3MCP]

I can confirm that i am having the exact same issue. 

I have done the Mapping correctly. i have listed my block on the server "A3FRAME" 

I have reproduced this on several Virtual Servers with different Vault Databases

Issue

 - 1. When Checking in a drawing from AutoCAD 2025, the Vault does not read the values from the AutoCAD Title Block.
 - 2. Select Properties, then go to mapping, attempt to create a new mapping. Click "Import from Vault", Select a drawing with the desired Title Block. This results with the following error (Screenshot).

If i use "Import from file" it works correctly.

After mapping, i can update the value in Vault and the bidirectional mapping, correctly updates value in the block

[jamesY3MCP]

Ok, I have worked out the issue.
Unfortunately, it was an operating system issue. I was running Windows Server 2016. after upgrading to 2022 the issue disappeared.