Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

too many arguments - but they match Expand / Collapse
Author
Message
Posted Sunday, May 25, 2014 11:56 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 5:40 PM
Points: 53, Visits: 137
Matt Miller (#4) (5/25/2014)
Have you tried look at the profiler session of the parameters being passed in? Also - have you made sure that there is in fact only ONE stored proc with that specific name (e.g. myuser.StoredProc and dbo.StoredProc)? If the ASP is using a specific user account it might not be using the default schema.

On profiler: start a session recording, then fire your ASP call at it - you should be able to see what it being passed in.



I don't think I can use profiler. My site and database are on a shared hosting service and concerning SQL Server I am sometimes severely hamstrung. There have been many scripts for querying performance and certain DBA type jobs that I have tried to run only to get the "You do not have permission for that function" message.

Luckily, this issue has been resolved. But thank you!

Dana
Post #1574450
Posted Monday, May 26, 2014 8:26 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 1:47 PM
Points: 35,215, Visits: 31,667
danaanderson (5/25/2014)
Jeff Moden (5/25/2014)
danaanderson (5/25/2014)
I don't think that it matters about the position in the parameter of the dbtype spec, but I'll check it out. It is ASP.NET. Classic ASP is quite a different animal. In any case, from what I know this error is indicating that more parameters were sent than the procedure has receptors for...but it is ambiguous. I really wish T-SQL had a function like PARAMETERS() in VFP. I could know for sure.

Anyone else have any thoughts? It's surprising that there was only one person replying in a time span of about 23 hours.

Dana


Heh... it IS an SQL Server forum with a large number of people that live in the United states and you've asked an ASP question on a holiday weekend.


Well, it was SQL Server that was throwing the error. I thought it was the best place to start looking...and asking. True, though, it is a holiday weekend and most are probably out firing up the barbie.

Dana


Ah... understood. I noticed that you marked the post of JLS as the answer so I went and looked at the post he provided a link for. It would seem that some form of "read only field" was the problem and you needed to change the parmeter listing of at least 1 of the fields from "bind" to "eval". If that's true, which of your fields was it and was it an "IDENTITY" or "COMPUTED" column or ???

I'm asking because the code is automatically generated based on the stored procedure parameters and seems like it could be a common problem. Since SQL Server produced the error, I thought I'd ask for more details on what you did for a fix so that folks like me that know little of ASP can lend a helping hand in the future.

Thanks.


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1574536
Posted Monday, May 26, 2014 8:57 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 2:32 PM
Points: 1,912, Visits: 19,379
danaanderson (5/25/2014)
J Livingston SQL (5/25/2014)
danaanderson (5/25/2014)


Anyone else have any thoughts? It's surprising that there was only one person replying in a time span of about 23 hours.



not sure what you expect from a volunteer forum..........???

anyways...I know nothing about ASP but a quick google came up with this and others like it on SO.

http://stackoverflow.com/questions/14712451/procedure-or-function-xyz-has-too-many-arguments-specified

it may help...may not.....


Well, what I expected was some responses...I see a lot of helpfulness here. That's why it was my first choice to post the question here.

Thank you, I did Google this issue...and saw some things at stackoverflow...but they weren't that one. many times when I go to that site I see things that aren't helpful, that are about different circumstances entirely, or even often have no replies at all. Once in a while I see something that is actually helpful to me. This one was that...it was exactly the answer! Thank you again!

Dana


Dana...as you say...the people on this forum are very helpful and friendly and I appreciate why you posted as you did.

that said... I am glad you have found a solution....though it was pure luck that my google-fu came up with an answer that matched your requirements........

hope we can help again in the future if required....also, suggest you respond to Jeff's question about how you fixed it ....we can then all learn.



______________________________________________________________
you can lead a user to data....but you cannot make them think
and remember....every day is a school day
Post #1574545
Posted Monday, May 26, 2014 1:29 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 5:40 PM
Points: 53, Visits: 137
Jeff Moden (5/26/2014)
danaanderson (5/25/2014)
Jeff Moden (5/25/2014)
danaanderson (5/25/2014)
I don't think that it matters about the position in the parameter of the dbtype spec, but I'll check it out. It is ASP.NET. Classic ASP is quite a different animal. In any case, from what I know this error is indicating that more parameters were sent than the procedure has receptors for...but it is ambiguous. I really wish T-SQL had a function like PARAMETERS() in VFP. I could know for sure.

Anyone else have any thoughts? It's surprising that there was only one person replying in a time span of about 23 hours.

Dana


Heh... it IS an SQL Server forum with a large number of people that live in the United states and you've asked an ASP question on a holiday weekend.


Well, it was SQL Server that was throwing the error. I thought it was the best place to start looking...and asking. True, though, it is a holiday weekend and most are probably out firing up the barbie.

Dana


Ah... understood. I noticed that you marked the post of JLS as the answer so I went and looked at the post he provided a link for. It would seem that some form of "read only field" was the problem and you needed to change the parmeter listing of at least 1 of the fields from "bind" to "eval". If that's true, which of your fields was it and was it an "IDENTITY" or "COMPUTED" column or ???

I'm asking because the code is automatically generated based on the stored procedure parameters and seems like it could be a common problem. Since SQL Server produced the error, I thought I'd ask for more details on what you did for a fix so that folks like me that know little of ASP can lend a helping hand in the future.

Thanks.


There were several columns that I didn't want the user to edit, a couple of date columns, and couple of Boolean (bit) columns. Things that indicate whether the product is approved, or is active. No IDENTITY or COMPUTED columns were involved. I changed the template values to eval() and that did the trick. I actually changed the table structure since I made that web page, but the new columns were not the ones causing the issue. Like the poster of that solution, I find it odd that you have a parameter list, but ASP.NET still decides on what are truly parameters by looking at the bind() or eval() methods used in the template. Someone dropped the ball there, eh?

The site will be selling digital content for 3D art software such as DAZ|Studio or Poser. I'm a one-man operation, so all this stuff falls on me. I've gone from developing with VFP to having to know VB.NET, sometimes a little C#.NET, SQL Server (which was a little more natural to migrate to for me), a little AJAX, etc. It's amazing how many things we need to know in the field of web development! And they keep changing...I can't keep up, and sometimes I don't want to. I don't hop on every bandwagon just because they say it's the latest and greatest.

Thanks again for all the help and just being there for those who need help!

Dana
Post #1574591
Posted Wednesday, May 28, 2014 6:28 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 1:47 PM
Points: 35,215, Visits: 31,667
Thanks, Dana. I appreciate both the info and the thought.

And, yeah... it's amazing what you need to know to get a front-end up and running correctly.


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1575404
Posted Wednesday, May 28, 2014 6:35 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 5:40 PM
Points: 53, Visits: 137
You're welcome!

Dana
Post #1575406
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse