FIX: Error message when you call the SQLTables function against an instance of SQL Server 2005: "Invalid cursor state (0)"
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. On This PageSUMMARYThis article describes the following about this hotfix release:
SYMPTOMSWhen 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 = "24000", *pfNativeError = 0, *pcbErrorMsg = 50, *ColumnNumber = -1, *RowNumber = -1
MessageText = "[Microsoft][SQL Native Client]Invalid cursor state" If you use the ODBC SQL Server data source driver, you receive the following error message: szSqlState = "24000", *pfNativeError = 0, *pcbErrorMsg = 55, *ColumnNumber = -1, *RowNumber = -1
MessageText = "[Microsoft][ODBC SQL Server Driver]Invalid cursor state" This problem occurs if the following conditions are true:
RESOLUTIONHotfix informationA supported hotfix is 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 software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, 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 (http://go.microsoft.com/?linkid=6294451) Note If additional issues occur or if 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 (http://support.microsoft.com/contactus/?ws=support) Note The "Hotfix download available" section and the online request forms display the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesYou 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 (http://support.microsoft.com/kb/913089/)
How to obtain the latest service pack for SQL Server 2005
Restart informationYou do not have to restart the computer after you apply this hotfix.Registry informationYou do not have to change the registry.Hotfix file informationThis 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
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONThe 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. REFERENCESFor more information about the SQLTables function, visit the following Microsoft Developer Network (MSDN) Web site: http://msdn2.microsoft.com/en-us/library/ms131341.aspx (http://msdn2.microsoft.com/en-us/library/ms131341.aspx)
For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 (http://support.microsoft.com/kb/822499/)
New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: 824684 (http://support.microsoft.com/kb/824684/)
Description of the standard terminology that is used to describe Microsoft software updates
APPLIES TO
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Help and Support
Back to the top
|
