Microsoft KB Archive/813588

= Access Violation May Occur in COM Modules When Managed Process Exits =

Article ID: 813588

Article Last Modified on 10/12/2005

-

APPLIES TO


 * Microsoft .NET Framework 1.0 Service Pack 2

-



SYMPTOMS
When a managed process exits, the .NET Framework 1.0 Service Pack 2 (SP2) runtime does not call the CoUninitialize procedure. This causes previous COM modules with interdependency to shut down in random order, and therefore, may cause an access violation.



Steps to Reproduce the Behavior
These steps assume that you have two previous COM components that are implemented in two modules: A and B. In this scenario, A depends on B.
 * 1) A managed client accesses a component in module A.
 * 2) Module B is also loaded because A depends on B.
 * 3) When the managed client exits, B may be unloaded from memory before A is unloaded. Therefore, when A is unloaded, an access violation occurs.



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 Microsoft .NET Framework 1.0 service pack that contains this hotfix.

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:

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. The English version of this fix has the file attributes (or later) 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.   Date      Time   Version      Size   File name -- 16-Jan-2003 22:27 1.0.3705.394        196608  Aspnet.isapi.dll 16-Jan-2003 22:27 1.0.3705.394         24576  Aspnet_regiis.exe 16-Jan-2003 22:27 1.0.3705.394         28672  Aspnet_wp.exe 16-Jan-2003 21:50 1.0.3705.394         69632  CORPerfMonExt.dll 16-Jan-2003 21:48 1.0.3705.394        303104  Mscorjit.dll 17-Jan-2003 20:47 1.0.3705.394       1953792  Mscorlib.dll 16-Jan-2003 21:50 1.0.3705.394       2269184  Mscorsvr.dll 16-Jan-2003 20:49 1.0.3705.394       2269184  Mscorwks.dll 17-Jan-2003 19:52 1.0.3705.394       1191936  System.Web.dll NOTE: Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.



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

Keywords: kbbug kbfix kbqfe kbhotfixserver KB813588

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.