Article ID: 823954
Article Last Modified on 10/26/2006
APPLIES TO
- Microsoft Windows 2000 Professional Edition
- Microsoft Windows 2000 Server
SYMPTOMS
When you try to use a personal certificate that was generated by using the Microsoft Strong Cryptographic Provider option in Microsoft NetMeeting version 3.01, you may receive the following error message:
RESOLUTION
Hotfix Information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, 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:
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
No prerequisites are required.
Restart Requirement
You must restart your computer after you apply this hotfix.
Hotfix Replacement Information
This hotfix does not replace any other hotfixes.
File Information
The English version of this hotfix 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 ---------------------------------------------------------- 21-Jul-2003 11:31 5.0.2195.6748 124,688 Adsldp.dll 21-Jul-2003 11:31 5.0.2195.6748 132,368 Adsldpc.dll 21-Jul-2003 11:31 5.0.2195.6748 63,760 Adsmsext.dll 21-Jul-2003 11:31 5.0.2195.6761 381,712 Advapi32.dll 21-Jul-2003 11:31 5.0.2195.6753 69,392 Browser.dll 21-Jul-2003 11:31 5.0.2195.6680 134,928 Dnsapi.dll 21-Jul-2003 11:31 5.0.2195.6780 96,528 Dnsrslvr.dll 21-Jul-2003 11:31 5.0.2195.6753 47,376 Eventlog.dll 21-Jul-2003 11:31 5.0.2195.6759 148,240 Kdcsvc.dll 18-Jun-2003 08:43 5.0.2195.6758 205,072 Kerberos.dll 26-Mar-2003 12:37 5.0.2195.6695 71,888 Ksecdd.sys 13-Jul-2003 19:17 5.0.2195.6779 509,712 Lsasrv.dll 13-Jul-2003 19:17 5.0.2195.6779 33,552 Lsass.exe 17-Jul-2003 14:13 5.0.2195.6786 109,840 Msv1_0.dll 21-Jul-2003 11:31 5.0.2195.6601 311,568 Netapi32.dll 21-Jul-2003 11:31 5.0.2195.6783 360,720 Netlogon.dll 21-Jul-2003 11:31 5.0.2195.6784 931,088 Ntdsa.dll 21-Jul-2003 11:31 5.0.2195.6742 392,464 Samsrv.dll 21-Jul-2003 11:31 5.0.2195.6737 131,344 Scecli.dll 21-Jul-2003 11:31 5.0.2195.6737 306,448 Scesrv.dll 21-Jul-2003 10:03 5.1.2195.6788 146,704 Schannel.dll 15-Jul-2003 13:08 5.0.2195.6776 4,858,368 Sp3res.dll 21-Jul-2003 11:31 5.0.2195.6601 51,472 W32time.dll 16-Aug-2002 04:32 5.0.2195.6601 57,104 W32tm.exe 21-Jul-2003 11:31 5.0.2195.6741 126,224 Wldap32.dll
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Keywords: kbhotfixserver kbqfe kbwin2000sp5fix kbwin2000presp5fix kbqfe kbfix kbbug KB823954
