FIX: You may receive a “Server: Msg 7358, Level 16, State 1, Line 1” error message after you run a linked server query in SQL Server 2000 Service Pack 4

This article describes the following about this hotfix release:

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

When you run a linked server query to Microsoft SQL Server 2000 Analysis Services, and the query uses the OLAP provider, you may receive the following error message: Note This problem occurs after you install Microsoft SQL Server 2000 Service Pack 4 (SP4).

This problem occurs when any one of the following conditions is true:

• The OLE DB provider returns one or more columns of Large Objects (LOB) data type for which the DBCOLUMNFLAGS_ISLONG value is set for the DBCOLUMNINFO.dwFlags structure member.
• The OLE DB provider returns one or more columns of Large Objects (LOB) data type for which the DBCOLUMNINFO.ulColumnSize structure member of a column is set to a value that is larger than 8000 characters.
• The OLE DB provider does not support the following interfaces:
  • ISequentialStream
  • ILockBytes
  • IStream

Hotfix information

A 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.

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 Customer Service and Support to obtain the hotfix.

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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays 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.

Prerequisites

Microsoft SQL Server 2000 SP4

For information about how to obtain SQL Server 2000 SP4, see the following article in the Microsoft Knowledge Base:

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 after you apply this hotfix.

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 tool in Control Panel.

SQL Server 2000, 32-bit versions

SQL Server 2000, 64-bit version

Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

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

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: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: