FIX: When you query a view that was created by using the VIEW_METADATA option, an access violation may occur in SQL Server 2000

This article has been archived. It is offered "as is" and will no longer be updated.
Bug #: 474800 (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 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
In Microsoft SQL Server 2000, when you query a view that was created by using the VIEW_METADATA option, an access violation may occur.

In the Itanium architecture versions of SQL Server 2000, you may notice the following symptoms:
  • An access violation in the sqlservr!memcpy function near offset 0x180
  • The assertion "cbSize <= m_cbMaxBlock" in Memblk.cpp at line 166
In the 32-bit versions of SQL Server 2000, you may notice the following symptom:
  • An access violation in the sqlservr!CRowFmtTds::InitODS function near offset 0xfb
For a list of all publicly released SQL Server 2000 post-Service Pack 4 hotfixes, see the following article in the Microsoft Knowledge Base:
894905 Cumulative list of the hotfixes that are available for SQL Server 2000 Service Pack 4
This problem may occur when the query references the cached view memory structure after the memory structure has been flushed from the procedure cache.
The installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:
  • The system uses the Advanced Micro Devices (AMD) AMD64 processor architecture or the Intel Extended Memory 64 Technology (EM64T) processor architecture.

    Note This issue does not occur on systems that use the Intel Itanium processor architecture.
  • The system is running a 64-bit version of the Microsoft Windows Server operating system.
  • The system is running a 32-bit version of SQL Server 2000.
We have corrected this installation issue in later builds of SQL Server 2000, starting with version 8.00.2244. When a customer who is running SQL Server 2000 on an x64-based system requests this hotfix, we will provide a build that includes this hotfix and that can be installed correctly on an x64-based system. The build that we provide will be version 8.00.2244 or a later version.

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.


  • Microsoft SQL Server 2000 Service Pack 4 (SP4)

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

Restart information

You may have to restart the computer after you apply this hotfix. However, the hotfix installation stops and then restarts the MSSQLSERVER service.

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 item in Control Panel.
SQL Server 2000, 32-bit versions
File nameFile versionFile sizeDateTimePlatform
Sqlevn70.rll2000.80.2172.045,05610-Nov-200506:42Not Applicable
SQL Server 2000, Itanium architecture version
File nameFile versionFile sizeDateTimePlatform
Sqlevn70.rll2000.80.2172.035,32810-Nov-200513:34Not Applicable
To work around this problem, do not use views that were created by using the VIEW_METADATA option.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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

Article ID: 910707 - Last Review: 01/17/2015 12:32:48 - Revision: 4.0

Microsoft SQL Server 2000 Standard Edition, Microsoft SQL Server 2000 Developer Edition, Microsoft SQL Server 2000 Enterprise Edition, Microsoft SQL Server 2000 Personal Edition

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe KB910707
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)