Now that MAPICDO has been updated to support connecting to Exchange 2013 using RPC/HTTP, and the guidance for programmatically building profiles has been published, Dave has published a pair of articles which will be very helpful for customers using MFCMAPI in such environments. The first covers using the guidance to build a profile for connecting to Exchange 2013:
The second article covers a scenario likely to be encountered during migrations/upgrades, building a profile that works against both Exchange 2013 and Exchange 2010:
Stephen, can you help or point me to how to track the cause of MAPI_E_NETWORK_ERROR when trying to create a MAPI profile on an Exchange 2013 environment please? My application needs RPCHTTPProxyMap_Myapp set. Here are the details:
- we originally had 2 MBX (let's say EXCH1 and EXCH2 in company.local) servers and another one running CAS. We were able to create MAPI profiles, with no problems.
- then, we removed the CAS server and installed CAS role on both servers running the mailbox roles.
- We have 2 databases, one on EXCH1 and one on EXCH2 and, from our application running on EXCH1
- my app running on EXCH1 could (and still can) create MAPI profiles for any users, whether the associated mailboxes are stored on EXCH1 or EXCH2.
- however, if I run the same application on EXCH2, under the built in domain administrator (which was used whenever installing or changing Exchange roles, and has full privileges on the entire organization) where the RPCHTTPProxyMap entry points to the local CAS server, we always get MAPI_E_NETWORK_ERROR.
- when I created another account, with similar privileges as the Domain administrator, with the mailbox on the database stored on EXCH2, and I run my application under this new user, I can create MAPI profiles for any user.
In both scenarios (running my app under Domain Administrator or under the new user) I created the RPCHTTPProxyMap entry with the same value, pointing to the local CAS, therefore that is not the cause. Also, it is not my application, given that it works without problem under the new account.
I suspect that something in the CAS configuration is causing the problem, but I do not now how to track it down.
Are there any tools that I could use to see what exactly causes this error? Can you give me any hints on what to look for?
One more thing: I do not know if I need to configure any additional parameters on the CAS servers, but I installed from scratch a second MBX/CAS to another environment and everything works properly.
Thank you in advance,