Trying to install the remote content center libraries for 2024 and it failing.

[shastu]

I have just upgraded Vault to 2024 and now I am trying to install the 2024 libraries.  I have downloaded the executable from my Autodesk account.  For example, one of them is InventorDIN.exe but when I try to run the executable I see an Autodesk Install window that says it is "Unable to install"  a required install component is missing or corrupted.  Error 3051.  I just have the ADMS installed on the server, not Inventor itself and I don't want to have to install Inventor on the server.  If I try the Import Library from the ADMS console, it wants a MDF file, not an executable.  So what am I doing wrong?

[CGBenner]

@shastu 

Hello.  I'm a little confused, do you want to install Remote Content Libraries (stored locally or on a shared network location), or Vault Content Libraries (located in the ADMS server).  Local libraries would be installed on your own machine, or on a network drive and then configured into your Inventor projects.

[shastu]

When you upgrade the Vault Server, the read-only libraries from Autodesk are not migrated because they are read-only.  From what I understand, you have to download them and install them.  Are you saying that I am not downloading the correct libraries and that those executables are not for an ADMS setup on a server?  If that is the case, where do I go to get the 2024 versions.  See screenshot of our old ADMS before the upgrade.

[shastu]

Here are the instructions I see from Autodesk:

Installation Instructions

• From the Autodesk web site, select and download the Remote Content Center Libraries for Inventor Professional 2024 that you wish to have ongoing access to.
• Save the downloaded executable(s) locally.
• Ensure Vault Server 2024 is installed, but not running.
• Extract each library by double clicking the .exe file. All libraries will be extracted into a default location, or you can specify a custom destination folder. To install all your libraries in a single operation, use the same extraction location.
• Browse to the extraction location to ensure all libraries were extracted successfully.
• If you are using the default username and password for the Vault and SQL servers, then within the extraction location, double click the setup.bat file. All libraries present will be installed into the Vault Server 2024 database. If you do not want to install a specific library, simply delete its zip file before running the setup.bat file.

NOTE: If you are using a non-default username and password for the Vault or SQL servers, you will need to modify the setup.bat file before double clicking to start the library installations. Using a text editor, modify the lines 6 to 11, starting with SET, appropriately. Do NOT make any changes below line 12 and ignore the remark lines starting with REM.

1. Open the Autodesk Data Management Server Console and verify that all libraries were installed successfully...

So this is what I have done.  I made sure that the ADMS Console was not opened and that the Process in the Task Manager was not there.  Then I doubleclicked on the InventorDIN.exe and got the error.

[shastu · Accepted solution]

So I finally broke down and went ahead and installed Inventor on the server and even though I can't actually get it to run/open on the server, I was then able to double click on the exe files and it was able to do its thing.  So then I tried to run the bat file and I got this error:  MigrateKnowledgeVaultMater:Error code -1.  So then I opened the actual zip file that it created and from the zip file I copied the contents out to a directory.  Then I opened up the ADMS console and did an import of the mdf file that I had copied to the directory and that finally worked.  None of this was required in the previous version which was 2021 for us.  Definitely feels like a step backwards from what was required in the past.  FYI, after I got this accomplished I realized that the MigrateKnowledgeVaultMater:Error code -1 was probably due to the fact that I didn't fill out the .bat file out correctly.  Also, I realized that I don't think I would have had to install Inventor on the server.  I probably could have just run the executables on a machine that already had Inventor on it, and then moved the zip files over to the server and continued the process.

[CGBenner]

@ihayesjr do you have any advice for @shastu ?

[ihayesjr]

I think you had other problems, as the library installer does not require Inventor.

Also, on the Vault Server, you could extract the zip files, place the database files in the same location as all of the other Vault databases, and run the Attach Library command. You should not have performed the Import.

If you are running with the imported libraries, you should detach these libraries and attach the original libraries.

[shastu]

I don't know what to tell you but I tried installing the libraries on two different servers that only had ADMS on them and was unable to on both of them.  As soon as I installed Inventor on the server then I was able to run the library executables.  As far as the import versus Attach, I guess I don't understand why it matters.  What do you mean when you say "original" libraries?  There are not two sets of the same library, one of which is an original and one that is not.

[ihayesjr]

My point is that you "imported" the libraries when you should have "attached" them. That is my recommendation for you in this scenario. You can choose to continue as you are if you want.

I will check why you need to have Inventor installed to install the libraries.

[shastu]

I appreciate your recommendation.  I guess I am just asking for more information.  Can you tell me why you recommend that because from what I can tell, both methods give me the same results.  So can you tell me what the downfall is of the import?

[ihayesjr]

You are correct. Both behaviors give you the same results. I was thinking of some legacy intentions and behaviors. 

[colin]

Irvin,

I am having an identical error trying to install the Content Center libraries on my 2025.1 Vault Pro Server. I get "Error 3051: A Required Install Component is Missing or Corrupted" when I try to run the EXE of any library executable. I found this thread while trying to search for a fix.  The Vault ADMS is a new install in a new Win 2022 server, and seems healthy and happy with a 2025.1 patch. What am I missing?

<This linked Help doc> seems to say that I need to install the Content Center on my local machine, and then upload the Content through Inventor, and does not show a way to just install them directly on the server. Is that correct?

Thanks!

Colin

[GunnarNilsson]

In that document point 1, 2, 5, 6 and 7 is what you need to do. The other points is what you can do, if required.

You only need to install standard content libraries on the server, as point 2 states.

[colin]

Thanks for clarifying that points 3-4 are optional. In that case, I’m stuck at point 2 with error 3051.

[GunnarNilsson]

I suggest you check this out then:
https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/A-required-install...

[GunnarNilsson]

You can also do a manual install. 

Open the dowloaded InventorDIN.exe with e g 7zip, Drill down to \x64\DIN and execute InventorDIN.exe which is a self extracting file as it was before v2024. Extract it and you'll get a zipfile with the databases in it.

[colin]

Thanks very much, @GunnarNilsson. Between your last two posts I was able to connect the libraries. I appreciate your responses.

For the record...

I tried the AdODIS-installer.exe method first, and that did get rid of the error and unzipped the libraries without needing 7zip. I then edited the Vault credentials in the included batch file that appeared in the unzipped contents. However, when I ran the batch file as Administrator I got the same error that @shastu did (MigrateKnowledgeVaultMater:Error code -1). But, I was able to open ADMS on the server and right-click on Libraries, and manually Attach each library using the Advanced tab; that part was the smoothest part of this whole process. Once I set Inventor to look at the Vault library, it looks like everything is working now.

Man, that is NOT a clearly-documented process. If it takes a forum post and 2-3 different knowledge base articles to do one task, it seems like a documentation revision would be appropriate.