Error while configuring esa-snappy with Python 3.9.13 on Windows 11 - Configuration Failed - No Error Code

Hi Alvaro,

always hard to find if all is fine on one computer, but not on the one next to…

What are the operating systems on the two computers?

You should find your latest SNAP log files here:

  • Windows: $HOME\AppData\Roaming\SNAP\var\log or $HOME\ .snap\var.log
  • Unix: ~/.snap/system/var/log

I assume you did the SNAP module update 10.0.0 → 10.0.1 as described above?

Cheers
Olaf

1 Like

Hi Olaf,

I have Ubuntu 22.04.4 LTS on the computer where Snappy works fine and Debian 12 on the computer where Snappy doesn’t work.

I did the update 10.0.0 → 10.0.1 and I’m trying with Python 3.10.14.

Also, I checked the log but there’s nothing new with the attempt to configure Snappy.

Thanks again for your help,

Álvaro

Edit: I notice that the configuration are con /home/myUser/.snap/snap-python
But I have all my other data on anotherFolder/myUser/

The home folder it’s a network folder to work with various computers.

Hi Alvaro,

we also mainly work with Ubuntu platforms For further investigation, we’ll try to find/setup a suitable Debian environment to reproduce your problem, but this may take a little while. Of course, we could not test everything for the many existing Linux distributions…

In the meantime, could you provide the logs from both the ‘good’ and the ‘bad’ computer which contain the snappy configuration approach?

Your network folder setup should not make a difference, I assume this applies for both computers?

Olaf

1 Like

Hi Olaf,

I’ve notice that I was seeing the incorrect log path (I modify the path for .snap for another previous problem and I was seeing the older one, that doesn’t have the snappy log) so now I see the correct log.

It’s seems that the Python path were corrupted, so I installed Python 10 again and it’s working now.

Thanks again for your help and sorry for the problems I cause you.

Have a nice day!

Alvaro

good to hear, thanks for the update!
Olaf

1 Like

@dolaf Hello. I am having the same issue. I followed these steps to configure python3.10 to use snap. The configuration was sucessful and I did sys.append

At first when I tried to import esa_snap, I got the error related to jpy. After installing it, I got ‘RuntimeError: can’t find any JVM shared library’. What am I missing?

Hello nann,

could you please briefly provide the following information:

  • your operating system
  • your installed SNAP version
  • the subsequent steps you did, and the full error messsage(s) you observed.
  • the content of the log file <esa_snappy install dir>/snappyutil.log

Regarding the message: ‘RuntimeError: can’t find any JVM shared library’: I recently observed the same while testing on a MacOS system. I have no idea what was wrong or corrupt in the setup, but just moving to a new terminal window helped for me, and the issue was gone.

Hello Olaf,

Just reinstalled snap 11 and tried with both python 3.10.11 and 3.80. Now I have a new set of error. Error while parsing JAI registry.

Steps followed:

  1. Install python3.10.11 (or 3.8.0). Install snap directly to C:\esa-snap (as a post a saw here suggested). Then install snap plugin from desktop.
  2. Open bin folder C:\esa-snap\bin… and type cmd
  3. Enter snappy-conf path-to-python10.11 … no space name folders
  4. Configuration successful
  5. cd path-to-esa_snappy then path-to-python10\python.exe
  6. from esa_snappy import productIO
    Using python terminal: Error while parsing JAI registry file ‘"file:/C:/esa-snap/snap/modules/ext/org.esa.snap.snap-core/org-geotools/gt-coverage.jar!/META-INF/registryFile.jai’':
    Opening python from pycharm: RuntimeError: can’t find any JVM shared library

Hello nann,

the JAI registry error message is not related to esa_snappy, but to SNAP core modules. You can ignore it and continue using esa_snappy. - As esa_snappy internally makes use of the SNAP API, you will usually see a couple of SNAP log messages on your Python console when importing esa_snappy.This is a bit confusing, but to my knowledge cannot be avoided easily. Sorry for this little inconvenience.

Thanks for your reply, first lemme try it out.