FDO 3.4.0 - Failed to read identity properties (MS SQL)

4 messages Options
Embed this post
Permalink
miansi

FDO 3.4.0 - Failed to read identity properties (MS SQL)

Reply Threaded More More options
Print post
Permalink
Hello,

I am using MapGuide v 2.0.2 and decided to try to upgrade to MapGuide v2.1 Beta1 today.

Everything went fine, but attempt to create/update existing dataconnection give me long list of errors::

<2009-06-08T16:25:17> 5560 MapGuide Maestro v1.0.9.39693 ::1 Administrator
 Error: An exception occurred in FDO component.
        Item vw_Asset is already in this named collection.
 StackTrace:
  - MgFeatureServiceHandler.ProcessOperation() line 83 file c:\osgeo\mapguide_21\mgdev\server\src\services\feature\FeatureServiceHandler.cpp
  - MgOpGetIdentityProperties.Execute() line 113 file c:\osgeo\mapguide_21\mgdev\server\src\services\feature\OpGetIdentityProperties.cpp
  - MgServerDescribeSchema.GetIdentityProperties() line 1683 file c:\osgeo\mapguide_21\mgdev\server\src\services\feature\ServerDescribeSchema.cpp
  - MgServerDescribeSchema.DescribeFdoSchema() line 204 file c:\osgeo\mapguide_21\mgdev\server\src\services\feature\ServerDescribeSchema.cpp


Basically 1 error per table/view in my database. Any idea why it behaves like that? I've got 3 schemas in the database - dbo, audit and geo. audit schema has copy of all tables in dbo schema. geo schema has all geospatial views. Everything worked OK in MG 2.0.2 with FDO 3.3.2
Jackie Ng

Re: FDO 3.4.0 - Failed to read identity properties (MS SQL)

Reply Threaded More More options
Print post
Permalink
Have you tried looking at this data source with FDO Toolbox (http://fdotoolbox.googlecode.com) to see if you get the same problem?

- Jackie

miansi wrote:
Hello,

I am using MapGuide v 2.0.2 and decided to try to upgrade to MapGuide v2.1 Beta1 today.

Everything went fine, but attempt to create/update existing dataconnection give me long list of errors::

<2009-06-08T16:25:17> 5560 MapGuide Maestro v1.0.9.39693 ::1 Administrator
 Error: An exception occurred in FDO component.
        Item vw_Asset is already in this named collection.
 StackTrace:
  - MgFeatureServiceHandler.ProcessOperation() line 83 file c:\osgeo\mapguide_21\mgdev\server\src\services\feature\FeatureServiceHandler.cpp
  - MgOpGetIdentityProperties.Execute() line 113 file c:\osgeo\mapguide_21\mgdev\server\src\services\feature\OpGetIdentityProperties.cpp
  - MgServerDescribeSchema.GetIdentityProperties() line 1683 file c:\osgeo\mapguide_21\mgdev\server\src\services\feature\ServerDescribeSchema.cpp
  - MgServerDescribeSchema.DescribeFdoSchema() line 204 file c:\osgeo\mapguide_21\mgdev\server\src\services\feature\ServerDescribeSchema.cpp


Basically 1 error per table/view in my database. Any idea why it behaves like that? I've got 3 schemas in the database - dbo, audit and geo. audit schema has copy of all tables in dbo schema. geo schema has all geospatial views. Everything worked OK in MG 2.0.2 with FDO 3.3.2
miansi

RE: [fdo-users] FDO 3.4.0 - Failed to read identity properties (MS SQL)

Reply Threaded More More options
Print post
Permalink
Some javascript/style in this post has been disabled (why?)

Unfortunately this tool not working on x64 platform.

 

Andrei

 

From: Jackie Ng (via Nabble) [mailto:[hidden email]]
Sent: Monday, June 08, 2009 5:55 PM
To: Sinelnikov, Andrei
Subject: Re: [fdo-users] FDO 3.4.0 - Failed to read identity properties (MS SQL)

 

Have you tried looking at this data source with FDO Toolbox (http://fdotoolbox.googlecode.com) to see if you get the same problem?

- Jackie

miansi wrote:

Hello,

I am using MapGuide v 2.0.2 and decided to try to upgrade to MapGuide v2.1 Beta1 today.

Everything went fine, but attempt to create/update existing dataconnection give me long list of errors::

<2009-06-08T16:25:17> 5560 MapGuide Maestro v1.0.9.39693 ::1 Administrator
 Error: An exception occurred in FDO component.
        Item vw_Asset is already in this named collection.
 StackTrace:
  - MgFeatureServiceHandler.ProcessOperation() line 83 file c:\osgeo\mapguide_21\mgdev\server\src\services\feature\FeatureServiceHandler.cpp
  - MgOpGetIdentityProperties.Execute() line 113 file c:\osgeo\mapguide_21\mgdev\server\src\services\feature\OpGetIdentityProperties.cpp
  - MgServerDescribeSchema.GetIdentityProperties() line 1683 file c:\osgeo\mapguide_21\mgdev\server\src\services\feature\ServerDescribeSchema.cpp
  - MgServerDescribeSchema.DescribeFdoSchema() line 204 file c:\osgeo\mapguide_21\mgdev\server\src\services\feature\ServerDescribeSchema.cpp


Basically 1 error per table/view in my database. Any idea why it behaves like that? I've got 3 schemas in the database - dbo, audit and geo. audit schema has copy of all tables in dbo schema. geo schema has all geospatial views. Everything worked OK in MG 2.0.2 with FDO 3.3.2

 


This email is a reply to your post @ http://n2.nabble.com/FDO-3.4.0---Failed-to-read-identity-properties-%28MS-SQL%29-tp3046089p3046406.html
You can reply by email or by visting the link above.

 

----Notice Regarding Confidentiality----
This email, including any and all attachments, (this "Email") is intended only for the party to whom it is addressed and may contain information that is confidential or privileged. Sierra Systems Group Inc. and its affiliates accept no responsibility for any loss or damage suffered by any person resulting from any unauthorized use of or reliance upon this Email. If you are not the intended recipient, you are hereby notified that any dissemination, copying or other use of this Email is prohibited. Please notify us of the error in communication by return email and destroy all copies of this Email. Thank you.

miansi

Re: FDO 3.4.0 - Failed to read identity properties (MS SQL)

Reply Threaded More More options
Print post
Permalink
In reply to this post by Jackie Ng
OK. I think this deserves a ticket :-)

After further investigation I discovered that FDO do not like database objects with the same name to be part of different schemas.

i.e. if you have table dbo.Asset - it will throw an exception if you also have table audit.Asset or geo.Asset.
Although I cannot confirm as of right now if it is an exception or just a warning, because Maestro give you an option to save dataconnection.


Andrei


Jackie Ng wrote:
Have you tried looking at this data source with FDO Toolbox (http://fdotoolbox.googlecode.com) to see if you get the same problem?

- Jackie