FIX: The "Data area passed to a system call is too small" error message is logged when you call the CreateEx method at the same time in a multiple-thread application that uses the Virtual Device Interface feature of SQL Server 2000
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 362953 (SQL Server 8.0)
Microsoft distributes Microsoft SQL Server 2000 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 2000 fix release.
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
- Whether you must restart the computer after you install the hotfix package
- Whether the hotfix package is replaced by any other hotfix package
- Whether you must make any registry changes
- The files that are contained in the hotfix package
Consider the following scenario:
- You call the CreateEx method at the same time on more than one thread in a multiple-thread application.
- The multiple-thread application uses the Virtual Device Interface feature of Microsoft SQL Server 2000.
Data area passed to a system call is too small.
Service pack informationTo resolve this problem, obtain the latest service pack for SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack
Hotfix 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.
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.
- Microsoft SQL Server 2000 Service Pack 3 (SP3)
For more information about how to obtain SQL Server 2000 SP3, click the following article number to view the article in the Microsoft Knowledge Base:290211 How to obtain the latest SQL Server 2000 service pack
Restart informationYou do not have to restart the computer after you apply this hotfix.
Registry informationYou do not have to change the registry.
Hotfix file informationThis hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain 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
Date Time Version Size File name ----------------------------------------------------- 01-Nov-2002 17:56 2000.80.698.0 45,644 Sqlvdi.dllNote 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. This problem was first corrected in SQL Server 2000 Service Pack 4.
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 packagesFor more information about the terminology that Microsoft uses when Microsoft corrects software after it is released, 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: 810065 - Last Review: 12/08/2015 01:39:00 - Revision: 2.0
Microsoft SQL Server 2000 Developer Edition, Microsoft SQL Server 2000 Enterprise Edition, Microsoft SQL Server 2000 Personal Edition, Microsoft SQL Server 2000 Standard Edition, Microsoft SQL Server 2000 Workgroup Edition
- kbnosurvey kbarchive kbautohotfix kbtshoot kbfix kbbug kbHotfixServer kbqfe KB810065