MAPI_E_FAILURE

I have a simple MAPI interface that has been working for years.  The user has
the option to open a send e-mail form.  The open form works fine for some
installations of Outlook but not others.  Here is the C++ code

flags = MAPI_DIALOG ;
error = lpfnSendMail( lplhSession, (ULONG)handle, &messg, flags, 0);

On some machines, notably 2003 server, Outlook fails to open and I get this
error.
MAPI_E_FAILURE
which is not terribly useful.

When that flag is not set it sends the message to Outlook without any
problems.

In my LAN it works on my xp machine with
Micrsoft Office Outlook 2003 ( 11.8217.8221 ) SP3
but it does not work on our 2003 server that has exchange installed to it.
It does have the same version of Outlook
Micrsoft Office Outlook 2003 ( 11.8217.8221 ) SP3.

My customer is using  Microsoft Office Outlook 2003 (11.8169.8172) SP3 on a
2003 server via Terminal Services.  It is not an exchange machine but there
is a separate Exchange server on his LAN.


Any suggestions would be most appreciated.

Bill

Hi,I have exact the same problem. My code is written in Delphi.

Hi,

I have exact the same problem. My code is written in Delphi. When sending an
e-mail "silent" it works, but when a dialog needs to be displayed
MapiSendMail returns MAPI_E_FAILURE.

Did you or anybody find a solution for this problem?

Thanks.

Kind regards,
Guus

Hello,Some research learned that this is probably caused by an ORACLE client.

Hello,

Some research learned that this is probably caused by an ORACLE client. See
http://forums.oracle.com/forums/thread.jspa?threadID=606204.

According to ORACLE documentation bug 5513561 (for ORACLE 10) and 8861816
(for ORACLE 11) are causing this problem. See http://support.oracle.com for
more information and a solution/work around.

Kind regards,
Guus Creuwels.

Hello,I am with the same problem when I use MAPI to send a email.

Hello,

I am with the same problem when I use MAPI to send a email. I also use de
ORACLE client.

I'd like to know if there are good news (any solution) for this problem...

Since now, thanks for the attention.

Daniel

There is no solution for this stupid MS bug."DSS Daniel" wrote:

There is no solution for this stupid MS bug.