« Previous Next »

Not Answered Thread: Multiple-step OLE DB operation generated errors

Last post 03-04-2007 1:01 PM by steve schofield. 2 replies.

 

RSS

Page 1 of 1 (3 items)

Sort Posts:

  • 03-03-2007, 11:21 AM

    • JROD_Z28
    • Not Ranked
    • Joined on 03-03-2007, 4:08 PM
    • Posts 2

    Multiple-step OLE DB operation generated errors

    All,

    Using Vista IIS7 with Oracle 10G.

    I'm getting a "Multiple-step OLE DB operation generated errors" when  issuing the execute command.  Here is the code I'm executing.  When I execute the same command from visual basic it works fine, I just get the error from ASP. 

     set oConn = Server.CreateObject("ADODB.Connection")
     oConn.Open "Provider=MSDAORA; DataSource=DB01; User ID=MAIN; Password=MAIN;" 

     sql= "SELECT * From securityinfo WHERE user='TEST' AND dte_effect <= {fn curdate() } and (dte_cncld IS NULL or dte_cncld >= {fn curdate() } )"

    Set oRs = oConn.Execute(Sql)

    Here is the entire error message. 

    Number: -2147217887

    Description: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.

    Source: Microsoft OLE DB Provider for Oracle

    SQLState:

    NativeError: 0

     

    Any ideas?

     

    Thanks,
    Jerry R.

     

  • 03-04-2007, 12:30 PM In reply to

    • JROD_Z28
    • Not Ranked
    • Joined on 03-03-2007, 4:08 PM
    • Posts 2

    Re: Multiple-step OLE DB operation generated errors

    After a little bit more testing it turned out that the error is being thrown when I execute the connection method.  If I ignore the error everything works fine,  I'm still confused why I would get a connection error after switching to Vista and Oracle 10g.

     Thanks,

    Jerry R.

  • 03-04-2007, 1:01 PM In reply to

    Re: Multiple-step OLE DB operation generated errors

    Not sure about the Oracle, personally I've not used it.  Coupel things to check.  It could be permissions related.  http://www.microsoft.com/technet/sysinternals/utilities/ProcessExplorer.mspx can help identify what is being blocked.  Secondly this seems to be common in Classic ASP and IIS7 http://forums.iis.net/thread/1587380.aspx  Hope that provides some ideas.

    Steve Schofield
    Windows Server MVP - IIS
    http://weblogs.asp.net/steveschofield

    http://www.IISLogs.com
    Log archival solution
    Install, Configure, Forget
Page 1 of 1 (3 items)