Export to a file crashes both versions of Outlook


I have two versions of Office, 2003 and 2007. When i open Outlook and it does not matter who i am looged in as, or from what pc, Outlook crashes in 2007 and restarts when i try to export a sub folder to a file and it does not matter who's inbox i use.

Office 2003 errors as soon as i click import/export with "The messaging interface has returned an unknown error, if problem persists, restart Outlook. Agaon does not matter what machine i am logged on from?

What is going on. I have the latest office service packs on all machines.

Who is Participating?
monarchitConnect With a Mentor Author Commented:
No fix found

How are you doing?

Check this link, there is a "post SP" hotfix for 2007:

You have only one version of Oulook, 2003 or 2007 on each PC, right? You don't have these installed on the same pc?

Try empyting out your deleted files folder, your .pst might be very large!

When you say multiple logins and pc's, are there more then one computer connected to a network? If so, the folder issue might be from a mapped drive that is not finding its target, are the drives that you use on the network all up and working?

Also - try running outlook in safe mode:
Hope this helps,
What could be happeing is that a Macro Rule or Outlook add-on is enabled at startup which is causing your outlook to crash.
If you have installed any Macro Rule or Outlook add-on e.g encryption add-on , PDF converter etc
Try this disabling theses

Outlook 2007: Disabling/Enabling Add-ins

Disable Macro
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Hi, I have the same problem. I have XP SP3 and Outlook 2003. All the latest updates. I have also tried to uncheck all add-ins and started in safe mode. No difference...

What to do?
If Outlook is acting up , best to completely uninstall Outlook and do a fresh install.


I know it not the best solution , but sometimes the simple solution is the answer.
I cannot replicate the behaviour you are seeing.
I have seen problems with this command in two situations:
a) path length too long - try saving to a short path
b) attachments freaking it out - try exporting a folder with only a few simple messages, and work up
monarchitAuthor Commented:
no fix found
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.