Post reply

Extra parameters being added onto SP call with ADO

  • February 24, 2004 at 3:29 pm

    #178223

    We are running into problems on our development environment with extra parameters being added on to a stored procedure call.  Instead of the expected parms, the trace shows something like this:

    declare @P1 int

    set @P1=NULL

    <<expected stored procedure call>> , @P1 output, <<repeat of first three sp parms>>

    select @P1

    The developer has checked the code, and I have checked the SP - both seem to match what is in production (which works fine).  The databases are on the same server, and the apps are running on seperate web servers.

    I'm guessing this may be some sort of configuration issue with ADO, SQL, or something else - has anone run into something similar to this?  Thanks!

    Z

  • February 25, 2004 at 12:20 pm

    #495646

    Not sure if this will help, but I had a similar problem and restarting IIS cleared it up.

    My problem was that I changed the name of an input parameter in a stored procedure and when I changed the parameter name in my custom database class (ASP.NET/ADO.NET SQLCommand.Parameters object), the function was still sending the original parameter name - even after a recomplile of the project.

    If restarting IIS doesn't help can you post some of the code (ADO & SP),the complete trace line from Profiler, and the error message returned?

  • February 25, 2004 at 1:43 pm

    #495666

    Billy -

    Thanks for the feedback - that will be good to note, as it sounds like a dicey problem to debug.

    As it turns out, the problem is being caused by a combination of poorly coded Paramaters.Refresh code along with the fact that a userid.spname proc is being run instead of the desiered dbo.spname proc.  We're still researching why that is happening...    

    Dave

     

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply