Exchange 2010 - Exchange MAPI 连接问题

发布于 2024-08-28 16:55:05 字数 1112 浏览 8 评论 0原文

我有一个适用于 Exchange 2000/2003/2007 的软件解决方案，现在希望能在 2010 年之后使用。该软件在服务器上运行，并通过 RDO 与 Exchange 服务器通信，检索邮箱内的电子邮件。

在 Exchange 2000/2003/2007 上一切正常，但 2010 就不会改变。尝试访问邮箱时（调用 Session.getSharedMailbox - RDO lib）继续出现此错误：

10:35:31:865       11932    Error in   IMAPISession::OpenMsgStore(pbExchangeProviderPrimaryUserGuid): MAPI_E_FAILONEPROVIDER
ulVersion: 0
Error: The Microsoft Exchange Server computer is not available.  Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.
Component: Microsoft Exchange Server Information Store
ulLowLevelError: 0
ulContext: 1318 (MAPI_E_FAILONEPROVIDER)

从错误来看，交换服务器似乎已关闭，但事实并非如此，我可以从 Outlook 正常访问所有内容。我已经向 RDO 的开发人员提交了我的案例，我们仍在通信中，但我只是想这可能是某些新的 Exchange 2010 功能或体系结构更改或 MAPI 更改可能导致此情况？除了在邮箱上启用 MAPI 并授予对软件运行帐户的访问权限之外，我还需要配置什么吗？

有人遇到过类似的事情吗？任何帮助将不胜感激。

编辑：如果我在这台计算机上安装 Outlook（从而用 Outlook MAPI 替换 Exchange MAPI）一切正常，这告诉我问题是 Exchange MAPI？有 MS Exchange 开发人员吗？

原文

I have a software solution for Exchange 2000/2003/2007 and now hopefully after this for 2010. The software runs on the server and uses Exchange MAPI through RDO to talk the the exchange server, retrieving emails inside mailboxes.

All works fine on Exchange 2000/2003/2007 but 2010 just won't budge. Keep on getting this error when trying to access a mailbox (in call to Session.getSharedMailbox - RDO lib):

10:35:31:865       11932    Error in   IMAPISession::OpenMsgStore(pbExchangeProviderPrimaryUserGuid): MAPI_E_FAILONEPROVIDER
ulVersion: 0
Error: The Microsoft Exchange Server computer is not available.  Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.
Component: Microsoft Exchange Server Information Store
ulLowLevelError: 0
ulContext: 1318 (MAPI_E_FAILONEPROVIDER)

From the error it seems like the exchange server is down, but its not, I can access everything fine from outlook.
I've presented my case with the developer of RDO and we are still in correspondence, but I was just thinking this may be some new Exchange 2010 feature or architectural change or MAPI change that may cause this? Is there something I need to configure besides enabling MAPI on the mailboxes and giving access to the account that the software is running as?

Anyone ever ran into something similar? Any help will really be appreciated.

Edit: If I install outlook on this machine (thus replacing Exchange MAPI with Outlook MAPI) all works fine, which tells me the problem is Exchange MAPI? Any MS Exchange Devs on SO?

分享到QQ

分享到微博