Try Now
More in this section

Forums / 3.x Pre-release forums (retired) / Generic content control SQL exception

Generic content control SQL exception

2 posts, 0 answered
  1. Jim Drain
    Jim Drain avatar
    2 posts
    16 Sep 2003
    12 Jan 2007
    Link to this post

    Hello Telerik,

    Ran into this while building pages.  When editing a page using generic content if you do a browser refresh before clicking on finish then an SQLException for update conflict is caused.

    [SqlException (0x80131904): Update conflict]
       Nolics.ORMapper.DataProviders.SQLBlockBuilder.EndStatement(SQLCommandEventArgs args, DataRow row) +526
       Nolics.ORMapper.DataProviders.SQLBlockBuilder.ExecCommandProcedure(StmtContext context, DataRow data) +779
       Nolics.ORMapper.DataProviders.SQLBlockBuilder.ExecuteCommand(StmtContext context, DataRow data) +76
       Nolics.ORMapper.DataProviders.SQLDataProvider.Update(DataSet updateData) +903
       Nolics.ORMapper.Base.Transaction.Commit(Boolean fCleanIfSuccess) +756
       Nolics.ORMapper.Base.Transaction.Commit() +10
       Telerik.Cms.Web.UI.ToolBar.Button_Command(Object sender, CommandEventArgs e) +310
       System.Web.UI.WebControls.LinkButton.OnCommand(CommandEventArgs e) +105
       System.Web.UI.WebControls.LinkButton.RaisePostBackEvent(String eventArgument) +163
       System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +7
       System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11
       System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +174
       System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5102

    This forces you to delete the page.  No other simple exit from this problem.  Perhaps there is an exception that can be trapped here to prevent end user error.


    Jim Drain

  2. Rebecca
    Rebecca avatar
    536 posts
    24 Sep 2012
    15 Jan 2007
    Link to this post
    Hi Jim,

    Thank you very much for drawing our attention to this issue. It will be fixed in the Release Candidate.

    Sincerely yours,
    the telerik team
2 posts, 0 answered