FIX: "Column index <index> out of range" error when you try to read a field from a JDBC ResultSet object

Article translations Article translations
Article ID: 838610
Expand all | Collapse all


You have a Java application that uses the Java Database Connectivity (JDBC) API to retrieve a ResultSet object by using the Microsoft SQL Server 2000 Driver for JDBC. When you try to read a field from the ResultSet object by using the methods in the JDBC API, you may receive an error message that is similar to the following:
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Column index <index> is out of range.
Note <index> is a placeholder for the index of the column that is being retrieved.

This problem occurs when all the following conditions are true:
  • The Select Transact-SQL statement that is used to retrieve the data from the SQL Server tables to the ResultSet object contains a JOIN between different tables in the SQL Server database.
  • The Select Transact-SQL statement uses asterisk (*) to retrieve all fields from the respective tables.


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 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. The English version of this hotfix has the file attributes (or later) 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.
   Date         Time   Version            Size    File name
   13-Jun-2003  09:22  2.2.0036          286,818  Msbase.jar 
   13-Jun-2003  09:22  2.2.0036           67,159  Mssqlserver.jar 
   13-Jun-2003  09:22  2.2.0036           58,903  Msutil.jar 


To work around this problem, explicitly specify the required field names in the SELECT Transact-SQL statement instead of using the asterisk (*) to represent all the fields from the respective tables.


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


For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
824106 PRB: "ResultSet can not re-read row data"' error when reading data from a JDBC ResultSet object
827221 FIX: Unsupported data conversion error occurs when you use a Null timestamp in JDBC
For additional 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


Article ID: 838610 - Last Review: June 20, 2014 - Revision: 3.0
kbbug kbjdbc kbjava kbfix kbqfe KB838610
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from