Microsoft KB Archive/919144

From BetaArchive Wiki

Article ID: 919144

Article Last Modified on 11/20/2007



APPLIES TO

  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Workgroup Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Standard X64 Edition



Bug #: 743 (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.

SUMMARY

This article describes the following about this hotfix release:

  • The issues that are fixed by the hotfix package
  • The prerequisites for applying the hotfix package
  • Whether you must restart the computer after you apply the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes after you apply the hotfix package
  • The files that are contained in the hotfix package


SYMPTOMS

Consider the following scenario. In Microsoft SQL Server 2005, you enable the lazy schema validation option for any linked server. Additionally, you run a distributed partitioned view query. In this scenario, an access violation may occur. An error message that resembles the following may be logged in the SQL Server error log:

Exception Address = 016FAE18 Module(sqlservr+006FAE18)
Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
Access Violation occurred reading address 00000018


This problem may occur when some information about the remote session is not correctly cached and is not correctly cleared.

RESOLUTION

Hotfix information

A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, 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:

Note If additional issues occur or 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:

Prerequisites

  • SQL Server 2005 Service Pack 1

    For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

    913089 How to obtain the latest service pack for SQL Server 2005

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

Hotfix file information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.

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 2005 32-bit version
File name File version File size Date Time Platform
Microsoft.sqlserver.sqlenum.dll 9.0.2156.0 908,064 24-May-2006 01:04 x86
Microsoft.sqlserver.mgdsqldumper.dll 2005.90.2156.0 75,552 24-May-2006 01:04 x86
Msmdlocal.dll 9.0.2156.0 15,661,344 24-May-2006 01:05 x86
Sqlaccess.dll 2005.90.2156.0 347,936 24-May-2006 01:04 x86
Sqlservr.exe 2005.90.2156.0 28,937,560 24-May-2006 01:05 x86
SQL Server 2005 x64-based version
File name File version File size Date Time Platform
Microsoft.sqlserver.sqlenum.dll 9.0.2156.0 875,296 25-May-2006 02:08 x86
Microsoft.sqlserver.mgdsqldumper.dll 2005.90.2156.0 91,424 25-May-2006 02:09 x64
Msmdlocal.dll 9.0.2156.0 15,661,344 24-May-2006 01:05 x86
Sqlaccess.dll 2005.90.2156.0 355,104 25-May-2006 02:09 x86
Sqlservr.exe 2005.90.2156.0 39,345,952 25-May-2006 02:08 x64
SQL Server 2005 Itanium-architecture version
File name File version File size Date Time Platform
Microsoft.sqlserver.sqlenum.dll 9.0.2156.0 875,296 24-May-2006 17:50 x86
Microsoft.sqlserver.mgdsqldumper.dll 2005.90.2156.0 163,104 24-May-2006 17:49 IA-64
Msmdlocal.dll 9.0.2156.0 48,731,936 24-May-2006 17:49 IA-64
Sqlaccess.dll 2005.90.2156.0 349,472 24-May-2006 17:50 x86
Sqlservr.exe 2005.90.2156.0 72,186,144 24-May-2006 17:49 IA-64


WORKAROUND

To work around this problem, disable the lazy schema validation option for all linked servers that are involved in the distributed partitioned view query.

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, click the following article numbers to view the articles in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates


922296 FIX: You may receive an access violation error message when you run a query against a linked server in SQL Server 2005


Keywords: kbtshoot kbfix kbqfe kbpubtypekc kbexpertiseadvanced kbhotfixserver kbsql2005engine KB919144