Microsoft KB Archive/910710

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 14:17, 21 July 2020 by X010 (talk | contribs) (Text replacement - "&" to "&")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Article ID: 910710

Article Last Modified on 11/2/2007



APPLIES TO

  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000 Standard Edition



BUG #: 20000192 (SQL Server 8.0)

Microsoft distributes Microsoft SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.

SUMMARY

This article describes the following about this hotfix release:

  • The issues that are fixed by the hotfix package
  • The prerequisites for installing the hotfix package
  • Whether you must restart the computer after you install the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes
  • The files that are contained in the hotfix package


SYMPTOMS

When a Microsoft Visual Basic application opens a dynamic cursor on a GROUP BY query, you receive an error message that is similar to the following:

Run-time error '3251': Object or provider is not capable of performing requested operation

This problem occurs when the following conditions are true:

  • The server is running Microsoft SQL Server 2000 Service Pack 4 (SP4).
  • The recordset object is declared by using the WithEvents keyword.
  • The dynamic cursor is implemented on the server.

For a list of all publicly released SQL Server 2000 post-Service Pack 4 hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

894905 Cumulative list of the hotfixes that are available for SQL Server 2000 SP4


RESOLUTION

The installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:

  • The system uses the Advanced Micro Devices (AMD) AMD64 processor architecture or the Intel Extended Memory 64 Technology (EM64T) processor architecture.


Note This issue does not occur on systems that use the Intel Itanium processor architecture.

  • The system is running a 64-bit version of the Microsoft Windows Server operating system.
  • The system is running a 32-bit version of SQL Server 2000.

We have corrected this installation issue in later builds of SQL Server 2000, starting with version 8.00.2244. When a customer who is running SQL Server 2000 on an x64-based system requests this hotfix, we will provide a build that includes this hotfix and that can be installed correctly on an x64-based system. The build that we provide will be version 8.00.2244 or a later version.

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

  • SQL Server 2000 SP4

    For more information about how to obtain SQL Server 2000 SP4, click the following article number to view the article in the Microsoft Knowledge Base:

    290211 How to obtain the latest SQL Server 2000 service pack

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

SQL Server 2000, 32-bit hotfix
File name File version File size Date Time Platform
Dtsui.dll 2000.80.2172.0 1,593,344 10-Nov-2005 06:42 x86
Impprov.dll 2000.80.2172.0 102,400 10-Nov-2005 06:42 x86
Mssdi98.dll 8.11.50523.0 239,104 06-Jun-2005 22:46 x86
Ntwdblib.dll 2000.80.2172.0 290,816 10-Nov-2005 06:42 x86
Odsole70.dll 2000.80.2172.0 69,632 10-Nov-2005 06:42 x86
Osql.exe 2000.80.2039.0 57,344 04-May-2005 04:32 x86
Pfclnt80.dll 2000.80.2172.0 430,080 10-Nov-2005 06:42 x86
Replprov.dll 2000.80.2172.0 237,568 10-Nov-2005 06:42 x86
Semexec.dll 2000.80.2172.0 856,064 10-Nov-2005 06:42 x86
Sqlagent.exe 2000.80.2172.0 323,584 10-Nov-2005 05:17 x86
Sqldiag.exe 2000.80.2172.0 118,784 10-Nov-2005 05:49 x86
Sqldmo.dll 2000.80.2172.0 4,362,240 10-Nov-2005 06:42 x86
Sqlfth75.dll 2000.80.2172.0 102,400 10-Nov-2005 05:18 x86
Sqlservr.exe 2000.80.2172.0 9,158,656 10-Nov-2005 06:42 x86
Sqlsort.dll 2000.80.2172.0 589,824 10-Nov-2005 06:42 x86
Stardds.dll 2000.80.2172.0 176,128 10-Nov-2005 06:42 x86
Svrnetcn.dll 2000.80.2172.0 110,592 10-Nov-2005 06:42 x86
Ums.dll 2000.80.2172.0 35,840 10-Nov-2005 06:42 x86
SQL Server 2000, 64-bit hotfix for Itanium processors
File name File version File size Date Time Platform
Impprov.dll 2000.80.2172.0 244,736 11-Nov-2005 01:34 IA-64
Mssdi98.dll 8.11.50523.0 758,784 11-Nov-2005 01:34 IA-64
Msvcr71.dll 7.10.3052.4 348,160 11-Nov-2005 01:34 x86
Odsole70.dll 2000.80.2172.0 150,528 11-Nov-2005 01:34 IA-64
Pfclnt80.dll 2000.80.2172.0 1,187,840 11-Nov-2005 01:34 IA-64
Replprov.dll 2000.80.2172.0 538,624 11-Nov-2005 01:34 IA-64
Replprov2.dll 2000.80.2172.0 538,624 11-Nov-2005 01:34 IA-64
Sqlagent.exe 2000.80.2172.0 1,061,376 11-Nov-2005 01:34 IA-64
Sqldiag.exe 2000.80.2172.0 334,336 11-Nov-2005 01:34 IA-64
Sqldmo.dll 2000.80.2172.0 13,860,352 11-Nov-2005 01:34 IA-64
Sqlfth75.dll 2000.80.2172.0 246,784 11-Nov-2005 01:34 IA-64
Sqlservr.exe 2000.80.2172.0 24,924,672 11-Nov-2005 01:34 IA-64
Sqlsort.dll 2000.80.2172.0 617,472 11-Nov-2005 01:34 IA-64
Sqlsort_.dll 2000.80.2172.0 617,472 11-Nov-2005 01:34 IA-64
Sqlsort_1.dll 2000.80.2172.0 617,472 11-Nov-2005 01:34 IA-64
Svrnetcn.dll 2000.80.2172.0 427,520 11-Nov-2005 01:34 IA-64


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates


Steps to reproduce the problem

To reproduce the problem, use the following Visual Basic code example.

Dim cnx As New ADODB.Connection
    Dim srvName As String
    
    srvName = "myServer"
    cnx.ConnectionString = "Provider=SQLOLEDB;Data Source=" & srvName & ";Integrated Security=SSPI;Initial Catalog=Northwind"
    cnx.Open
    
    Dim cmd As New ADODB.Command
    Set cmd.ActiveConnection = cnx
    
    cmd.CommandText = "SELECT Customers.CustomerID, Orders.OrderID FROM Customers LEFT OUTER JOIN Orders ON Customers.CustomerID = Orders.CustomerID GROUP BY Customers.CustomerID, Orders.OrderID ORDER BY Orders.OrderID"
    cmd.CommandType = adCmdText
    'cmd.CommandText = "dbo.test"
    'cmd.CommandType = adCmdStoredProc
    
    Set rs = New ADODB.Recordset
    rs.CursorLocation = adUseServer
    
    ' should fail with 3251
    rs.Open Source:=cmd, CursorType:=adOpenDynamic, LockType:=adLockOptimistic, Options:=1
        
    rs.Close
    Set rs = Nothing
    Set cmd = Nothing
    
    cnx.Close
    Set cnx = Nothing

Note In this code example, change the value of the srvName parameter to the name of the server.

Keywords: kbbug kbfix kbtshoot kbhotfixserver kbqfe kbpubtypekc KB910710