[fdo-users] Resource ID does not refer to a valid feature source
Brad Nesom
kidsmake6 at msn.com
Thu Dec 9 14:48:57 EST 2010
Let me know how that 9.0 test goes.
On Thu, Dec 9, 2010 at 8:33 AM, Heddo Klandermans <h.klandermans at hawarit.com
> wrote:
> I installed MG Enterprise 2011 (incl. MG Studio 2011) and found all working
> well again (after some initial trouble) using the FDO 3.5
> PostgreSQL-provider (comes within the MG Enterprise package).
> Connection was made to PostGreSQL 8.4.5.1 /PostGIS 1.5.2.1
> Nice to know: Also MG Studio 2010 could be used to connect to the MGE 2011
> environment (based on Apache).
>
> In a next stage I will test the combination of MGE Studio 2011 and MG OS
> 2.2 and also the connection to the latest PostgreSQL 9.0 and PostGIS
> 1.5.2.3.
>
> Heddo Klandermans
>
>
>
>
> Op 23-11-2010 9:51, Heddo Klandermans schreef:
>
> Thx for your reply. I will try this option out.
> Another option might be to upgrade to MGStudio 2011. I will keep you
> informed about results.
>
> Heddo
>
> Op 22-11-2010 18:49, Greg Boone schreef:
>
> The PostGIS 3.4 provider has not been tested heavily with MG, and has fallen off the active development list now that the PostgreSQL provider has been released. I know that there were a number of outstanding defects logged against the PostGIS provider that were never resolved. You might want to try the FDO 3.5 release and its PostgreSQL provider to see if using that provider resolves your issues. However, that would mean you would need to move to the version of MG that is compatible with FDO 3.5.
>
> Greg
>
> -----Original Message-----
> From: fdo-users-bounces at lists.osgeo.org [mailto:fdo-users-bounces at lists.osgeo.org <fdo-users-bounces at lists.osgeo.org>] On Behalf Of Heddo Klandermans
> Sent: Friday, November 19, 2010 3:49 AM
> To: fdo-users at lists.osgeo.org
> Subject: [fdo-users] Resource ID does not refer to a valid feature source
>
> Hi,
>
> Using MapGuide Studio 2010 I can make a succesful connection to my
> database by FDO PostGIS connection (PostGreSQL 8.4 + PostGIS 3.4). Also
> (geometric) tables can be read to create layers.
> After performing some changes in the database table structure the Data
> connection was still ok, but MG had problems in getting table-data for
> the layers. I fixed this by a Vacuum Analyse on the database and finally
> a reindex. This worked well and solved the problems.
>
> After another change in my databse now data connection is still ok, but
> when trying to create a layer i get the message:
> "Invalid Stream Header Exception" followed by "Resource ID does not
> refer to a valid feature source".
>
> Any attempt to create a new folder and/or data connection in MG using
> FDOPostGIS connecting to that specific database gives the same problem:
> data connection is succesful, when creating a layer it displays these
> messages. Connecting to other databses does not give any problem.
>
> I think this problem is caused by mismatch between Library settings and
> Database. Did anyone experience similar problems and if so what can be
> done to it?
>
> Thx,
>
>
>
> --
> ir. H.D. (Heddo) Klandermans
> Senior Consultant
>
> Hawar Information Technology bv
> De Wymerts 7, 8701 WT Bolsward, NL
> Postbus 42, 8700 AA Bolsward, NL
> Tel.: (+31)-(0)515-570 333
> E-mail: h.klandermans at HawarIT.com
>
>
> _______________________________________________
> fdo-users mailing listfdo-users at lists.osgeo.orghttp://lists.osgeo.org/mailman/listinfo/fdo-users
>
>
> --
> ir. H.D. (Heddo) Klandermans
> Senior Consultant
>
> Hawar Information Technology bv
> De Wymerts 7, 8701 WT Bolsward, NL
> Postbus 42, 8700 AA Bolsward, NL
> Tel.: (+31)-(0)515-570 333
> E-mail: h.klandermans at HawarIT.com
>
>
> _______________________________________________
> fdo-users mailing list
> fdo-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fdo-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-users/attachments/20101209/74864d8f/attachment.html
More information about the fdo-users
mailing list