Problem with Vista Windows mail

Hi everyone,

We have this foxpro 8 program that getting email from Outlook 2000, 2003, 2007 with MAPI32. It works fine until we try it on Vista's Windows mail. Everytime it runs "fetch" and get the meesage, the program will just break and pop up an error message saying

"An error occurred communicating with your MAPI message system. If you are using Microsoft Outlook try checking the 'Verify email address when sending messages' checkbox in the System Screen on the Other tab"

It could be that the MAPI32 doesn't support Windows Mail but I can't find any reference on Microsoft website. Has anyone ran into this problem before

Thanks

Jack

Yes, on the same mentioned site in your other thread I saw this problem reported as well.

I found a similar thread with no real answer

http://www.universalthread.com/wconnect/wc.dll 2,15,1237482

and another one with an answer from Nigell Gomm http://www.universalthread.com/wconnect/wc.dll 2,15,1165365

I'm not sure if it can help.

Also what is the exact message number I found this website

http://rselby.net/out2_3.htm

which lists lots of different errors related with Outlook. Perhaps you would be able to find your answer there.

thanks for the reply Naomi, in my case, the program can run on Outlook2000, Outlook2003 or even Oulook2007 in Vista without any problem. Only Vista Windows Mail will cuz the problem to occur. And it still can sign in, send message but only fail at the point of "fetch" the message. Very weird.. I unisntall the Antivirus software with no luck.

-Jack

Sorry, I don't know then. I'm not having Vista here.

Good luck with finding a solution and if you find it, please, let us know.

You may also try to post in Outlook forum.

Hi Phil,

when I said Fetch I mean the program fetch all emails from the default email client's in-box. Here is a piece of code:

IF MainApp.OpenMail(.T.)
MainApp.CloseWindows()
MainApp.Wait(MainApp.GetLocalString(1238, STRINGSOURCE_ID, .T.))
WITH MainApp.OLE
.Messages.FetchUnreadOnly = .T.
IF NOT MainApp.NoMessageTypes
.Messages.FetchMsgType = MSG_CIECA
ELSE
.Messages.FetchMsgType = ''
ENDIF
.Messages.FetchSorted = .T.
.Messages.Fetch() <-- - failed right here
FOR i = 0 TO .Messages.MsgCount - 1

...

...

again this code work fine with Outlook Express, Outlook 2000, 2003, 2007 and only Windows Mail have problem with it. Any input will be appreciated, Thanks!

Tamar E. Granor wrote:

The question you need to ask (and I don't know the answer) is whether Windows Mail is an Automation server. I won't be surprised if it's not because it's a successor to Outlook Express, which has never been an automation server. Tamar

Hi Tamar, I am not sure what automation server is but I do know the program works fine with Outlook Express. Thanks.

Phil Brammer wrote:

Do you have Windows Mail set up to be the default mail handler Also, Windows Mail by default prevents the sending of messages programmatically.

Hi Phil, yes, the WIndows Mail has been set to default. And the sending mechanism is working properly. only when I try to get message , it fail.

Naomi Nosonovsky wrote:

What is MainAPP and OLE in this case Are you using some third party tool to get e-mails

I am taking over this project from another guy who can't figure it out and quitted. As I know we are using MAPI OLE automation support to get e-mails and the MSMAPI32.ocx that we use are the latest (version 6.0xx )

Naomi Nosonovsky wrote:

Is it the program you wrote or it's using third party tool Since it works with Outlook Express, it's not OE outomation, it's probably working through MAPI interface.

yes, you are right, we are using MAPI OLE automation support to get e-mails. I posted the question in another group but never able to get an answer, it's hard to believe that nobody ever ran into this problem before.. Thanks and please let me know if you have any idea or suggestion.

Long time ago I used MapiMail class by Nigel Coates from http://nbcsoftware.com/freeware.html (MapiMail). May be you can download and try it and see if it has the same problem.

I would think the problem may be coming from Windows Mail.