| | Re: MAPI connections failing - but no alerts
It would certainly be nice if these types of errors could be monitored to provide alerts that point you directly to a root cause. The most likely reason that there isn't BES monitoring for these types of messages, is that MAPI errors are typically pretty generic. With respect to BES, these errors often expose an issue with a different component in your network (Exchange, GC, DC, etc.) so RIM will do best effort to identify these problems but won't necessarily provide monitoring sets for them. In your case, the MAPI_E_LOGON_FAILED messages simply indicated that the BESAdmin account was refused connection for one of several different reasons. (It sounds like the cause ended up being the NSPI bind limit in your case.) I've been in your shoes several times, spending hours researching an issue and wishing that the MAPI errors were more to the point. Often, they will send you off chasing a lead that ends up being a dead end.
You know your environment best, so your best bet is to get a good grasp on when these messages appear and then determine what the correlating root cause is. Then you can utilize the monitoring software in your environment and set up some SNMP traps to allow you to get on these problems proactively. Sounds like you should be in the clear for now though, especially with that NSPI limit increased on your GC's.