Solved

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

Posted on 2004-04-01
7
908 Views
Last Modified: 2008-02-07
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
Comment
Question by:yuri_legalmatch
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 
LVL 15

Expert Comment

by:namasi_navaretnam
ID: 10738270
0
 

Author Comment

by:yuri_legalmatch
ID: 10738302
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
 
LVL 15

Accepted Solution

by:
namasi_navaretnam earned 100 total points
ID: 10738349
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
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:yuri_legalmatch
ID: 10738645
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
 
LVL 15

Expert Comment

by:namasi_navaretnam
ID: 10740477
There is only one parameter. Try adParamInput.
regards-
0
 

Author Comment

by:yuri_legalmatch
ID: 10742525
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
 
LVL 15

Expert Comment

by:namasi_navaretnam
ID: 10745356
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

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Introduction In my previous article (http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SSIS/A_9150-Loading-XML-Using-SSIS.html) I showed you how the XML Source component can be used to load XML files into a SQL Server database, us…
I have a large data set and a SSIS package. How can I load this file in multi threading?
This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.
Via a live example, show how to shrink a transaction log file down to a reasonable size.

729 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question