I found the solution myself. I removed the custom MGOS2.2 from the connectionproviders xml (was second item). An exception occured in the Maestro5 API when that file is missing and it did not load the rest of the items from the xml.
Hans... -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Maestro-4-to-5-migration-QueryMapFeatures-tp5064064p5064219.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
