Admin Guide
Troubleshooting
QGIS

QGIS

If you encounter issues with QGIS, before you even try to use Pozi, check the QGIS User Guide.

https://docs.qgis.org/latest/en/docs/user_manual/

Additionally we’re compiling a list of common issues as a reference.

QGIS Desktop doesn’t open

If you experience an “Error loading QGIS” message, it may specify a file named qgis-ltr-bin.env that might not exist in your installation:

Error loading QGIS Oops, looks like an error loading QGIS

Details: Could not load qgis_app.dll Windows Error: The specified module could not be found.

Help: Check C:\OSGeo4W\bin\qgis-ltr-bin.env for correct environment paths

Use a text editor to recreate the missing file with the following content:

PATH=C:\OSGeo4W\apps\qgis-ltr\bin;C:\OSGeo4W\apps\qt5\bin;C:\OSGeo4W\apps\Python39\Scripts;C:\OSGeo4W\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32\WBem
GDAL_DATA=C:\OSGeo4W\apps\gdal\share\gdal
GDAL_DRIVER_PATH=C:\OSGeo4W\apps\gdal\lib\gdalplugins
GDAL_FILENAME_IS_UTF8=YES
JPEGMEM=1000000
OSGEO4W_ROOT=C:\OSGeo4W
PROJ_LIB=C:\OSGeo4W\share\proj
PYTHONHOME=C:\OSGeo4W\apps\Python39
PYTHONUTF8=1
QGIS_PREFIX_PATH=C:/OSGeo4W/apps/qgis-ltr
QT_PLUGIN_PATH=C:\OSGeo4W\apps\qgis-ltr\qtplugins;C:\OSGeo4W\apps\qt5\plugins
VSI_CACHE=TRUE
VSI_CACHE_SIZE=1000000
O4W_QT_PREFIX=C:/OSGeo4W/apps/Qt5
O4W_QT_BINARIES=C:/OSGeo4W/apps/Qt5/bin
O4W_QT_PLUGINS=C:/OSGeo4W/apps/Qt5/plugins
O4W_QT_LIBRARIES=C:/OSGeo4W/apps/Qt5/lib
O4W_QT_TRANSLATIONS=C:/OSGeo4W/apps/Qt5/translations
O4W_QT_HEADERS=C:/OSGeo4W/apps/Qt5/include
QGIS_WIN_APP_NAME=OSGeo4W\QGIS Desktop 3.22.8

Check that the GDAL_DATA and GDAL_DRIVER_PATH paths exist for your installation. If not, update the file accordingly.

If you are denied permission to create or edit the file in the destination location, create the file elsewhere and move it to C:\OSGeo4W\bin\ using Windows Explorer.

Further details about this issue

Layers from SQL Server are not visible

If a layer is not visible when added to QGIS, it may be because the geometry field name specified in the SQL Server geometry_columns name doesn’t match exactly with the layer’s geometry field name.

When inserting records into the SQL Server geometry_columns table, ensure the f_geometry_column value matches exactly with the geometry field name in the layer. This includes matching the case of the field name (ie, geom and GEOM are not the same field name).

See https://ukcommunity.arkance.world/hc/en-us/articles/21548201654034-QGIS-Not-Showing-SQL-Geometry

For more information about the SQL Server geometry_columns table, see https://www.spdba.com.au/qgis-geometry_columns-and-sql-server-spatial/

For general information about adding SQL Server layers to QGIS, see https://docs.qgis.org/latest/en/docs/user_manual/managing_data_source/opening_data.html#connecting-to-ms-sql-server

QGIS Server crashes

QGIS versions 3.40.9 and 3.40.11 may crash immediately upon launch on certain virtualised environments, with no profile folder created in %APPDATA% and no entries logged in Event Viewer. This behaviour has been observed on both Hyper-V and VMware servers.

Symptoms:

  • Application crashes immediately on launch
  • No profile folder or logs generated
  • Event Viewer shows no relevant entries
  • Setting QT_OPENGL environment variable has no effect

The issue is linked to graphics adapter compatibility. QGIS requires OpenGL 2.1+, but many virtual environments (especially Hyper-V) default to adapters supporting only OpenGL 1.1, which causes newer QGIS versions to fail silently.

QGIS 3.28 is more tolerant of older OpenGL versions and may work in environments where 3.40.x fails.

Recommendation:

  • Test with QGIS 3.28 if newer versions crash
  • Consider upgrading virtual GPU support or switching to environments with OpenGL 2.1+ compatibility
Last updated on
Info Display