10080 sql server 2005 configuration caused error?

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Jeff Kish

    10080 sql server 2005 configuration caused error?

    Hi.

    I have an ancient preCambrian app that uses the db library to interface with
    sql server databases.

    It is written in c++.

    When testing it I noticed on one machine with sql server 2005 installed it
    runs fine, but on another it has some problems, notably.. it gets as a result
    of a select statement with an order by clause the error:

    only fully keyset ddriven cursors can have 'order by', 'group by', or 'having'
    phrases.
    Error code 10080

    Can someone suggest a 'configuration' parameter that might be causing the
    otherwise identical systems to have this problem on one machine and not the
    other?

    Thanks
    Jeff


    thanks
    Jeff
    Jeff Kish
  • Jeff Kish

    #2
    Re: 10080 sql server 2005 configuration caused error?

    On Tue, 30 Jan 2007 13:15:12 -0500, Jeff Kish <jeff.kish@mro. comwrote:
    >Hi.
    >
    >I have an ancient preCambrian app that uses the db library to interface with
    >sql server databases.
    >
    >It is written in c++.
    >
    >When testing it I noticed on one machine with sql server 2005 installed it
    >runs fine, but on another it has some problems, notably.. it gets as a result
    >of a select statement with an order by clause the error:
    >
    >only fully keyset ddriven cursors can have 'order by', 'group by', or 'having'
    >phrases.
    >Error code 10080
    >
    >Can someone suggest a 'configuration' parameter that might be causing the
    >otherwise identical systems to have this problem on one machine and not the
    >other?
    >
    >Thanks
    >Jeff
    >
    >
    >thanks
    >Jeff
    >Jeff Kish
    I found the problem.
    It turned out that there is, in the windows system32 directory an ntdblib.dll
    file. The misbehaving machine had a very old version, probably from sql server
    7 or something else.

    I actually was able to just replace it with an updated version and it seems
    fine now.

    thanks
    Jeff
    Jeff Kish

    Comment

    Working...