Microsoft KB Archive/925227

= FIX: Error message when you call the SQLTables function against an instance of SQL Server 2005: &quot;Invalid cursor state (0)&quot; =

Article ID: 925227

Article Last Modified on 11/20/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Workgroup Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems Community Technology Preview
 * Microsoft SQL Server 2005 Service Pack 1

-



Bug #: 50000244 (SQL Hotfix)

Bug #: 482039 (SQLBUDT)



Microsoft distributes Microsoft SQL Server 2005 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 2005 fix release.



SUMMARY
This article describes the following about this hotfix release:
 * The issues that are fixed by this 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 you call the SQLTables function against an instance of Microsoft SQL Server 2005, you may receive an error message. The error message that you receive is based on the ODBC data source driver that you use to connect to the instance of SQL Server 2005. If you use the SQL Native Client data source driver, you receive the following error message:

szSqlState = &quot;24000&quot;, *pfNativeError = 0, *pcbErrorMsg = 50, *ColumnNumber = -1, *RowNumber = -1 MessageText = &quot;[Microsoft][SQL Native Client]Invalid cursor state&quot;

If you use the ODBC SQL Server data source driver, you receive the following error message:

szSqlState = &quot;24000&quot;, *pfNativeError = 0, *pcbErrorMsg = 55, *ColumnNumber = -1, *RowNumber = -1 MessageText = &quot;[Microsoft][ODBC SQL Server Driver]Invalid cursor state&quot;

This problem occurs if the following conditions are true:  The value that you specify in one of the following parameters of the SQLTables function contains a wildcard character:  CatalogName SchemaName TableName

For example, one of these parameters contains an underscore (_) character or a percent (%) character. You specify ODBC 3.0 for the ODBC behavior of the ODBC data source driver.</li> You call the SQLTables function on a server-side cursor.</li></ul>

<div class="resolution_section">

Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
You must have SQL Server 2005 Service Pack 1 (SP1) installed to apply this hotfix.

For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005

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 of 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 item in Control Panel.SQL Server 2005 32-bit version

SQL Server 2005 x64-based version

SQL Server 2005 Itanium architecture version

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
The hotfix changes the sp_tableswc system stored procedure and the sp_ddopen;13 system stored procedure. The sp_tableswc system stored procedure has been changed to return either a result set or a cursor based on a parameter. The sp_ddopen;13 system stored procedure now calls the sp_tableswc system stored procedure that has a parameter that is set to return a cursor. Therefore, a nested INSERT… EXEC statement can be avoided.

This hotfix adds new parameters to the sp_tableswc system stored procedure. However, these new parameters have default values. Therefore, these new parameters will not cause a problem to the existing call to the sp_tableswc system stored procedure.

<div class="references_section">