Hello community
When running the pollination model using the farms map, I got the following error:
2024-05-06 14:44:17,923 (natcap.invest.utils) utils.prepare_workspace(166) ERROR Exception while executing natcap.invest.pollination
Traceback (most recent call last):
File “natcap\invest\utils.py”, line 164, in prepare_workspace
File “invest\cli.py”, line 470, in main
File “natcap\invest\pollination.py”, line 536, in execute
File “taskgraph\Task.py”, line 336, in init
File “retrying.py”, line 49, in wrapped_f
File “retrying.py”, line 212, in call
File “retrying.py”, line 247, in get
File “six.py”, line 719, in reraise
File “retrying.py”, line 200, in call
File “taskgraph\Task.py”, line 1561, in _execute_sqlite
sqlite3.OperationalError: invalid uri authority: ags-fs-profiles
2024-05-06 14:44:17,945 (natcap.invest.utils) utils.prepare_workspace(169) INFO Elapsed time: 5m 16.980000000000018s
2024-05-06 14:44:17,952 (natcap.invest.utils) utils.prepare_workspace(172) INFO Execution finished
InVEST-natcap.invest.pollination-log-2024-05-06–14_39_00.txt (20.2 KB)
Kind regards
Sibylle
Well that is an interesting and unusual error! Thanks for including your logfile.
Based on the parameters logged, it appears that you have your workspace in a network drive. This is very likely the cause of the database locked errors as well. To make sure that this is the issue, could you set your workspace to somewhere on your local computer (somewhere you have write permissions) and try re-running the model? You can always copy the workspace over to your network drive later if you prefer.
Let us know how this goes,
James
Dear James
Thanks very much for your reply. Yes indeed I was aware that my error is probably linked to the virtual IT machine. I already sent a message to the my institute’s IT service. However, InVEST worked now for months using the same workspace. Additionally I reinstalled InVEST on the desktop of the virtual machine. Nevertheless, InVEST is working fine on my private computer. I assume that
the institute now blocked the InVEST app.
Kind regards
Sibylle
Interesting! I would not have expected a crash like this to just occur suddenly, so I’m curious if IT has changed something, as you mention.
Does the issue happen if you change the workspace to another location on the remote machine? Perhaps a different folder also on your desktop?
James
Hello James
Yes I reinstalled InVEST on different locations including desktop of the virtual machine. However, at the Desktop version I was not able to open InVEST.
Kind regards
Sibylle
To confirm: is the logfile linked above (which has lots of errors in it and then finally an exception) from the desktop installation on the VM?
Could you attach a logfile from when InVEST ran successfully (or at least did not exhibit this same behavior) when you were using a different workspace location?
Thanks,
James
InVEST-natcap.invest.pollination-log-2024-03-11–09_40_06.txt (423.8 KB)
Dear James
Find enclosed the log file used some weeks ago with the same InVEST installation at the same place of the virtual machine: AppData_Roaming
So yes hte first log file is on the AppData/Roaming place of the virtual machine.
Sibylle
InVEST-natcap.invest.pollination-log-2024-05-06–20_41_04.txt (426.6 KB)
And here the logfile of my private computer. InVEST works fine there.
Sibylle
Dear James
Thank you very much for your feedback. I have been able to report the error with the InVEST app to my department’s IT helpdesk.
Yes, it is definitely a problem with the authorisation. I am not allowed to install any apps or programmes on the personal desktop or on the virtual computer. Unfortunately, the app was probably blocked later. It is still strange, that the app was running for months.
The (inefficient) solution is now to run InVEST on my personal computer and then transfer the output to the storage place at my working location…
Sibylle
@jdouglass