BES Express Support
 

Not sure if this is the best place/if there's anywhere to ask about BES Express anymore but our BES users have stopped being able to send emails to external or internal recipients. I've checked permissions/updated MAPI/recreated the accounts on BES/wiped phones/made sure that sends as works for that BES Admin/run IEMSTest/recreated the MAPI profile/restarted all the services/set-up the user to run in its own static mailbox agent but the users are still not able to send emails from their phones.

The errors is always pretty much the same/not sure if someone here can advise:
[40700] (12/14 17:24:14.087):{0x3D28} {<sender>} Receiving packet from device, size=138, TransactionId=133779, Tag=9286, content type=CMIME, cmd=0x3
[30112] (12/14 17:24:14.088):{0x3D28} {<sender>} Receiving message from device, RefId=5036737, Tag=9286, TransactionId=133779, Date=14/12/2015 17:24:17
[30447] (12/14 17:24:14.211):{0x3D28} No EntryID found for =SMTP:<recipient>
[20482] (12/14 17:24:14.211):{0x3D28} ResolveNamesMAPI ResolveName(1) succeeded, but list does not contain EntryID for all items
[30147] (12/14 17:24:14.211):{0x3D28} {<sender>} MAPIMailbox::Send(ppMAPIMessage) Cleanup - HrGetOneProp (0x8004010f) failed
[30549] (12/14 17:24:14.211):{0x3D28} {<sender>} Send() failed: ERR_BAD_RECIP, RefId=5036737, Tag=9286
[40277] (12/14 17:24:14.211):{0x3D28} {<sender>} Sending message error to device for message 5036737
[40583] (12/14 17:24:14.212):{0x3D28} {<sender>} Sending packet to device, Size=45, Tag=72965,

Re: BES Express Support
 

Error "MAPI error 0x8004010f" appears in the Windows Application and BlackBerry Enterprise Server logs

can help some

is your GC reachable from BES?

Re: BES Express Support
 

I've tried to follow the article as much as possible, although it doesn't list specific issues. I'm afraid the compatability matrix no longer seems to be available but I've tried what seems to be the latest version of CDO/MAPI: 6.5.8353 but it hasn't helped.

BES can definitely talk to GC. To clarify we co-host our BES server on our Exchange server.

Re: BES Express Support
 

what version Exchange?
What version server OS?

Re: BES Express Support
 

We are using Update Rollup 8 v2 for Exchange Server 2010 SP3 with Windows 2008 R2 SP1.

Re: BES Express Support
 

Mail server - BES12 - 12.3 has the chart

Re: BES Express Support
 

I think it's kind of supported as we use: MAPI/CDO 8.3.8353.0 (the issue started with MAPI/CDO 6.5.8244.0, I then tried: MAPI/CDO 8.3.8309.0 and are now on: MAPI/CDO 8.3.8353.0).

I'm not 100% sure but I manually set-up LDAP search and it seems to have kind of started working now.

Originally it was set to:
LDAPSearch=1
I tried 0 but it didn't help.

I switched it back to 1 and set: LDAPALPSearch/LDAPBaseDN/LDAPDomain/LDAPPIMSearch/LDAPTimeout and it seems to have started working again.

I have noticed this in the Event log however:
ResolveProxyMAPI(1) - pAddrBook->PrepareRecips (0x80040200) failed

Hopefully it means this is kind of working but not sure why it broke/exactly what fixed it.

Re: BES Express Support
 

It looks like I spoke too soon. If you don't send an email for a while it errors on the first one. If you then retry it works fine however and subsequent emails also work fine.

[40700] (12/17 11:59:30.477):{0x4A54} {user@domain.com} Receiving packet from device, size=133, TransactionId=-2145811, Tag=541946, content type=CMIME, cmd=0x3
[30112] (12/17 11:59:30.477):{0x4A54} {user@domain.com} Receiving message from device, RefId=560465, Tag=541946, TransactionId=-2145811, Date=17/12/2015 11:59:26
[20265] (12/17 11:59:30.597):{0x4A54} {user@domain.com} MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80004005) failed
[20472] (12/17 11:59:30.637):{0x4A54} {user@domain.com} Send() failed: ERR_SUBMIT_MAIL, RefId=560465, Tag=541946
[40277] (12/17 11:59:30.637):{0x4A54} {user@domain.com} Sending message error to device for message 560465
[40583] (12/17 11:59:30.637):{0x4A54} {user@domain.com} Sending packet to device, Size=44, Tag=2479749, TransactionId=-697131

Re: BES Express Support
 

maybe point to a GC on a DC

if using 2008 a DC can block NSPI connections which can do similar
https://support.microsoft.com/en-us/kb/949469

Re: BES Express Support
 

I have tried increasing that to 1000 but it hasn't helped. we run 2008 R2 which does seem to require the registry key to see the errors in the Event log but there's nothing logged on the DCs for this.

Re: BES Express Support
 

NSPI connection limits when using a Microsoft Windows Server 2008 - 2012 Global Catalog Server - NSPI Bind Limit exceeded

NSPI connection limits.