XADM: Importing a Large CSV Hangs and Eventually Consumes All MemoryID: Q222997
|
DAPI batch import may stop responding (hang) or take a long time to complete and the computer may eventually run out of virtual memory space.
The import routines that check for modified values did not register the fact that previous values had already been checked. This caused an exponential growth in the number of passes (and memory allocation) made during the import.
A supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. If you are not severely affected by this
specific problem, Microsoft recommends that you wait for the next Microsoft Exchange Server version 5.0 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 on support costs, please go to the following
address on the World Wide Web:
http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this fix should have the following file attributes or later:
File name | Version |
---|---|
Dapi.dll | 5.0.2232.0 |
Q154871 Determining If You Are Eligible for No-Charge Technical Support
Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0.
Additional query words:
Keywords :
Version : winnt:5.0
Platform : winnt
Issue type : kbbug
Last Reviewed: June 28, 1999