Microsoft KB Archive/259713

= Custom Import Fails to Import Date Attributes After an Upgrade to ADSI 2.5 =

Article ID: 259713

Article Last Modified on 4/29/2000

-

APPLIES TO


 * Microsoft Site Server 3.0 Standard Edition

-



This article was previously published under Q259713



SYMPTOMS
When you upgrade Active Directory Service Interfaces (ADSI) to version 2.5, Microsoft Site Server Custom Import returns empty strings for all of the user data defined as GeneralizedTime attributes.



CAUSE
This problem occurs because ADSI 2.5 changes the way that GeneralizedTime attributes were handled in previous versions.



WORKAROUND
To work around this problem, perform one of the following:

  Open the \Bin\P&m\html\dsexport.asp file, and then comment out line 74 as follows: 'g_fExportMode = MODE_FASTADS and then uncomment line 76 to this:

g_fExportMode = MODE_ADODB -or-

  Open the \Bin\P&m\html\dsexport.asp file, and then add the following after line 874 in the WriteUser Sub: oUser.GetInfo(&quot;&quot;) 



STATUS
Microsoft has confirmed that this is a problem in Microsoft Site Server version 3.0.



MORE INFORMATION
Custom user data is stored in the tblReference table in the Prop column as a VARCHAR (255). When a GeneralizedTime attribute is imported with ADSI 2.1, the format is an unseparated string &quot;YYYYMMDDHHMMSS.&quot; ADSI 2.5 uses the format &quot;M/D/YY H:MM:SS AM?PM.&quot;

Keywords: kbprb KB259713

-

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

© Microsoft Corporation. All rights reserved.