May 28, 2007 at 6:57 am
The procedure is called from ASP page. Before I execute the procedure, I gather the values of the parameters, their values and their vartypes.
In this case, @parm1 is an integer and returns that and a valid value. No matter what I do to this parameter, I still get this error. I've been troubleshooting this for two days and I've never seen anything like this. What is interesting, is I have other pieces of code on the webpage using the same value prior to calling this function/procedure that work with this value. I have hooked the IIS 500 to a custom error page and have verfied the value is there. I've run this procedure
manually from QA and it works.... This is quite perplexing.
May 28, 2007 at 9:10 am
Can you put the entire error message and the code you're using in the post? Looks like the subject got cut off.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
May 28, 2007 at 1:34 pm
Actually, I resolved the problem. What was throwing me off was the proc's first parameter has a default.
The problem was the code calling the procedure. We code a lot of our procs in function calls and pass in the parameters.
For some reason, this line was missing:
.CommandType = adCmdStoredProc
I don't even understand what SQL was attempting to do here. Solved though.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply