[mapguide-users] Migrating Mapguide 2.4 from Server2012 to 2019

[Jackie Ng]

If upgrading MapGuide is really not an option, then the only diagnostic
recourse is to stop the MapGuide Server service and to run the MapGuide
Server in interactive mode from the command-line (mgserver.exe run) and
before running "mgserver.exe run", to set any appropriate GDAL environment
variables to activate debugging (CPL_DEBUG=ON) and any additional
diagnostic capabilities in the GDAL/OGR library.

Some relevant links below:

GDAL debugging in MapGuide:
https://trac.osgeo.org/mapguide/wiki/MGOSGdalProviderFor26And30#Debugging

GDAL environment variables list:
https://trac.osgeo.org/gdal/wiki/ConfigOptions

Hopefully by getting GDAL/OGR library to be more verbose, it can spit out
the underlying cause for the "Fail to get image information" error that the
FDO provider is sending to your MapGuide error log.

You can ignore the MOSAIC/CLIP/RESAMPLE error as that's a nothingburger
error explained in the thread that Pierre linked in an earlier reply.

- Jackie

You wrote:

Hi,
we have developed a special frontend based on fusion. It takes a lot
of work to adapt them (and
nobody would pay for it). All other 90 layers work perfectly, only the
layers with tiffs cause
problems. Something must have changed somewhere in the depths of Server 2019...


-- 
*Please Note: I no longer create new posts or post replies to any OSGeo
mailing list through nabble. As a result, you most likely won't see this
message appear on nabble's view of any OSGeo mailing list and may only see
this message through mailing list archives or depending on your mailing
list subscription settings, through daily message digests or automated
notifications from the mailing lists.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapguide-users/attachments/20220909/0401e134/attachment.htm>