error:The parameterized query '(@param1 int,@Paramout int OUTPUT)' expects the parameter '@Paramout', which was not supplied.

• Guras

  SSCertifiable

  Points: 6518

  More actions

  January 23, 2014 at 9:14 am

  #303343

  I am using sp_executesql and I get the following error

  Declare @retProcVal int

  SELECT @SqlString2 = N'use @dbName exec PROC_01 @param1,@paramout OUTPUT'

  set @ParamDef = N'@param1 int,@paramout int OUTPUT'

  SET @SqlString2 = Replace(@sqlString2,'@dbName',@dbName)

  EXECUTE sp_executesql @SqlString2 ,@ParamDef, @param1 = @intHosp,@paramout = @retProcVal OUTPUT

  --PROC_01 returns 0 upon sucess and 1 upon failure.

  Cannot tell where is the bug.

  Thanks

• Kurt W. Zimmerman

  SSCrazy Eights

  Points: 8676

  More actions

  January 23, 2014 at 9:43 am

  #1682854

  What is the error message you are receiving?

  Kurt

  Kurt W. Zimmerman
  SR DBA
  Lefrak Organization
  New York, NY

  http://www.linkedin.com/in/kurtwzimmerman

• Guras

  SSCertifiable

  Points: 6518

  More actions

  January 23, 2014 at 9:45 am

  #1682855

  error:The parameterized query '(@param1 int,@Paramout int OUTPUT)' expects the parameter '@Paramout', which was not supplied.

• doug.brown

  SSCertifiable

  Points: 5607

  More actions

  January 23, 2014 at 10:55 am

  #1682878

  Is it possibly a collation issue? I notice in your code the parameter is uncapitalized (@paramout), but in the error message it is capitalized:

  error:The parameterized query '(@param1 int,@Paramout int OUTPUT)' expects the parameter '@Paramout', which was not supplied.

  What happens if you capitalize it in your code, as below:

  Declare @retProcVal int

  SELECT @SqlString2 = N'use @dbName exec PROC_01 @param1,@Paramout OUTPUT'

  set @ParamDef = N'@param1 int,@Paramout int OUTPUT'

  SET @SqlString2 = Replace(@sqlString2,'@dbName',@dbName)

  EXECUTE sp_executesql @SqlString2 ,@ParamDef, @param1 = @intHosp,@Paramout = @retProcVal OUTPUT

• Guras

  SSCertifiable

  Points: 6518

  More actions

  January 23, 2014 at 12:47 pm

  #1682904

  I figured out what the issue was. There were two stored procedure calls ( I did not have that code in the post) .

  Both calls were using the same paramdef. Separated the paramdef and it worked. Thanks