<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body dir="auto">Hi,<div dir="auto"><br></div><div dir="auto">https://trac.osgeo.org/mapguide/wiki/ConfiguringAliases</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">Regards, </div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">Pierre</div><div><br></div><div align="left" dir="auto" style="font-size:100%;color:#000000"><div>-------- Message d'origine --------</div><div>De : mg@maw-gis.de </div><div>Date : 22-09-12 08 h 50 (GMT-05:00) </div><div>À : mapguide-users@lists.osgeo.org </div><div>Objet : Re: [mapguide-users] Migrating Mapguide 2.4 from Server2012 to 2019 </div><div><br></div></div>Hi Jackie,<br><br>that put me on the right track:<br><br>ERROR 4: `%MG_DATA_PATH_ALIAS[data_unmanaged]%Luftbilder/4442000_5470000.tif' does not exist in the <br>file system,<br>and is not recognised as a supported dataset name.<br><br>After replacing the alias with an absolute path, it works.<br>Do you have an idea why this doesn't work properly on Server2019?<br><br>The alias works for all other data sources.<br><br><br><br>Am 09.09.2022 um 10:56 schrieb Jackie Ng:<br>> If upgrading MapGuide is really not an option, then the only diagnostic recourse is to stop the <br>> MapGuide Server service and to run the MapGuide Server in interactive mode from the command-line <br>> (mgserver.exe run) and before running "mgserver.exe run", to set any appropriate GDAL environment <br>> variables to activate debugging (CPL_DEBUG=ON) and any additional diagnostic capabilities in the <br>> GDAL/OGR library.<br>> <br>> Some relevant links below:<br>> <br>> GDAL debugging in MapGuide: <br>> https://trac.osgeo.org/mapguide/wiki/MGOSGdalProviderFor26And30#Debugging <br>> <https://trac.osgeo.org/mapguide/wiki/MGOSGdalProviderFor26And30#Debugging><br>> <br>> GDAL environment variables list: https://trac.osgeo.org/gdal/wiki/ConfigOptions <br>> <https://trac.osgeo.org/gdal/wiki/ConfigOptions><br>> <br>> Hopefully by getting GDAL/OGR library to be more verbose, it can spit out the underlying cause for <br>> the "Fail to get image information" error that the FDO provider is sending to your MapGuide error log.<br>> <br>> You can ignore the MOSAIC/CLIP/RESAMPLE error as that's a nothingburger error explained in the <br>> thread that Pierre linked in an earlier reply.<br>> <br>> - Jackie<br>> <br>> You wrote:<br>> <br>> Hi,<br>> we have developed a special frontend based on fusion. It takes a lot of work to adapt them (and<br>> nobody would pay for it). All other 90 layers work perfectly, only the layers with tiffs cause<br>> problems. Something must have changed somewhere in the depths of Server 2019...<br>> <br>> <br>> -- <br>> /Please Note: I no longer create new posts or post replies to any OSGeo mailing list through nabble. <br>> As a result, you most likely won't see this message appear on nabble's view of any OSGeo mailing <br>> list and may only see this message through mailing list archives or depending on your mailing list <br>> subscription settings, through daily message digests or automated notifications from the mailing lists./<br>> <br>> _______________________________________________<br>> mapguide-users mailing list<br>> mapguide-users@lists.osgeo.org<br>> https://lists.osgeo.org/mailman/listinfo/mapguide-users<br><br>_______________________________________________<br>mapguide-users mailing list<br>mapguide-users@lists.osgeo.org<br>https://lists.osgeo.org/mailman/listinfo/mapguide-users<br></body></html>