To resolve MapGuide publishing errors
- On the Publish To MapGuide
Results dialog box, click View Log.
For information on publishing
and viewing results, see Publishing to MapGuide.
- Examine the log file to see which layers
failed and why.
- Resolve the publishing errors in the
- Errors due to joined data: You
can detach the joined data from the layers before publishing to
omit that data but still publish the layers. If you must include
the joined data, save layers with joined data to SDF format (which converts
the join into a flat table), remove the layers from the map (turning
them off is not sufficient), and publish the resulting map. Then
copy the SDF containing the joined data layer to the MapGuide server.
This places a “static” copy of the data on the server (the features
no longer point to the original databases and data). You must reconstruct
the map on the server to add the SDF layer back in. For information
on how to save a layer to SDF, see Saving or Exporting a Display Manager Layer.
- Errors resulting from layers
without assigned coordinate systems: Display the Data
Connect dialog box, select the data source whose layers
are missing a coordinate system, and click Edit
Coordinate Systems. Click Edit and select
a coordinate system. Click OK in both
dialog boxes to apply your changes.
- ODBC DSN errors: If
feature sources in the map use an ODBC DSN (Data Source
Name) on the local computer, the DSN must exist on the
machine where the server resides, and it must have the same name
as the DSN on the local machine.
- Errors related to missing
provider components on the server: If you publish a map
layer from a provider that requires software or components, such
as an Oracle database, ArcSDE data source, SQL server, or a third-party
database provider you set up, you must install that software on
the MapGuide server and configure it correctly. For example, if
you publish a layer from an Oracle database, you must install the
Oracle client on the server.
NoteMapGuide Enterprise installs some provider
support automatically, while the open source version does not. However,
in both cases, you will need to install components for some providers.
- Errors due to a failure
to determine the source data type or read the configuration file: These
errors are usually the result of using data from third-party FDO
Providers. Contact Autodesk technical support, or the support group
for the FDO Provider you are using.
- Errors due to existing
files on the server: If you specified that this publish operation
should stop if it encounters existing files with the same names as
new ones, and if those files exist, you can either remove the existing files
from the server or change the publishing options to overwrite the existing
files. For more information, see Publishing to MapGuide.
- Errors due to invalid characters: Rename
the offending files or folders to avoid invalid characters.