MAPI woes

[fabwhack]

Hi all,

Hope someone can help me out. I've inherited a Exchange 2003 (on Windows 2003) server that on the surface is working fine, but has some big problems under the surface. I've only a little knowledge of Exchange, but am fairly experienced in other areas.

The main problem seems to be MAPI. ESM works fine, mail comes in and out etc, but any other non-Exchange application that uses MAPI falls over - in particular, BlackBerry Enterprise Server and Backup Exec.

BES fails when trying to connect to Exchange; looking at the logs, there's lots of references to MAPI error 0x80070057. We managed to get BES up and running on another server. However ...

BackupExec is worse: it was working for a while, but now when trying to back up the Exchange Information Store it's failing with the error:

MAPIAdminService::CreateMsgService Failed! hr = 0x8004010F

That error (8004010F) seems to be a generic MAPI error, which adds weight to my theory that the MAPI on the server is somehow a bit broken. I don't know enough about Exchange to tell why this isn't affecting other areas of the system.

The question is: how do I fix it? The mapi32.dll in \windows\system32 is the same date and time as the one in the Exchange \bin directory. Does anyone have any advice on how to proceed?

 

[Alshrim]

Both of these services have Agents installed on the exchange server. If the previous administrator used his account as the service accounts for these agents, things may have broken.
It's something to look at.

I know that Backup Exec doesn't NEED a service accounts, but some admins still use them ..

So you may want to start there.

AlRo
System Administrator
Ottawa, Canada.