hexagon logo
Register Sign in
  • State Not Answered
  • Replies 1 reply
  • Subscribers 7 subscribers
  • Views 58 views
  • Users 0 members are here
Options
Related

"The following subsystem file was not found" Error after reinstallation

walther.johnson
I recently reinstalled ADAMS and now I am not able to open old files because of the error above. These files worked before reinstalling, and I've tried adding the databases and all that all over again to no avail. If I create a file from a template and save them inside of the databases I'm able to open it normally.
 
The message above was shown while trying to open an assembly, but a similar thing happens when trying to open subsystems, except it says that it can't find the template file. I can confirm that the files are still in the same place as before, and that they exist.
 
The standard databases (acar_shared, etc) work normally.
 
Does anyone know what could have happened to my files, and what can I do to fix it?
Parents
  • 0
    Of course, after hours trying to figure it out, minutes after posting the question I found the answer by myself. Classic.
    Basically the files do not update the path if you update the database alias.
     
    For anyone that runs into this issue in the future, if you don't know the database alias go inside of your database, open the assemblies or subsystems folder, and right click the file and open with notepad or whatever other text editor you want.
    If you are looking at an assembly file, under the "SUBSYSTEM" header there will be a line USAGE: <database_alias>,
    where <database_alias> will be the files database alias. Take note of that.
    If you are look at a subsystem file, under the [SUBSYSTEM_HEADER] header there will be a line TEMPLATE_NAME, take note of what comes right after mdids://, and that's your database alias.
     
    With the database alias in hand, go to your ADAMS and add a new database, and make its alias whatever the file's alias is, and set the file path to be the path to that database. After you do this, you can simply open the subsystem/assembly as you normally would, but you have to choose the correct database alias when selecting from which database you want it to be.
Reply
  • 0
    Of course, after hours trying to figure it out, minutes after posting the question I found the answer by myself. Classic.
    Basically the files do not update the path if you update the database alias.
     
    For anyone that runs into this issue in the future, if you don't know the database alias go inside of your database, open the assemblies or subsystems folder, and right click the file and open with notepad or whatever other text editor you want.
    If you are looking at an assembly file, under the "SUBSYSTEM" header there will be a line USAGE: <database_alias>,
    where <database_alias> will be the files database alias. Take note of that.
    If you are look at a subsystem file, under the [SUBSYSTEM_HEADER] header there will be a line TEMPLATE_NAME, take note of what comes right after mdids://, and that's your database alias.
     
    With the database alias in hand, go to your ADAMS and add a new database, and make its alias whatever the file's alias is, and set the file path to be the path to that database. After you do this, you can simply open the subsystem/assembly as you normally would, but you have to choose the correct database alias when selecting from which database you want it to be.
Children
No Data
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement