XADM: Directory Import Error: Unable to Process Object

 Last reviewed: April 15, 1997
Article ID: Q155743
The information in this article applies to:
  • Microsoft Exchange Server, versions 4.0 and 4.0a

SYMPTOMS

After you perform a Directory Import in the Exchange Administrator program, the following error message is displayed: 

   The directory import from the file <filename>.CSV is complete.

   <x> error descriptions were recorded in the system's application event
   log. The file <filename>.err contains copies of all object descriptions
   containing errors.
The following error message appears in the Application Event Log, and in the <filename>.err file 

   Unable to process object <Username> because the import line must contain
   the same number of fields as the header line. <x> were expected. <n>
   were found.
where <x> is a larger number than <n>. The Directory Import fails.

WORKAROUND

  1. Highlight the cells in the empty column(s) (not the whole column),

  2. Click Format and click Cells.

  3. Under Category, select Text on the Number tab

  4. click OK. On the File menu, click Save as, and verify that it is being
saved in .csv format.

  1. Close the file. Do not save when prompted, and re-run Directory Import.

NOTE: Every time this file is modified, the cells must be reformatted.

Additional query words: administrator
Keywords : kbusage XADM
Version : 4.0 4.0a
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 15, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.