Mapi Error 0x80070057 is returned when an Invalid Parameter is encountered.
Assuming that this error occurs "all the time" and not just a one-time blip,
then the error would logically appear to be in contact #1382 given that the
first 1381 were imported. Take a look at that to see if there is anything
visible or create a copy of your worksheet, delete that particular contact
and see how far you get. It is possible that more then one contact record in
your Excel worksheet may have the same issue (whatever that issue may be) so
repeat the above process as often as necessary if the problem is not visibly
evident.
Karl
___________________________________________________
Karl Timmermans - The Claxton Group
ContactGenie - Importer 1.3 / DataPorter 2.0 / Exporter
"Power contact importers/exporters for MS Outlook '2000/2007"
http://www.contactgenie.com
> Hello,
>
[quoted text clipped - 19 lines]
>
> Amy
AmyR in So Cal - 18 Aug 2007 18:06 GMT
Thank you Karl,
I am going thru my list in sections and skipping the one's that have errors
and will input these manually later. I appreciate the explanation of the
error as that helped me figure out how to proceed.
Amy
> Mapi Error 0x80070057 is returned when an Invalid Parameter is encountered.
> Assuming that this error occurs "all the time" and not just a one-time blip,
[quoted text clipped - 36 lines]
> >
> > Amy
Sajit - 01 Feb 2008 19:13 GMT
The wizard should have allowed the import of those records where there isn't
any errors.
In my case I don't see apparent errors. No records are imported.
Hope to see MS improve the wizard.

Signature
Sajit
Abu Dhabi
> Mapi Error 0x80070057 is returned when an Invalid Parameter is encountered.
> Assuming that this error occurs "all the time" and not just a one-time blip,
[quoted text clipped - 36 lines]
> >
> > Amy
Karl Timmermans - 01 Feb 2008 20:40 GMT
First and foremost, there is a contradiction in terms of your original post
versus the last response. In the first post you stated that 1381 of 1782
records were imported and in the last response you mentioned "no records"
were imported - two completely different case scenarios.
Since the original scenario has already been addressed in terms of things to
try - this reply is related to "no records being imported".
Going on the premise that there is nothing wrong with your configuration in
terms of the import/export filters, the operative statement here is "don't
see <apparent> errors" with the emphasis on <apparent>. Given no records
were imported, than there is likely something in the header row (you do have
one correct?) that it doesn't like - either in construct or in one or more
field names. We have run across more than one case where a file couldn't be
imported via Outlook but was something that any of the ContactGenie products
could deal with (or identify the cause of an issue). In reality, all that
was required was fixing the data file to enable Outlook to successfully
import it for those who had the time and inclination. You may also want to
save your Excel worksheet as a CSV file to see if the same error occurs
(only to exclude any issues related to a problematic XLS file which is also
something we've run across in isolated cases over the years).
One quick test you can do is create a new dummy CSV file (and/or Excel
worksheet with a defined named range) to import with 2 lines similar to
something below:
Lastname,Email Address
SomeName,xxx@xxx.xxx
If you can import that file with no problems, the odds are likely 100-1 that
your Outlook import filters are OK and the issue is with the file you are
trying to import. If you can't - then there are other issues at play in your
setup and would recommend doing a "Detect and Repair".
Karl
___________________________________________________
Karl Timmermans - The Claxton Group
ContactGenie - Importer 1.3 / DataPorter 2.0 / Exporter
"Power contact importers/exporters for MS Outlook '2000/2007"
http://www.contactgenie.com
> The wizard should have allowed the import of those records where there
> isn't
[quoted text clipped - 55 lines]
>> >
>> > Amy