+1-888-365-2779
Try Now
More in this section

Forums / Bugs & Issues / procedure or function sf_CmsPageContent_upd has too many arguments specified.

procedure or function sf_CmsPageContent_upd has too many arguments specified.

4 posts, 0 answered
  1. gohigher
    gohigher avatar
    25 posts
    Registered:
    24 Nov 2008
    15 Jul 2010
    Link to this post
    I recently upgraded a project (so I thought) to 3.7 SP 3. Last week I started to receive the following error message when accessing certain pages:

    procedure or function sf_CmsPageContent_upd has too many arguments specified.

    After reviewing an earlier thread I checked the database and the incorrect schema number was listed, hinting that the database had not been upgraded. I followed the recommendation and since then everything has been working fine.

    Today I have attempted to edit another page of the website and am receiving the error again. In it's entirety it states:

    Procedure or function sf_CmsPageContent_upd has too many arguments specified.

    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: System.Data.SqlClient.SqlException: Procedure or function sf_CmsPageContent_upd has too many arguments specified.

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace:

    [SqlException (0x80131904): Procedure or function sf_CmsPageContent_upd has too many arguments specified.]
       Nolics.ORMapper.DataProviders.SQLBlockBuilder.EndStatement(SQLCommandEventArgs args, DataRow row) +503
       Nolics.ORMapper.DataProviders.SQLBlockBuilder.ExecCommandProcedure(StmtContext context, DataRow data) +714
       Nolics.ORMapper.DataProviders.SQLBlockBuilder.ExecuteCommand(StmtContext context, DataRow data) +76
       Nolics.ORMapper.DataProviders.SQLDataProvider.Update(DataSet updateData) +1094
       Nolics.ORMapper.Base.Transaction.Commit(Boolean fCleanIfSuccess) +921
       Telerik.Cms.Data.StagedPage.CheckOut(Boolean increaseVersion) +385
       Telerik.Cms.Data.StagedPage.CheckOut() +26
       Telerik.Cms.Web.EditPage.OnPreInit(EventArgs e) +1117
       System.Web.UI.Page.PerformPreInit() +31
       System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +282
    


    Version Information: Microsoft .NET Framework Version:2.0.50727.4927; ASP.NET Version:2.0.50727.4927


    I checked the schema value in the DB and it is set to 2057. Please advise. Thank you.
  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    09 Dec 2016
    15 Jul 2010
    Link to this post
    Hello gohigher,

    You have not updated your project properly. The dataAccess section of your web.config has not be merged. Currently your project is using the old DataAccess provider Nolics.ORMapper.DataProviders.SQLDataProvider instead of ExtendedSqlServer2005Provider

    Kind regards,
    Ivan Dimitrov
    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? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. gohigher
    gohigher avatar
    25 posts
    Registered:
    24 Nov 2008
    15 Jul 2010
    Link to this post
    The web.config file does reflect that. It shows:

     <dataAccess defaultConnection="DefaultConnection">
           <connections>
               <add name="DefaultConnection" driver="Telerik.DataAccess.Providers.ExtendedSqlServer2005Provider, Telerik.DataAccess" connectionStringName="Sitefinity" />
               <add name="GenericContentConnection" driver="Telerik.Cms.Engine.Data.Providers.GCSql2005Provider, Telerik.Cms.Engine.Data" connectionStringName="Sitefinity" />
           </connections>
    </dataAccess>
  4. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    09 Dec 2016
    16 Jul 2010
    Link to this post
    Hello gohigher,

    Ok, then check whether you have not connected an earlier version of Sitefinity  to the same database which causes upgrade/downgrade each time you access the project . You can also go to your database and open the table sf_CmsVariables, there you should see a row with name SchemaVersion and the value should be the same as the build number of your website. ( How to check your version) . If you are using Sitefinity 3.7 SP3 (3.7.2096 build) the value will be 2096. If you reset the value to say 1 and restart the website, when the website is initialized it will upgrade the database to the correct number.

    Kind regards,
    Ivan Dimitrov
    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? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
Register for webinar
4 posts, 0 answered