Hi Andrew Brown,
We found the problem and it is that we are querying the sys.database_principals
table to obtain the default schema name for the current user. However, this table does not contain a record for the current user. The record for the group login used has the default_schema_name set to NULL, as group logins do not have default schemas.
Probably we will have to implement additional logic to handle this case and get the default schema for the dbo user. You can expect this to be fixed in one of the following internal builds or service packs. Until then, I am afraid you will have to use another login (not a group one) to create the domain model. Once you create the model and include all needed tables, you can switch back to the group login, there should be no problems at runtime. Please excuse us for the inconvenience caused.
the Telerik team
Register for the Q2 2011 What's New Webinar Week. Mark your calendar for the week starting July 18th and book your seat for a walk through of all the exciting stuff we will ship with the new release!