Results 1 to 4 of 4
  1. #1
    Join Date
    Jan 2003
    Location
    Oxted, England
    Posts
    2

    Red face Unanswered: SQL Server and ASP

    I wonder if someone can help me.

    I designed a web-site using asp pages that access an SQL DB. Thing work fine, but I moved the web-site to another server and now I get the following error: -

    "Requested operation requires an OLE DB Session object, which is not supported by the current provider."

    I file that has the problem is here: -

    function dbNewCommand( oConn, procedureName )
    dim objCommand
    set objCommand = server.CreateObject( "ADODB.Command" )
    set objCommand.ActiveConnection = oConn
    objCommand.CommandText = procedureName

    set dbNewCommand = objCommand
    end function

    I must stress that this file works, unaltered, on the other web server.

    Does anyone have any clues?

    Thanks

  2. #2
    Join Date
    Jan 2003
    Location
    Washington, DC
    Posts
    24

    Question Re: SQL Server and ASP

    Where is oConn defined? I fixing to do the same exact thing and do
    recall needing to change the connection. Is it looking at the new
    server hostname in the connection statement? Does anything work
    or this is the first thing you noticed didn't work?

    BobbyJ

    Originally posted by warrenb
    I wonder if someone can help me.

    I designed a web-site using asp pages that access an SQL DB. Thing work fine, but I moved the web-site to another server and now I get the following error: -

    "Requested operation requires an OLE DB Session object, which is not supported by the current provider."

    I file that has the problem is here: -

    function dbNewCommand( oConn, procedureName )
    dim objCommand
    set objCommand = server.CreateObject( "ADODB.Command" )
    set objCommand.ActiveConnection = oConn
    objCommand.CommandText = procedureName

    set dbNewCommand = objCommand
    end function

    I must stress that this file works, unaltered, on the other web server.

    Does anyone have any clues?

    Thanks

  3. #3
    Join Date
    Jan 2003
    Location
    Oxted, England
    Posts
    2

    Smile

    Thanks for the reply, but I managed to muddle through.

    The oConn object is created in another function and should return a valid connection object. I made some changes to the connection string and things started to work as they should.

    In the connection string I changed "Provider=sqloledb" to "Driver={SQL Server}". I thought that this should not make a vast amount of difference, but it did.

    Warren

  4. #4
    Join Date
    Jan 2003
    Location
    Washington, DC
    Posts
    24

    Thumbs up

    Interesting. Thanks for the reply........ I'll add that to my list of things
    to check as I will do the same move in a matter of months.

    BobbyJ

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •