Opened 15 years ago

Closed 15 years ago

#1123 closed defect (wontfix)

MGOS 2.0.2 or MGOS 2.1 not compatible for using PostGIS 1.4

Reported by: ssddgreg Owned by:
Priority: high Milestone:
Component: General Version: 2.1.0
Severity: blocker Keywords: postgis
Cc: dejan.gregor@… External ID:

Description

I have seached several forums for more than two working days for solution to error in Windows environment (32-bit) - reporduced on Windows XP and Windows Server 2003

"Failed to read schema from data source" The Operation gave the error message. The remote server returned an error: (559) MgConnectionFailedExeception.:Cannot establiosh connection."

Please note that PosrGRESQL 8.4 is running well, as well as PostGIS module. All required DLL files from PostGRESQL 8.4 were copied to the Program Files\OSGeo\MapGuide\Server\Fdo folder and restarted the MapGuide Server service.

However, Data Connection was tested successfull without any errors, just when trying to select the PostGIS data connection, it fails.

The same occurs with the Autodesk MapGuide Studio 2010 when accessing the MGOS 2.1 beta.

It is an essential step in our solution for our customer and we need to know, if this works on Windows platforms well. For now, we did not have any success and would need good support in this. Already reported to Autodesk for the MGE Studio 2010.

pg_hba.conf host all all 127.0.0.1/32 md5 host all all 0.0.0.0/0 trust

pg_ident.conf empty

postgresql.conf listen_addresses = '*'

No firewalls enabled, no antivirus installed.

Attachments (2)

002.JPG (96.8 KB ) - added by ssddgreg 15 years ago.
MapGuide Maestro
001.JPG (33.6 KB ) - added by ssddgreg 15 years ago.
Mapuide Maestro

Download all attachments as: .zip

Change History (3)

by ssddgreg, 15 years ago

Attachment: 002.JPG added

MapGuide Maestro

by ssddgreg, 15 years ago

Attachment: 001.JPG added

Mapuide Maestro

comment:1 by tomfukushima, 15 years ago

Resolution: wontfix
Status: newclosed

A while ago, I tried using this with 1.4/8.4 as well, but it didn't work for me. However, I believe that this works with 1.3(?)/8.3. As this is a PostGIS provider issue, please create a ticket in the FDO trac against the PostGIS provider.

Note: See TracTickets for help on using tickets.