More in this section

Forums / Developing with Sitefinity / Net SqlClient Data Provider - Procedure or function sf_CmsPageProps_upd has too many arguments specified.

Net SqlClient Data Provider - Procedure or function sf_CmsPageProps_upd has too many arguments specified.

5 posts, 0 answered
  1. Salman
    Salman avatar
    18 posts
    Registered:
    07 Nov 2007
    09 Feb 2009
    Link to this post
    Hi,

    We upgraded from Sitefinity 3.1 to 3.5 recently. I am experiencing this error:

    .Net SqlClient Data Provider - Procedure or function sf_CmsPageProps_upd has too many arguments specified.

    Whenever i do the following things:

    • Duplicate an existing Sitefinity page
    • Edit Page Name, Menu Label and Title
    • Click Save Changes (Takes me to Error Page)
    • I again logon to Sitefinity and see that Page is created
    • I click Edit button to change the content of the page
    • After making changes whenever i click Publish button, it always takes me to above error page.

    Please let me know that what's wrong with it?

    Is this a known bug?

    Is there any workaround to avoid this error?

    Many Thanks & Kind Regards,

    Salman Sarfraz

  2. Salman
    Salman avatar
    18 posts
    Registered:
    07 Nov 2007
    09 Feb 2009
    Link to this post
    Just to add more, i am looking for the causes/scenarios that may trigger this error so that i can avoid them.

    Looking forward to your prompt reply.
  3. Georgi
    Georgi avatar
    3583 posts
    Registered:
    28 Oct 2016
    09 Feb 2009
    Link to this post
    Hi Salman,

    Do you have several projects attached to a single database? . In this case, you should upgrade both projects because:

    • If you run the project with Sitefinity 3.5, it checks if the database schema is 3.5. If it is not, the database is upgraded.
    • If you then run the 3.1 project, it again checks for the version number of the database. If it is 3.5, the database schema is being downgraded.
    Now, if you have two users logged from the different instances at the same time, you can imagine what is happening with the database. Because the different versions have different stored procedures (or parameters), sometimes the 3.1 user might see the error you mentioned.

    We hope this helps.

    Regards,
    Georgi
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
  4. Salman
    Salman avatar
    18 posts
    Registered:
    07 Nov 2007
    18 Feb 2009
    Link to this post
    Hi Georgi,

    Sorry for this delayed answer from my side. I wanted to share that the information provided by you was useful. By the way, were not facing this error now.

    Thanks for your help.

    Have a good time.
  5. Georgi
    Georgi avatar
    3583 posts
    Registered:
    28 Oct 2016
    19 Feb 2009
    Link to this post
    Hi Salman,

    I am glad everything is fine.
    Please feel free to reopen the thread if you face this problem again.

    Kind regards,
    Georgi
    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.
Register for webinar
5 posts, 0 answered