We recently upgraded our Exchange server to 2010 SP1 and are now having issues with our MAPI Gateway connecting to it reliably. We had upgraded our MAS to v.4.2 a month or so prior to our Exchange upgrade and it was all working fine with Exchange 2003. I've gone through the MAPI Gateway installation guide for connecting NPM to Exchange 2010, but we're still seeing sporadic connections. I've actually stripped down the throttling policy more than what Mitel says to do in the hopes of fixing this issue, but it didn't fix anything.
For reference, we're running a 2 node DAG with a CentOS network load balancer (using Piranha). And we're using the latest version of the MAPI GW on the same server we used before. We have around 200 voicemail boxes as well.
First issue: Getting the NPUMAdmin account to authenticate correctly in the MAPI GW is difficult. When it works, and you don't modify the system, it works great. When it doesn't, you get "Failed to create MAPI Profile" errors. This seems to be more finicky than it should be.
Second issue: Sporadic connection from the MAPI GW to Exchange. The most frustrating issue is that voicemail does get delivered occasionally, but it's fairly sporadic. From my tracking of the issue, voicemail are getting delivered around midnight and then on days that we have very few people here.
In the msblog log file I see errors such as "Mailbox xxxx reinit reason = Failed in 'pAdapter->StoreVoiceMail'", "IMAP4 Store mail failed -> Invalid Store Response <APPEND Failed to append message to mail box INBOX>", "Unable to read Exchange Alias/Password for mailbox (phone number)", etc. which appear to be access issues, but this does work occasionally so there shouldn't be any access issues.
Mitel has punted this off to Microsoft and said it's not their issue. It appears as though the issue has something to do with connectivity limits in Exchange 2010. There are quite a few places in Exchange to make changes and I'm hesitant to just start trying things since I don't want to take down the whole email system.
Sorry for the length description. If anyone has dealt with this issue (especially number 2), I'm all ears!
Chris
For reference, we're running a 2 node DAG with a CentOS network load balancer (using Piranha). And we're using the latest version of the MAPI GW on the same server we used before. We have around 200 voicemail boxes as well.
First issue: Getting the NPUMAdmin account to authenticate correctly in the MAPI GW is difficult. When it works, and you don't modify the system, it works great. When it doesn't, you get "Failed to create MAPI Profile" errors. This seems to be more finicky than it should be.
Second issue: Sporadic connection from the MAPI GW to Exchange. The most frustrating issue is that voicemail does get delivered occasionally, but it's fairly sporadic. From my tracking of the issue, voicemail are getting delivered around midnight and then on days that we have very few people here.
In the msblog log file I see errors such as "Mailbox xxxx reinit reason = Failed in 'pAdapter->StoreVoiceMail'", "IMAP4 Store mail failed -> Invalid Store Response <APPEND Failed to append message to mail box INBOX>", "Unable to read Exchange Alias/Password for mailbox (phone number)", etc. which appear to be access issues, but this does work occasionally so there shouldn't be any access issues.
Mitel has punted this off to Microsoft and said it's not their issue. It appears as though the issue has something to do with connectivity limits in Exchange 2010. There are quite a few places in Exchange to make changes and I'm hesitant to just start trying things since I don't want to take down the whole email system.
Sorry for the length description. If anyone has dealt with this issue (especially number 2), I'm all ears!
Chris