outlook xp translation error 0x80070057 import'g contacts fr exce

[Peter]

I'm running Windows XP with SP3 and latest updates with Office XP small
business.
When I try to import contacts from an excell spreadsheet I get the error:
Translation Error MAPI 0x80070057 and will not allow the import of my
contacts. The file was an export prior to an XP reload. I do not see much to
help from the Microsoft website, any ideas

 

[Brian Tillman [MVP-Outlook]]

I'm running Windows XP with SP3 and latest updates with Office XP small
business.
When I try to import contacts from an excell spreadsheet I get the error:
Translation Error MAPI 0x80070057 and will not allow the import of my
contacts. The file was an export prior to an XP reload. I do not see much
to
help from the Microsoft website, any ideas

Is the Business Contact manager installed? If so, if the import for a regular
Contacts folder or the business contacts? Why did you export anything? Do
you still have access to the PST that was in use prior to the reload? That's
what you should have saved, not an export of anything.

 

[Karl Timmermans]

If you're running BCM - then the import/export process is a separate and
different animal then the one contained in standard Outlook so this is
really a BCM related question. BCM stores it's primary data in a backend
SQL database whereas standard Outlook will have it in a PST file (assuming
no Exch in play).

However, in general, there are 3 primary reasons that the import/export
wizard will suddenly retire with a less than an informative message which
are:

#1 - There is an issue with the header field names for the file. Since you
mentioned that this was an exported Outlook file - can safely rule that out
since Outlook uses its "very safe" internal field names on an export so not
likely to be the cause of anything in this case

#2 - It encountered some data it didn't like in one of the contact items.
Unfortunately, the only remote clue you have as to which contact item is
causing this is to take a look to see if anything got exported at all and
go from there.

#3 - Corrupt contact item(s) that is/are seldom referenced in normal
day-to-day operation. In this case, it's impossible to directly identify
which contact item it is since it can't be recalled. Given you're
description - not likely to be the cause since you have exported your data
and error has occured on import - so issue will be related to item#2

The other item noticed is that when importing in standard Outlook and the
"Check for duplicates" is checked - Outlook can become very, very moody as
to if it is going to complete the import without an error - something else
to check.

Of course, if you are not using BCM (or importing to a PST file), then to
echo a question already asked - why are you exporting/importing at all? -
wrong way to move information.

Karl

--
____________________________________________________________
Karl Timmermans - The Claxton Group
ContactGenie - QuickPort/DataPort/Exporter/Toolkit/Duplicate Contact Mgr
"Contact import/export/data management tools for Outlook '2000/2010"
http://www.contactgenie.com