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


The information in this article applies to:

  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
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

SYMPTOMS

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

CAUSE

This problem may occur when the query references the cached view memory structure after the memory structure has been flushed from the procedure cache.

RESOLUTION

A 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 SQL Server 2000 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:

http://support.microsoft.com/contactus/?ws=support

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.

Prerequisites

  • 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
Dtsui.dll2000.80.2172.01,593,34410-Nov-200506:42x86
Impprov.dll2000.80.2172.0102,40010-Nov-200506:42x86
Mssdi98.dll8.11.50523.0239,10406-Jun-200522:46x86
Ntwdblib.dll2000.80.2172.0290,81610-Nov-200506:42x86
Odsole70.dll2000.80.2172.069,63210-Nov-200506:42x86
Pfclnt80.dll2000.80.2172.0430,08010-Nov-200506:42x86
Replprov.dll2000.80.2172.0237,56810-Nov-200506:42x86
Semexec.dll2000.80.2172.0856,06410-Nov-200506:42x86
Sqlagent.exe2000.80.2172.0323,58410-Nov-200505:17x86
Sqldiag.exe2000.80.2172.0118,78410-Nov-200505:49x86
Sqldmo.dll2000.80.2172.04,362,24010-Nov-200506:42x86
Sqlfth75.dll2000.80.2172.0102,40010-Nov-200505:18x86
Sqlservr.exe2000.80.2172.09,158,65610-Nov-200506:42x86
Sqlsort.dll2000.80.2172.0589,82410-Nov-200506:42x86
Stardds.dll2000.80.2172.0176,12810-Nov-200506:42x86
Svrnetcn.dll2000.80.2172.0110,59210-Nov-200506:42x86
Ums.dll2000.80.2172.035,84010-Nov-200506:42x86
Sqlevn70.rll2000.80.2172.045,05610-Nov-200506:42Not Applicable
SQL Server 2000, Itanium architecture version
File nameFile versionFile sizeDateTimePlatform
Impprov.dll2000.80.2172.0244,73610-Nov-200506:44IA-64
Mssdi98.dll8.11.50523.0758,78406-Jun-200522:46IA-64
Odsole70.dll2000.80.2172.0150,52810-Nov-200506:43IA-64
Pfclnt80.dll2000.80.2172.01,187,84010-Nov-200506:58IA-64
Replprov.dll2000.80.2172.0538,62410-Nov-200506:49IA-64
Sqlagent.exe2000.80.2172.01,061,37610-Nov-200507:01IA-64
Sqldiag.exe2000.80.2172.0334,33610-Nov-200507:00IA-64
Sqldmo.dll2000.80.2172.013,860,35210-Nov-200507:07IA-64
Sqlfth75.dll2000.80.2172.0246,78410-Nov-200506:44IA-64
Sqlservr.exe2000.80.2172.024,924,67210-Nov-200513:35IA-64
Sqlsort.dll2000.80.2172.0617,47210-Nov-200505:12IA-64
Svrnetcn.dll2000.80.2172.0427,52010-Nov-200506:56IA-64
Sqlevn70.rll2000.80.2172.035,32810-Nov-200513:34Not Applicable

WORKAROUND

To work around this problem, do not use views that were created by using the VIEW_METADATA option.

STATUS

Microsoft 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 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

Modification Type:MinorLast Reviewed:7/26/2006
Keywords:kbHotfixServer kbQFE kbpubtypekc KB910707 kbAudITPRO kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.