sql exception unhandled user code

Question

0.00/5 (No votes)

See more:

while executing the stored procedure it is showing the following error message even though the passing arguments are matching with the arguments in stored procedure.

"Procedure or function usp_MemberRegistration_UPDATE_BY_MemberRegID_MEMBERPROFILE has too many arguments specified".

Posted 6-Sep-11 0:36am

Bernadshaw

Updated 6-Sep-11 0:40am

Toniyo Jackson

v2

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Toniyo Jackson · Answer 1 · 2011-09-06T00:41:00

Solution 1

This error will occur only when the passing arguments are not matching with the arguments in stored procedure. So, check one more time or share your code with us.

Posted 6-Sep-11 0:41am

Toniyo Jackson

Updated 6-Sep-11 0:53am

v2

Comments

Wendelius 6-Sep-11 6:52am

That's it, my 5

OriginalGriff · Answer 2 · 2011-09-06T00:41:00

Solution 2

Without your code it is difficult to tell exactly, but: do you execute the SP in a loop? If so, do you add parameters withing the loop? That can cause the problem: move the parameter add outside the loop and just change the values, or create a new SqlCommand object each time round the loop.

Posted 6-Sep-11 0:41am

OriginalGriff

Comments

Wendelius 6-Sep-11 6:53am

Good answer, just a case like that was yesterday. my 5

OriginalGriff 6-Sep-11 7:23am

I remembered that one - that gave me the clue! The error message was the same IIRC

prot0col · Answer 3 · 2011-09-06T00:46:00

Solution 3

Its tough to say anything without looking at your code.
Still you can check the number of parameters in the stored proc and the method from where you are sending them should be same and also check the order of the parameters.

Posted 6-Sep-11 0:46am

prot0col