Interface for stored procedure ... not sufficient to pass the value for oid column

Thread is closed for posting
3 posts, 0 answers
  1. Alec
    Alec avatar
    43 posts
    Member since:
    Mar 2009

    Posted 21 Jun 2009 Link to this post

    We have our application using ORM with 2009.01.0311.1 and everything is fine. But then when we try to work on the applicaton on another PC, which using the latest version 2009.1 405, it throws this error when we commit something:

    Interface for stored procedure 'sp_oa_ins__address' not sufficient to pass the value for oid column 'AddressId' of table 'Address'.
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: Telerik.OpenAccess.Exceptions.MetadataException: Interface for stored procedure 'sp_oa_ins__address' not sufficient to pass the value for oid column 'AddressId' of table 'Address'.

    Source Error:

    Line 22:             scope.Transaction.Begin();
    Line 23:             scope.Add(ObjectRef);
    Line 24:             scope.Transaction.Commit();
    Line 25:
    Line 26:             return Convert.ToInt16(scope.GetObjectId(ObjectRef).ToString());
     

     

  2. Alec
    Alec avatar
    43 posts
    Member since:
    Mar 2009

    Posted 22 Jun 2009 Link to this post

    Now we uninstalled that machine's ORM and installed the one with 2009.01.0311.1 and it's the same still...
  3. PetarP
    Admin
    PetarP avatar
    754 posts

    Posted 25 Jun 2009 Link to this post

    Hi Alec,
    we had a bug with our service pack that was fixed in internal build 2009.01.0520.1. If you upgrade to this internal build or any later you should find this error fixed. Please do not hesitate to contact us if you have any further difficulties.

    Best wishes,
    Petar
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Check out the tips for optimizing your support resource searches.
Back to Top