Sorry for the delayed reply.
While obtaining information for an Oracle database, we filter out certain system schemas in order to avoid reading in unnecessary (in most cases) information. To do this we have a filter that filters out schemas ending in 'SYS'.
The error 'Value cannot be null', occurs when you have a FK constraint between 2 tables and we cannot read the information for the destination table. This might be because the existing credentials do not have rights to read information of this table (maybe because it is in another schema and there are no rights to read this schema).
Is this the situation in your case? Do you have references across schemas in your database or limited rights to certain tables?
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?
Telerik Public Issue Tracking
system and vote to affect the priority of the items