• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 985
  • Last Modified:

error '80004005' when calling stored procedure with parameters using ADODB.Command

Hello guys.
I'm trying to finish asp page that executes the sql server stored procedure. The database is SQL Server 2000.
Here is the piece that I'm trying to run:
*************************************************************************
    ' Call the stored procedure to populate usUser table
    Dim cn, cmd, param2, rs, sql, tmpXML
   
    Set cn = Server.CreateObject("ADODB.Connection")
    Set cmd = Server.CreateObject("ADODB.Command")
    Set param2 = Server.CreateObject("ADODB.Parameter")
    'Set rs = Server.CreateObject("ADODB.Recordset")
       
    cn.Open c_QBUS_MSSQL01Connection
    tmpXML = "<TEST1>"
   
    Set cmd.ActiveConnection = cn
    cmd.CommandText = "udp_insert_xml_usUser"
    cmd.CommandType = adCmdStoredProc
    Set param2 = cmd.CreateParameter("pXMLDoc",adLongVarchar,adParamInputOutput,10,tmpXML)
   
    cmd.Parameters.Append param2
    Response.Write("<p>Executing SQL stored procedure:" & cmd.CommandText)
       
    cmd.Execute

    'rs.Close
    cn.Close
    Set cn = Nothing
*************************************************************************

Stored procedure inserts contents of the variable into the table.

Wnenever I'm trying to run the page it returns the following error:
------------------------------------------------------------------------------------------------------------------
Executing SQL stored procedure:{ call udp_insert_xml_usUser(?) }

Provider error '80004005'

Unspecified error

/departments/it/UpShot/users.asp, line 157
--------------------------------------------------------------------------------------------------------------------
Where line 157 is the calling cmd.Execute method.

I noticed it only happens when I'm trying to call procedure with parameters. When I'm calling stored procedure without any parameters it executes fine.


What is wrong?

Any help will be highly appreciated.

Thanks,
Yuri.


0
yuri_legalmatch
Asked:
yuri_legalmatch
  • 4
  • 3
1 Solution
 
namasi_navaretnamCommented:
0
 
yuri_legalmatchAuthor Commented:
As I stated before - the problem occurs only if I'm calling stored procedure with parameters.

If I had this stored procedure without parameters it would run fine.

0
 
namasi_navaretnamCommented:
Could you post your stored proc? Parameters must be added in the order in which they appear within stored proc. It seems your proc has only one parameter is that right.

Use the actual parameter name as the first parametr. Try with input, output paramters instead of one inputoutput paramter. Should work as inputoutput paramter, but splitting them will help to isolate the issue.
 
Set myParameter = Command.CreateParameter (Name, [Type], [Direction], [Size], [Value])

I am sure you may have seen these examples: I list them anyway.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;300488

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q165/1/56.asp&NoWebContent=1
0
Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

 
yuri_legalmatchAuthor Commented:
drop procedure udp_insert_xml_usUser
go

create procedure udp_insert_xml_usUser
                 (@pXMLDoc  text)
AS
  Declare
    @vReturnCode    int,
    @vDocID         int

select * from usUser

GO
0
 
namasi_navaretnamCommented:
There is only one parameter. Try adParamInput.
regards-
0
 
yuri_legalmatchAuthor Commented:
I did change it it solved the problem....

Now I have different one. I'm passing ~26k characters of XML. Procedure blows somewhere. How should I trap the error?
0
 
namasi_navaretnamCommented:
Perform error checking ffter each statement

IF @@ERROR <> 0
Begin
  Raiserror(16001, 'Error inserting into mytable')
  Retrun 1000
End

Check the retrun number to see where the code blows. Or execute the procedure from query analyser with same parameter to track where the error is.

For debugging purposes PRINT statement can be used. But remove pront statements once finding where the issue is.

regards-

0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now