Exception message: Procedure or function sp_procedurename has too many arguments specified.

If this error results from attempting to call a stored procedure from within an asp.net aspx page,

Fix: modify aspx page to rename procedure arguments to match the stored procedure arguments


A potentially dangerous Request.Form value was detected from the client …

One work around is to set


in Page element in web.config. Only trouble with that is, it allegedly then leaves the page vulnerable to script-injection attacks.
And apparently Html.Encoding() the control’s contents on the grid alone will not prevent the error either, but using a combination of both steps, is a fairly acceptable workaround.

Alternatively, validateRequest=”false” can be used just in the page directive of a specific page rather than in the web.config file, and the second step is to then html encode the contents of controls on the web page or grid view. e.g. Textbox.Text = HttpUtility.HtmlEncode(databasevalue)