Identity Mechanism and exception: LoggingDbDataReader to type SqlDataReader

3 posts, 0 answers
  1. Waqar
    Waqar avatar
    7 posts
    Member since:
    Apr 2014

    Posted 13 Nov 2014 Link to this post

    I created my model from the existing database. And then i modified Identity Mechanism to HighLow for a single domain class OMS_COUNTRY. I used that class here as:

    public ActionResult _Read([DataSourceRequest]DataSourceRequest request)
            {
                IQueryable<OMS_COUNTRY> CustomerList = this.dbContext.OMS_COUNTRies;
                DataSourceResult result = CustomerList.ToDataSourceResult(request
                    , ModelState
                    , c => new OMS_COUNTRYViewModel
                    {
                        OMS_COUNTRY_ID = c.OMS_COUNTRY_ID,
                        COUNTRYNAME = c.COUNTRYNAME,
                        ABBREVIATION = c.ABBREVIATION
                    });

                return Json(result);
            }

    This code was working till I modify Identity Mechanism to HighLow for all the rest of the classes. After changing the Identity Mechanism for every domain class to HighLow the existing code above throw this exception.

    Unable to cast object of type 'Telerik.OpenAccess.Runtime.Logging.LoggingDbDataReader' to type 'System.Data.SqlClient.SqlDataReader'.



  2. Waqar
    Waqar avatar
    7 posts
    Member since:
    Apr 2014

    Posted 13 Nov 2014 in reply to Waqar Link to this post

    Finally i managed to come out from this error by inserting rows in voa_keygen for each table that is using HighLow

    insert into voa_keygen values('OMS_PURCHASEORDER', 0); -- OMS_PURCHASEORDER is a table name using HighLow
  3. DevCraft banner
  4. Thomas
    Admin
    Thomas avatar
    590 posts

    Posted 18 Nov 2014 Link to this post

    Thanks for reporting this issue. I will try to reproduce this problem tomorrow and will let you now about the results.

    Regards,
    Thomas
    Telerik
     
    OpenAccess ORM is now Telerik Data Access. For more information on the new names, please, check out the Telerik Product Map.
     
Back to Top