WHAT the hell: Word couldn't send mail because of MAPI failure: "Unspecified error".. NO one answere..
WE have noticed a number of our Outlook 2003 users on XP SP3 CANNOT send Word file as attachment. Error being so general and even worse, This same error is ALL over the net with various flavors of Office and OS's. We have spent three days searching and applying EVERY ones solutions that worked for the individual. AS with us and other, it didn't work for us:
XPv3
Office Enterprise 2003
Exchange 2007
rename all mapi*.* repair office.
change reg keys
add to ini's
reinstall Office.
reinstall fresh XP load and office. <--this on blows my mind (start with no win updates, but, running outlook from exchange server account on domain.)
run fixmapi.
check WMI for errors with scan tool
NOT using any fax
Now, to blow mind more. Uninstall office 2003 on same load. Load 2007. works. Works for us, but all over the net folks with 2007 have the issue. And, we do not have corp lic. for 2007.
Another, and here is where the answer lies somewhere in this:
set hotmail as default mapi client. works.
somewhere a failure with "seeing" calling Outlook as the mapi client is the problem.
XPv3
Office Enterprise 2003
Exchange 2007
rename all mapi*.* repair office.
change reg keys
add to ini's
reinstall Office.
reinstall fresh XP load and office. <--this on blows my mind (start with no win updates, but, running outlook from exchange server account on domain.)
run fixmapi.
check WMI for errors with scan tool
NOT using any fax
Now, to blow mind more. Uninstall office 2003 on same load. Load 2007. works. Works for us, but all over the net folks with 2007 have the issue. And, we do not have corp lic. for 2007.
Another, and here is where the answer lies somewhere in this:
set hotmail as default mapi client. works.
somewhere a failure with "seeing" calling Outlook as the mapi client is the problem.
ASKER
PS. ... Outlook is the default in IE and Word is in Outlook. What we have so far is ANY program that can send an attachment and use the mapi client cannot use outlook.. BuT if we set "hotmail".. all good. CRAZY.. and, this error is seen from 2004 and up with all types of setups and window versions.. Microsoft even goes as far as to say: Make sure outlook is installed. DUH.
I just went through the registry and win.ini to check that all entry's are there under "mail"..
We have turned around and installed office 2007 on top of the same win setup and it all worked fine.. what is outlook 2003/0ffice 2003. We have used a unpacked enterprise from a folder on network. We are going to go download a new set up.
I just went through the registry and win.ini to check that all entry's are there under "mail"..
We have turned around and installed office 2007 on top of the same win setup and it all worked fine.. what is outlook 2003/0ffice 2003. We have used a unpacked enterprise from a folder on network. We are going to go download a new set up.
What we have so far is ANY program that can send an attachment and use the mapi client cannot use outlook
This is actaully quite a common issue
When ever you send an email or attachement from another program such as word, excel, adobe ect ect
It doesnt really use Outlook Per say
It Uses soemthing called a MAPIMail Service
This MAPIMail Service is quite dependant on the Mapi dlls on the local machine.
More often than not these dlls can become broken or corrupt
Often happens after Office/outlook is upgraded or and application that uses the MAPIMail Service.
Should any one of the mapi dlls become broken or corrupt the MAPIMail Service used by outlook will stop functioning
The way to resovle is is by loggin onto the PC as an Local Amdin
Make sure all applications are closed on the PC
make sure show hidden files and folders is selected
Search for your mapi dlls
Once found renamen them to .old
Retart the PC, and re-open outlook and new working dlls should be created
Open outlook
Then try the Send Attachment to Mail Recipient from your other applicaions
Heres a good link to a Site I use often when I come across PCs that are experiening a MAPIMail Service Issue
http://www.ctimls.com/support/kb/error%20fixes/fix_mapi_error.htm
This is actaully quite a common issue
When ever you send an email or attachement from another program such as word, excel, adobe ect ect
It doesnt really use Outlook Per say
It Uses soemthing called a MAPIMail Service
This MAPIMail Service is quite dependant on the Mapi dlls on the local machine.
More often than not these dlls can become broken or corrupt
Often happens after Office/outlook is upgraded or and application that uses the MAPIMail Service.
Should any one of the mapi dlls become broken or corrupt the MAPIMail Service used by outlook will stop functioning
The way to resovle is is by loggin onto the PC as an Local Amdin
Make sure all applications are closed on the PC
make sure show hidden files and folders is selected
Search for your mapi dlls
Once found renamen them to .old
Retart the PC, and re-open outlook and new working dlls should be created
Open outlook
Then try the Send Attachment to Mail Recipient from your other applicaions
Heres a good link to a Site I use often when I come across PCs that are experiening a MAPIMail Service Issue
http://www.ctimls.com/support/kb/error%20fixes/fix_mapi_error.htm
ASKER
@apache09
Thanks for the reply. If you notice in my remarks we have attempted so far three days of various searches and applied everything we could find to do. Renaming included.
We even started with a FRESH WinXP load. A new MS download of our enterprise Office. Tested without updating office or OS. Tested with updating Office only. Test updating OS only. Same results.
Along with the generic "unspecified" error we get the common Event ID 2002, source "LoadPerf" which also leads to the mapi dll errors. WHAT BLOWS AND IS WEIRD, is we can on this SAME machine uninstall office 2003, load 2007 enterprise and it WORKS. Thus, why we downloaded a fresh copy of 2003 from MS. We are again testing that theory
One other common ground has been loading on Dell 745/755. Today we are going to load on a Dell 390. This is where we are at, attempting anything new to try.
Thanks for the reply. If you notice in my remarks we have attempted so far three days of various searches and applied everything we could find to do. Renaming included.
We even started with a FRESH WinXP load. A new MS download of our enterprise Office. Tested without updating office or OS. Tested with updating Office only. Test updating OS only. Same results.
Along with the generic "unspecified" error we get the common Event ID 2002, source "LoadPerf" which also leads to the mapi dll errors. WHAT BLOWS AND IS WEIRD, is we can on this SAME machine uninstall office 2003, load 2007 enterprise and it WORKS. Thus, why we downloaded a fresh copy of 2003 from MS. We are again testing that theory
One other common ground has been loading on Dell 745/755. Today we are going to load on a Dell 390. This is where we are at, attempting anything new to try.
ASKER
PS. also the Event ID 2002 is the .MOF file created for outlook service could not be loaded.. which leads to wmi and mapi dll stuff in searches
ASKER
UPDATE:
removed office 2003. Installed 2007. Noticed a new "MAPIR.dll was the only thing changed and was placed in the /12/1033 location. Mapir.dll on 2003 is in the common files area. Test send as attachment worked. Removed 2007, installed newly downloaded Office 2003 standard. Test FAILED.
removed office 2003. Installed 2007. Noticed a new "MAPIR.dll was the only thing changed and was placed in the /12/1033 location. Mapir.dll on 2003 is in the common files area. Test send as attachment worked. Removed 2007, installed newly downloaded Office 2003 standard. Test FAILED.
"three days of various searches and applied everything we could find to do."
This is a bit general, and doesnt really tell us eveything you have done.
Thanks for clarifying
AS mentioned above the MAPI dlls do quite often break through Office Upgrades/Downgrades.
Once downgraded if broken, you may need too try and rename the mapi Dlls Again.
You only mention one above
In reality there should be at least 4 mapi dlls that need to be renamed or deleted
If you miss one of them, the fix wont work....
COnsidering the amount of time you have already spent on this, i would just flag it.
Theres more than one way to skin a cat, and since your using Office 2003 and windows XP there another soultion you can use here.
Rather than using the Send To functionality in Word or Excel that uses MAPIService you can setup/create a New Send To that actaully uses Outlook Itself
To do this
Right Click on Start and select Explore
Windows Explorer should Open.
Go to Tools>Folder Options>View
Select "Show hidden files and Folders"
Apply Okay
Under Documents and Settings>Your username
go to the "SendTo" Folder
Right click in the white space on the right
New>Shortcut
Assuming Office 2003 has been installed to the default location, copy and paste the following into "Type the location of the item"
"C:\Program Files\Microsoft Office\Office11\OUTLOOK.EX
Next - Name the shortcut (ie Outlook Email )
Next / Finish
Now when in Word you should be able to Go to File>Send TO>Outlook Email
It should create a New Email, Attach your file, and should be able to send with out error
Also
Now when you right click on any document, Select Send To>Outlook Email, or whatever you chose to name your new Send To shortcut, and a new mail item with be created with this document attached, you should then be able to send without errors.
This is a bit general, and doesnt really tell us eveything you have done.
Thanks for clarifying
AS mentioned above the MAPI dlls do quite often break through Office Upgrades/Downgrades.
Once downgraded if broken, you may need too try and rename the mapi Dlls Again.
You only mention one above
In reality there should be at least 4 mapi dlls that need to be renamed or deleted
If you miss one of them, the fix wont work....
COnsidering the amount of time you have already spent on this, i would just flag it.
Theres more than one way to skin a cat, and since your using Office 2003 and windows XP there another soultion you can use here.
Rather than using the Send To functionality in Word or Excel that uses MAPIService you can setup/create a New Send To that actaully uses Outlook Itself
To do this
Right Click on Start and select Explore
Windows Explorer should Open.
Go to Tools>Folder Options>View
Select "Show hidden files and Folders"
Apply Okay
Under Documents and Settings>Your username
go to the "SendTo" Folder
Right click in the white space on the right
New>Shortcut
Assuming Office 2003 has been installed to the default location, copy and paste the following into "Type the location of the item"
"C:\Program Files\Microsoft Office\Office11\OUTLOOK.EX
Next - Name the shortcut (ie Outlook Email )
Next / Finish
Now when in Word you should be able to Go to File>Send TO>Outlook Email
It should create a New Email, Attach your file, and should be able to send with out error
Also
Now when you right click on any document, Select Send To>Outlook Email, or whatever you chose to name your new Send To shortcut, and a new mail item with be created with this document attached, you should then be able to send without errors.
ASKER
@apache09
Yes, we see that as a work around. I was even wondering if that "send to" was the problem. I can send to everything but attachments.
Yes, we see that as a work around. I was even wondering if that "send to" was the problem. I can send to everything but attachments.
ASKER
@apache09.. to add to that.. I noticed that in word the new send to "outlook" does not show. Does of course for other areas in the context menu. And, note, we noticed also that the "send to" original mail did not work, thus our thought something not right with it.. that is, when doing "attachments"..
You mentioned I was a bit general on what solutions I tried. In the original post I listed a few, 8 and included reinstall, etc. to sum up; Some make program run as admin. Some did fix .ost. Some, change mapi*.* names and do repairs. Some save doc, reopen word. Some run fixmapi.exe. Some run scan and fix files. Some, change attachment size. Some run around computer three times....
This error is so generic that the cause and fix vary. Only fix so far is move to 2007. Tested on WinxP and Win7 all works again. For almost 10 years here running network and have never seen an issue like this. To top it off, didn't know it was existing until one person doing a certain job it had "stopped" after an upgrade to new PC. Then find a slew of them that wasn't working but they just wasn't using it. And then the icing, others, no problem. At first I thought it was from cloning and not running SID or not using sys prep. Then, allowing Right Fax integration.. but these also vary in network. But, some with this scenario work. others not. Tried with no SP on OS and Office. Tried updating Office, and XP.. still no go.
I quit pulling hair. I have started on teeth.
You mentioned I was a bit general on what solutions I tried. In the original post I listed a few, 8 and included reinstall, etc. to sum up; Some make program run as admin. Some did fix .ost. Some, change mapi*.* names and do repairs. Some save doc, reopen word. Some run fixmapi.exe. Some run scan and fix files. Some, change attachment size. Some run around computer three times....
This error is so generic that the cause and fix vary. Only fix so far is move to 2007. Tested on WinxP and Win7 all works again. For almost 10 years here running network and have never seen an issue like this. To top it off, didn't know it was existing until one person doing a certain job it had "stopped" after an upgrade to new PC. Then find a slew of them that wasn't working but they just wasn't using it. And then the icing, others, no problem. At first I thought it was from cloning and not running SID or not using sys prep. Then, allowing Right Fax integration.. but these also vary in network. But, some with this scenario work. others not. Tried with no SP on OS and Office. Tried updating Office, and XP.. still no go.
I quit pulling hair. I have started on teeth.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
The usual solution is to set your default mapi client.. i.e. set outlook as your default and make sure it has all of its settings.
I believe the other 'solutions' are simply fluff.. don't forget that on the internet you can find anything you want to support your case even if it is wrong.