This question is locked. New answers and comments are not allowed.
I have been working with OpenAccess all day and adding classes and making them Persistent and it has been working great. It will auto generate the tables and all without a hitch until I came hit this error:
OpenAccess Error: Not all delayed fixup objects could be resolved. Such objects could be cyclic IObjectReferences, IObjectReferences that return other IObjectReferences too many times (i.e. objects with too long an IObjectReference chain) or nested valuetypes.
I have no idea what I changed that caused that or what it is really trying to tell me. Any ideas or suggestions on where to look? I have been adding a ton of classes and fields so it could be anything to me.
Where should I look?
5 Answers, 1 is accepted
0
Hello Jonathan Marbutt,
This seems to be a serialization exception, can you tell me where you are getting it? A stacktrace is always helpful as well.
Sincerely yours,
Jan Blessenohl
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
This seems to be a serialization exception, can you tell me where you are getting it? A stacktrace is always helpful as well.
Sincerely yours,
Jan Blessenohl
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
0
Jonathan
Top achievements
Rank 1
Rank 1
answered on 20 Jan 2010, 08:58 PM
I get the error when I run compile the app and it runs the UpdateDatabase. Doesn't give me any more detail than that.If I turn off UpdateDatabase on the project it works fine. It has been working all day though and not sure what changed.
0
Hi Jonathan Marbutt,
Can you try to start with a fresh database? Maybe the schema migration process is the problem.
Kind regards,
Jan Blessenohl
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Can you try to start with a fresh database? Maybe the schema migration process is the problem.
Kind regards,
Jan Blessenohl
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
0
Luca Sormani
Top achievements
Rank 1
Rank 1
answered on 07 Mar 2010, 02:17 AM
I have the same problem.
In my case I'm doing a Forward mapping and this error happen when I change an existing Mapping, a n:m Collection with already Cascading Delete and Managed Collection selected. When I add Preserve Order and recompile the project I get the above error.
Am I doing something wrong or is this a bug?
0
Hello Luca Sormani,
Can you switch off the database update and do a
Database.Get("DatabaseConnection1").GetSchemaHandler().CreateUpdateDDLScript(null);
and catch the exception. Can you send me the stacktrace plus the InnerException if it is there?
The code should do the same as the schema update in the VS.
All the best,
Jan Blessenohl
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
Can you switch off the database update and do a
Database.Get("DatabaseConnection1").GetSchemaHandler().CreateUpdateDDLScript(null);
and catch the exception. Can you send me the stacktrace plus the InnerException if it is there?
The code should do the same as the schema update in the VS.
All the best,
Jan Blessenohl
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.