mfcmapi issue with WIN7\Outlook 2010\exch2003?

Jan 11, 2011 at 7:54 PM

Attempting to use mfcmapi for customer site evaluation regarding why exchange 2010 custom attribute 1-15 data can not be obtained thru entended mapi calls. Mfcmapi works fine in-house on xp\outlk 2007\exch 2003 as well as xp\outlk 2003\exch 2003, however, when run on in-house win7\outlk 2010\exch 2003 get one of two conditions:

a) Run mfcmapi\session\logon & display store table\click ok on default profile\address book\open default directory results in displaying only "off-line address book" content, or

b) Run mfcmapi\session\logon & display store table\click ok on default profile\address book\open default directory results in "Windows Security\Mail Application\Connecting to user@domain \enter password dialog".  Proper domain\user name is detected (in this case domain admin logged into machine which has valid exch account and for which outlk 2010 works fine) but entering correct password results in just repetitive cycling of same Windows Security dialog (will not logon\authenticate user).

So can not access on-line GAL content with this machine\outlook\exch combination. Any ideas? Will eventually try at customer site to see if works ok but looking to see if any known win7 issues first.

Guess while I'm at it... We have a service that works in all prior exchange versions (exchange 2007 is an unknown) which grabs display name\alias\fax number or custom attributes 1-15 if warranted. Running under exch 2010 we get all info OK except custom attributes data. Limited research is leading towards custom attributes may no longer be accessible via extended mapi to exchange 2010 and only stored in AD.

Appreciate any thoughts.

Jan 12, 2011 at 2:26 PM

I don't know why you'd suspect Win7 for any of this. You appear to have tried Outlook 2010+Exchange 2003 only from Windows 7. You didn't try it from Windows XP (at least, not that you mentioned). We use Outlook 2010 on Windows 7 all the time.

Since your end goal is to test something with Exchange 2010, why are all your in house tests with Exchange 2003? Shouldn't you set up an Exchange 2010 server and learn from it what does and doesn't work?

Jan 12, 2011 at 5:41 PM

Thanks for reply and sorry if post disturbed you. Long time since used mfcmapi and simply looking to re-familiarize prior to working at customer site. Not blaming WIN7 or Outlook 2010 for behavior we experienced during testing and only sought to get heads up (if any) prior to moving to production environment.