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)

    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.


Who is Participating?
namasi_navaretnamConnect With a Mentor Commented:
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.;EN-US;300488
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.

A proven path to a career in data science

At Springboard, we know how to get you a job in data science. With Springboard’s Data Science Career Track, you’ll master data science  with a curriculum built by industry experts. You’ll work on real projects, and get 1-on-1 mentorship from a data scientist.

yuri_legalmatchAuthor Commented:
drop procedure udp_insert_xml_usUser

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

select * from usUser

There is only one parameter. Try adParamInput.
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?
Perform error checking ffter each statement

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

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.


Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.