Certificate Export Problem with the LDAP Exchange Management Agent (323182)


The information in this article applies to:

  • Microsoft Metadirectory Services 2.2 SP1
This article was previously published under Q323182

SYMPTOMS

Certificates that flow from the metaverse to Microsoft Exchange 5.5 are not usable after they are exported to Exchange.

CAUSE

The certificates are exported to Exchange as raw text data; Base64 encoding is not used because the data already uses Base64 encoding. If you use the LDAP Exchange management agent (MA) to export the user certificates and the user MIME certificates without using the binary Base64 encoding function, the MA (Cdir_ldp.exe) inadvertently changes two bytes of the attribute data 4,000 characters into the data.

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 version of Microsoft Metadirectory Services 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:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

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 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
   ----------------------------------------------------------
   03-Jan-2002  16:37  2.2.1300.16    175,104  Cdir_ad.dll
   20-May-2002  14:01  2.2.1300.26  1,015,296  Cdir_ex.exe
   12-Jul-2002  13:50  2.2.1300.29  1,031,680  Cdir_ldp.exe
   20-May-2002  14:01  2.2.1300.26  1,017,856  Cdir_ln.exe
   20-May-2002  14:01  2.2.1300.26  1,060,864  Cdir_nt.exe
   20-May-2002  14:01  2.2.1300.26    998,400  Cdir_nw.exe
   20-May-2002  14:01  2.2.1300.26    987,648  Cdir_vns.exe
   20-May-2002  14:00  2.2.1300.26    964,096  Importt.exe
   20-Sep-2001  16:41  2.2.1300.10     26,624  Ldapschema.dll
   22-Apr-2002  09:04  2.2.1300.21  1,030,656  Viacompact.exe
   07-Jun-2002  10:44  2.2.1300.28  1,266,176  Viaserver.exe
   20-May-2002  14:01  2.2.1300.26    997,888  Zscript.exe 
   01-Aug-2001  15:17                     834  Updoid.bat  
   25-Jul-2001  15:08                 166,356  Db5attrib.oid

STATUS

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

MORE INFORMATION

This problem occurs if the certificate data is more than 4,000 characters long. Note that this problem may occur with any text attribute that is more than 4,000 characters in length.
Modification Type:MinorLast Reviewed:9/30/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbQFE KB323182
©2004 Microsoft Corporation. All rights reserved.