FIX: You receive an error message when you use Microsoft OLE DB Provider for Visual FoxPro in SQL Server (908915)
The information in this article applies to:
- Microsoft Visual FoxPro 9.0 Professional Edition
- Microsoft Visual FoxPro 8.0 SP1
- Microsoft Visual FoxPro 8.0
- Microsoft Visual FoxPro for Windows 7.0 SP1
- Microsoft Visual FoxPro for Windows 7.0
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2000 Enterprise Edition
- Microsoft SQL Server 2000 Standard Edition
SYMPTOMSConsider the following scenario: - In Microsoft SQL Server, you use Microsoft OLE DB Provider for Visual FoxPro as a linked server by using the OPENQUERY function or the OPENROWSET function.
- In SQL Server, you configure Microsoft OLE DB Provider for Visual FoxPro to run in-process.
- You run repeated queries that return many rows and columns.
In this scenario, you receive an error message that is similar to the following: Server: Msg 7346, Level 16, State 2, Line 7
Could not get the data of the row from the OLE DB provider 'vfpoledb'. Could not convert the data value due to reasons other than sign mismatch or overflow.
OLE DB error trace [OLE/DB Provider 'vfpoledb' IRowset::GetData returned 0x40eda: Data status returned from the provider: [COLUMN_NAME=f100 STATUS=DBSTATUS_S_OK], [COLUMN_NAME=f99 STATUS=DBSTATUS_S_OK], [COLUMN_NAME=f98 STATUS=DBSTATUS_S_OK], [COLUMN_NAME=f97 STATUS=DBSTATUS_S_OK], [COLUMN_NAME=f96 STATUS=DBSTATUS_S_OK], [COLUMN_NAME=f95 STATUS=DBSTATUS_S_OK], [COLUMN_NAME=f94 STATUS=DBSTATUS... When the memory in the SQL Server MemToLeave region is exhausted, you may receive error messages that are similar to the following: Server: Msg 701, Level 17, State 1, Line 8
There is insufficient system memory to run this query. CAUSEThis problem occurs because of a memory leak in Microsoft OLE DB Provider for Visual FoxPro. Memory that is allocated by the provider is not released. The memory leak may eventually cause the memory in the SQL Server MemToLeave region to be exhausted.RESOLUTIONHotfix informationA 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 Microsoft Visual FoxPro 9.0 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. 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 tool in Control Panel. Date Time Version Size File name
-------------------------------------------------------
14-Sep-2005 21:45 9.0.0.3314 1,773,568 Vfpoledb.dll
14-Sep-2005 23:44 844,800 Vfpoledb.msm WORKAROUNDInstall the hotfix version of the Microsoft OLE DB Provider for Visual FoxPro in this article, and then configure the provider to run inside the SQL Server process. To do this, use the Allow InProcess setting. By default, the OLE DB Provider for Visual FoxPro runs out-of-process. Alternatively, you can work around this problem in previous versions of the Microsoft OLE DB Provider for Visual FoxPro. To do this, configure the Microsoft OLE DB Provider for Visual FoxPro to run outside the SQL Server process. Do not use the Allow InProcess setting. Although this workaround prevents the memory leak, data throughput is usually much lower. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Minor | Last Reviewed: | 7/26/2006 |
---|
Keywords: | kbQFE kbpubtypekc KB908915 kbAudDeveloper kbAudITPRO |
---|
|