Microsoft KB Archive/256094

From BetaArchive Wiki
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Knowledge Base


Explorer.exe May Generate an "Access Violation" Error Message

PSS ID Number: 256094

Article Last Modified on 10/16/2002



The information in this article applies to:

  • Microsoft Windows NT Server 4.0



This article was previously published under Q256094

SYMPTOMS

An access violation may be generated in the Explorer.exe process.

CAUSE

The access violation is actually generated by Ole32.dll when a 0 (zero) is passed to a function that does not expect a 0 value.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows NT 4.0 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone 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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

   Date      Time                 Size    File name     Platform
   -------------------------------------------------------------
   02/23/00  06:33p               701,200 Ole32.dll     x86
   02/23/00  06:33p             1,239,312 Ole32.dll     Alpha
                



STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbbug kbQFE KB256094
Technology: kbWinNT400search kbWinNTS400 kbWinNTS400search kbWinNTsearch kbWinNTSsearch