Microsoft KB Archive/937033

= FIX: Error message when you run a linked server query in SQL Server 2005: &quot;The oledbprovider unisys.dmsII.1 for linkserver '' reported an error the provider ran out of memory&quot; =

Article ID: 937033

Article Last Modified on 11/20/2007

-

APPLIES TO


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

-



Bug #: 50001248 (SQL Hotfix)



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 the hotfix package
 * The prerequisites for installing the hotfix package
 * Information about whether you must restart the computer after you install the hotfix package
 * Information about whether the hotfix package is replaced by any other hotfix package
 * The files that are contained in the hotfix package



SYMPTOMS
Consider the following scenario. You create a linked server in Microsoft SQL Server 2005. Then, you use Unisys OLE DB Data Provider for ClearPath MCP as an index provider to access data from a Unisys Enterprise Database Server (DMSII) database. You run several linked server queries successfully. In this scenario, you may receive the following error message when you run a linked server query against the provider:

The oledbprovider unisys.dmsII.1 for linkserver &quot; &quot; reported an error. the provider ran out of memory

Additionally, error messages that resemble the following are logged in the SQL Server 2005 error log file:

2007-04-05 13:14:27.410 spid59 Failed Virtual Allocate Bytes: FAIL_VIRTUAL_RESERVE 589824

2007-04-05 13:14:27.440 spid59 Error: 701, Severity: 17, State: 123.

2007-04-05 13:14:27.440 spid59 There is insufficient system memory to run this query.

Note This problem also occurs when you use other index providers as the linked server.



CAUSE
This problem occurs because a memory leak occurs in SQL Server 2005. The memory leak occurs because the memory that is allocated when SQL Server 2005 calls the IRowsetIndex::GetIndexInfo function is not freed.



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 Microsoft SQL Server 2005 Service Pack 2 (SP2) installed on the computer.

Restart information
You must restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix is not replaced by any other hotfixes.

File information
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 IA-64 versions


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



MORE INFORMATION
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

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 Description of the standard terminology that is used to describe Microsoft software updates



The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver KB937033

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.