GAMS error while solving

[ShaiWinograd-zz]

Have anyone encountered the following gams error?

>>> scenario.solve()
Traceback (most recent call last):
  File "MsgScenario.java", line 1328, in at.ac.iiasa.ixmp.objects.MsgScenario.toGDX
  File "Scenario.java", line 1811, in at.ac.iiasa.ixmp.objects.Scenario.makeGamsDB
  File "GAMSWorkspace.java", line 252, in com.gams.api.GAMSWorkspace.<init>
  File "GAMSWorkspace.java", line 344, in com.gams.api.GAMSWorkspace.initializeAttributes
  File "GAMSWorkspace.java", line 381, in com.gams.api.GAMSWorkspace.getVersionInfo
Exception: Java Exception
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/vblasslab/envs/message_ix/message_ix/core.py", line 565, in solve
    super().solve(model=model, solve_options=solve_options, **kwargs)
  File "/vblasslab/envs/ixmp/ixmp/core.py", line 1670, in solve
    model.run(self)
  File "/vblasslab/envs/message_ix/message_ix/models.py", line 363, in run
    result = super().run(scenario)
  File "/vblasslab/envs/ixmp/ixmp/model/gams.py", line 276, in run
    self.in_file, ItemType.SET | ItemType.PAR, **s_arg
  File "/vblasslab/envs/ixmp/ixmp/backend/jdbc.py", line 510, in write_file
    self.jindex[ts].toGDX(str(path.parent), path.name, False)
com.gams.api.GAMSException: com.gams.api.GAMSException: Error retrieving GAMS release information

GAMS's technical support says it's not a GAMS issue.
I am running the model on a Linux server.
The GAMS release is - GAMSX 32.1.0 r75a5b5d Released Jul 31, 2020 LEG x86 64bit/Linux
and the java version is -

java version "9.0.1"
Java(TM) SE Runtime Environment (build 9.0.1+11)
Java HotSpot(TM) 64-Bit Server VM (build 9.0.1+11, mixed mode)

[khaeru]

The cause of this issue turned out to be a misconfiguration of the Linux server on which @ShaiWinograd was trying to run the software. The GAMS installation had been added to PATH, but not to LD_LIBRARY_PATH, and so the Java backend of ixmp could not locate the shared libraries needed for the GAMS API.

The issue was resolved by correcting the server configuration.