[conniet]

Hi, hope someone can help

I am running BES 5.01 on windows server 2008 against exchange 2007. I have quite a few users, but one is experiencing issues. He can send email to folks inside my domain but he cannot send to external email addresses (things work fine in outlook, though)

iemstest reports fine for him

All I see in the magt log is :


[20265] (05/12 13:22:56.691):{0x1858} {user email address} MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80004005) failed

[20472] (05/12 13:22:56.707):{0x1858} {user email address} Send() failed: ERR_SUBMIT_MAIL, RefId=1870005791, Tag=14634

[40277] (05/12 13:22:56.707):{0x1858} {user email address} Sending message error to device for message 1870005791

[40583] (05/12 13:22:56.707):{0x1858} {user email address} Sending packet to device, Size=46, Tag=11281, TransactionId=-873814658

[40279] (05/12 13:22:56.707):{0x1858} {user email address} SubmitToRelaySendQ, Tag=11281

[40279] (05/12 13:22:56.707):{0x1858} {user email address} SubmitToRelaySendQ, Tag=14634

[conniet]

I have heard from a few other users and this is happening to a few other people. And they are saying it will work for a period of time and then will stop working for a period of time. Very curious.

[rsk]

this looks like a permissions/account issue:

SubmitMessage (0x80004005) failed

is the service account getting locked out ?

[conniet]

I found the article (below) on another site talking about servername changes causing issues. I have not renamed any of my servers, but just before the problem started, one of my nodes failed over to the standby server. This made me wonder if having my active node running on a server with a different name (the standby server) was causing issues. I failed my node off the original standby server back to the original active server and followed up with the users - and this solved the problem for them.

Has this happened to anyone else? Should I expect issues everytime my nodes failover to the standby servers?

------Excerpt from other site --------------------------------

Turns out the servername was changed by one of my co-workers...

The issue has been associated with "Servername1" and stems from the server name, its relation the SQL database and the MDS service. Some time ago "severname1" was renamed to "servername2" at which time the problem started. The SQL DB has tables associated with the old server name causing an issue when trying route outgoing external mail appropriately. Unfortunately, the only clean way to resolve the issue *(according to RIM)* is to reinstall blackberry enterprise on "servername2" and correct the name during the install.

That being said, I'm posititive that there is a back door way to resolve the issue by changing the servername tables in the SQL DB but RIM refused to take us down that road becasue of how "high profile" our corporate account is...

[ldickie]

I'm not sure if this exact thing is related, but after spending a LOT of time on the phone with RIM support, I was told of a 'known issue' that RIM is working on that they are calling "MAPI Shared Heap Corruption". Basically, it's very similar to the older 4.6 server's "hung MAPI threads" issue.

Problems are -

• can't send/receive from BB devices (random)
• can't activate new devices (randomly) BBAdmin must completely remove user and re-add multiple times to get activated.
• random address book look-ups failing
• random calendar and address book reconciliation

I'm sure there are more symptoms, but these are what we have found.

The only "fix" is to fail-over to the standby server (if using HA). If not, you have to reboot the server (or stop and restart all BB services). Any of which is a huge pain.

RIM has no KB on this yet... but they said they are working on a fix... whatever that means.

If anyone else has heard of this or might have a KB on it, please share!!

[Raiden]

Experiencing the same issue intermittently - when i resart the disptacher service the problem goes away!!

40700] (07/17 00:18:41.964):{0x14F0} {USER EMAIL} Receiving packet from device, size=125, TransactionId=1111662454, Tag=466207, content type=CMIME, cmd=0x3
[30112] (07/17 00:18:41.964):{0x14F0} {USER EMAIL} Receiving message from device, RefId=1297985543, Tag=466207, TransactionId=1111662454
[20265] (07/17 00:18:42.198):{0x14F0} {USER EMAIL} MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80004005) failed
[20472] (07/17 00:18:42.230):{0x14F0} {USER EMAIL} Send() failed: ERR_SUBMIT_MAIL, RefId=1297985543, Tag=466207
[40277] (07/17 00:18:42.230):{0x14F0} {USER EMAIL} Sending message error to device for message 1297985543
[40583] (07/17 00:18:42.230):{0x14F0} {USER EMAIL} Sending packet to device, Size=46, Tag=271641, TransactionId=-868186788
[40279] (07/17 00:18:42.230):{0x14F0} {USER EMAIL} SubmitToRelaySendQ, Tag=271641