FIX: Error message when you run a linked server query in SQL Server 2005: "The oledbprovider unisys.dmsII.1 for linkserver '<ServerName>' reported an error the provider ran out of memory"
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. On This PageSUMMARY This article describes the following about this hotfix release:
SYMPTOMSConsider 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 "<ServerName>" 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
Note This problem also occurs when you use other index providers as the linked server.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. CAUSEThis 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. 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 Microsoft SQL Server 2005 Service Pack 2 (SP2) installed on the computer.Restart informationYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix is not replaced by any other hotfixes.File informationThe 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 86-bit versions
SQL Server 2005 IA-64 versions
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" 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 (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
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. APPLIES TO
| Article Translations
|
Back to the top
