Article ID: 327964
Article Last Modified on 10/11/2005
APPLIES TO
- Microsoft Data Access Components 2.8
- Microsoft Data Access Components 2.7
- Microsoft Data Access Components 2.6
This article was previously published under Q327964
SYMPTOMS
You might experience slow performance or high CPU utilization, or the system may stop responding. If you attach a debugger to the process, or you load a user dump file in a debugger with correct symbol files setup, you might experience high critical section contention. The following is an example:
0:177> !locks CritSec MSWSTR10!g_CritSec+0 at 1B64A010 LockCount 26 RecursionCount 0 OwningThread 0 EntryCount 522d0 ContentionCount 52373
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 MDAC 2.6/2.7 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 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 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 |
|---|---|---|---|---|
| 15-Aug-2002 | 08:57 | 2.70.9001.16 | 307,200 | Msadce.dll |
| 15-Aug-2002 | 08:57 | 2.70.9001.16 | 57,344 | Msadcf.dll |
| 15-Aug-2002 | 08:57 | 2.70.9001.16 | 131,072 | Msadco.dll |
| 15-Aug-2002 | 08:57 | 2.70.9001.16 | 53,248 | Msadcs.dll |
| 15-Aug-2002 | 08:57 | 2.70.9001.16 | 147,456 | Msadds.dll |
| 15-Aug-2002 | 08:57 | 2.70.9001.16 | 487,424 | Msado15.dll |
| 15-Aug-2002 | 08:57 | 2.70.9001.16 | 53,248 | Msadrh15.dll |
| 15-Aug-2002 | 08:57 | 2.70.9001.16 | 180,224 | Msdaprst.dll |
| 15-Aug-2002 | 08:57 | 2.70.9001.16 | 110,592 | Msdarem.dll |
| 15-Aug-2002 | 08:57 | 2.70.9001.16 | 32,768 | Msdfmap.dll |
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 KB327964
