2022 Custom Content center on 2023 Vault Server

[Fazlur_Rahaman]

Hi guys, 

We recently upgraded to the 2022 version, specifically Inventor and Vault Client. However, our IT department, in consultation with IMAGINiT, decided to upgrade the server to the 2023 version under the impression that it would be backward compatible. While most things are functioning as expected, we have encountered an issue with the custom Content Center Library.

Whenever I attempt to upload the custom Content Center using the "From Inventor Desktop Content to Autodesk Vault Server" to Vault through the Project tab, an error message pops up stating that it's an "Unsupported server version." And if I update the Content Center first to the 2023 version using the provided update tool (I had to do this using 2023 Inventor), I am able to upload the library to Vault. However, there's a problem when I try to access the library using the "Place from Content Center" command in Inventor 2022, as the library remains invisible.

I'm wondering if anyone has come across a solution to this issue or if I'll have to wait until our organization decides to upgrade Inventor to the 2023 version, which could potentially take several years. Any recommendations would be greatly appreciated.

Thanks

FR

[Gabriel_Watson]

The Vault server (ADMS) should tell you if the CC libraries there are all 2023 or if some were left as 2022. I think whoever upgraded the Vault Server should have left a copy of the custom library in 2022 format.

Migrating customized CC library in Vault Server:
https://help.autodesk.com/view/INVNTOR/2023/ENU/?guid=GUID-CEA48D57-577A-4551-BD71-9303AEAEC5DC

[Fazlur_Rahaman]

This is a new custom library i am trying to add/upload to the Vault. This library was not there during the upgrade. All the previous standards (ANSI, DIN, ISO, etc) were left in 2022 and are accessible using Inventor 2022.  

[Gabriel_Watson]

Did you do Step 1 of this list?
https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Inventor-Desktop-C...

[Fazlur_Rahaman]

Yes, those were the steps I have followed. When I get to Step 5, that's when I get the error saying the Server version doesn't match. 

[GunnarNilsson · Accepted solution]

Library transfer from local cc to vault server can only be done on the same version, e g 2022 to 2022 or 2023 to 2023.

To get your local 2022 cc to your 2023 server you first need to set up a temporary 2022 server and transfer your local cc to that server. Then you export that cc from the 2022 server and import it to the 2023 server. 

[Fazlur_Rahaman]

Thank you for the suggestion. I will see if I can get IT to create a temporary 2022 server for this transfer. I will report back if it worked. 

[Fazlur_Rahaman]

Hey @Gabriel_Watson  & @GunnarNilsson ,

Given that the Vault Pro server requires features from Window server 2016/2019, can I just install the Vault Basic on my local station and import/export the CC? 

Does the Vault basic have the export function and will that export function be compatible with Pro version? I am assuming there are some key differences in how the database work between the Pro and Basic. 

[GunnarNilsson]

You can very well use Vault Basic Server 2022 if you wish. All Vault Editions handle cc libraries the same way. But just for export/import cc libraries Vault Pro Server is ok on Windows 10.

[Fazlur_Rahaman]

Hi @GunnarNilsson ,

I have exported the CC.mdf file using the Vault Basic and when I tried to import it into the Vault Pro 2023, I got the following error. 

I tried manually dumping the files (CC.mdf  & CC_log.idf) into the DBs folder and using the Attached Library command, I got the same error. 

[GunnarNilsson]

Haven't seen that error before. Maybe you do need a Vault Pro 2022 server to make the transfer to, or you have an error in your database. 
Try making the transfer of the local cc once more first. Check this out as well:

https://www.stellarsqldatabaserecovery.com/blog/sql-database-error-5172-the-page-control-property-is...

[Fazlur_Rahaman]

Hi @GunnarNilsson , 

I was able to upload the library after using Vault Pro 22 to export. But now I run into this error. 

I suspect this is due to uploading 2023 version and deleting it from the initial test.

I did some searching and found the following solution from Autodesk: 

Is there any other way to fix this without detaching the database? IT is not too thrilled when it comes to this type of change. We tried renaming and that didn't work. 

[GunnarNilsson]

You need to delete or detach the the 2023 version of the cc.