[dgregait-21stsystems]

Good morning all,

I am receiving the following error in the event log on my BES.

Event Type: Warning
Event Source: BlackBerry Messaging Agent CCI-EXCHANGE Agent 1
Event Category: None
Event ID: 20265
Date: 10/1/2008
Time: 7:16:41 AM
User: N/A
Computer: CCI-EXCHANGE
Description:
{user@domain.com} MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80070005) failed

Followed by,

Event Type: Warning
Event Source: BlackBerry Messaging Agent CCI-EXCHANGE Agent 1
Event Category: None
Event ID: 20472
Date: 10/1/2008
Time: 7:16:42 AM
User: N/A
Computer: CCI-EXCHANGE
Description:
{user@domain} Send() failed: ERR_SUBMIT_MAIL, Tag=3804

We have seen these error's at random. and there is no pattern to users, time, or date. a user might have an issue one day, then the next (with nothing being done to the server) it works. This also goes the other direction a user was working fine yesterday, today now has an issue sending. again no changes made to the server or AD.

Blackberry server 4.1.6, I applied MR for SP6 last night.
ALL user permissions are in place and have not changed. (I have verified that the send-as permission is still in each AD account.)

The users at random currently get a red X while sending, "Desktop Email program unable to submit message".

As an example, The above error message happened at 7:21am this morning. I just took the users device and successfully sent myself a test message. I then RESENT the message that failed at 7:21 this morning and it also was delivered with no issue. again, between 7:21 and now we have made NO changes to the BES, Exchange, or AD. NO services stopped and started, NO server reboots, Nothing.

I have been working with BEs for over 5 years now and have never seen anything so random. If has any idea's that would be great. I am currently going to install the software on a different server to see if maybe it is the blackberry server software itself.

[dgregait-21stsystems]

Also to note, I have gone through all of microsofts "protected groups" and no users or groups that the users are in are members of a protected group. Nothing I have found points to a permissions issue.

[scott_perry]

This is what I found when I searched the Blackberry.com knowledge base for the log messages you posted.

BlackBerry Search Results

BlackBerry Search Results

Also, in the future, BES questions should be posted in the Admin section - you'll get a better response. Maybe one of the mods will move it

[dgregait-21stsystems]

Thanks Scott, I have looked at the first link and will be appling this Hot Fix shortly. As for the second one, I would be shocked (and would eat my own blackberry) if it was a permissions issue. Again this morning we had a user failed to send, then less then 2 hours later was able to send a message, again with NO changes to server, accounts, or services.

Thanks again for the links and I'll see how the first one goes in just a bit.

Could one of the MOD's move this to the BES section for me?

[dgregait-21stsystems]

Ok, so I know it's not a permissions issue. I did try the Hot-Fix Scott listed before, still getting sent message failures.

Send() failed: ERR_SUBMIT_MAIL, Tag=733
Sending message error to device for message 265676675

From the Blackberry log file.

Anyone else have any thoughts on this. I'm sure if I give it an hour and ask the user to re-send it will go out fine.

[scott_perry]

How is your connection between the BES and Exchange servers? What is the load on exchange when these errors are occurring?

[dgregait-21stsystems]

Well it turns out this has been going on since atleast the first of September, if not longer.

The BES was installed on the same server as Exchange, as part of the troubleshooting I have installed the BES on a different server then exchange and we still see the error's. The error's are at random and no extra activity on the servers can be found. We had 2 error's yesterday (Sunday) 5:28PM and 6:56PM, and then this morning (Monday) 8:16AM, 9:34AM, and 9:47AM.

Again the permissions are not changing, the send as is not being removed.

We have started looking at AD and our Global Catalog servers, but nothin jumps outs out, we can't seem to put a fingure on whats causing this. I am very close to calling Blackberry support and paying for a support call.

[sunray73]

Originally Posted by dgregait-21stsystems

Well it turns out this has been going on since atleast the first of September, if not longer.

The BES was installed on the same server as Exchange, as part of the troubleshooting I have installed the BES on a different server then exchange and we still see the error's. The error's are at random and no extra activity on the servers can be found. We had 2 error's yesterday (Sunday) 5:28PM and 6:56PM, and then this morning (Monday) 8:16AM, 9:34AM, and 9:47AM.

Again the permissions are not changing, the send as is not being removed.

We have started looking at AD and our Global Catalog servers, but nothin jumps outs out, we can't seem to put a fingure on whats causing this. I am very close to calling Blackberry support and paying for a support call.

If you found an answer to this, can you please post your resolution. I'm having similar issues.

[southwestcomm]

First thought - never install a BES on the Exchange server.

[gibson_hg]

It's not permissions. The permissions don't go away and return on their own. Sounds like a network issue, either yours or the carriers. If you can resend the message later odds are it's something on the network side.

It's not a mailbox full issue is it?

How many users are on the BES?

[TreeDude]

Originally Posted by southwestcomm

First thought - never install a BES on the Exchange server.

QFT. It is specifically stated in the installation documentation that Exchange should not be on the same server as the BES. If you called RIM for support they would tell you to move it off.

Is Outlook installed on the server? If so remove it. See KB10493.

[sunray73]

[QUOTE=TreeDude;1211229]QFT. It is specifically stated in the installation documentation that Exchange should not be on the same server as the BES. If you called RIM for support they would tell you to move it off.[QUOTE]

We have BlackBerry Professional Server which they specifically made for running on the Exchange server from my understanding. These are the Event ID's we are consistantly getting...

ALL FROM BLACKBERRY:
20265
20472
45058
50000
50097
50092
50090
56001
35006
35005
35004
35003
35002
35001

[gibson_hg]

The event id's are pretty much useless without the actual event assocaited with it.

What is the version of MAPI32.dll on both BES and the Exchange Server?

[TreeDude]

[QUOTE=sunray73;1211500][QUOTE=TreeDude;1211229]QFT. It is specifically stated in the installation documentation that Exchange should not be on the same server as the BES. If you called RIM for support they would tell you to move it off.

We have BlackBerry Professional Server which they specifically made for running on the Exchange server from my understanding. These are the Event ID's we are consistantly getting...

ALL FROM BLACKBERRY:
20265
20472
45058
50000
50097
50092
50090
56001
35006
35005
35004
35003
35002
35001

You may think you have BPS, but if your running 4.1.6, you have BES. BPS is only up to 4.1.4B.

[southwestcomm]

BPS was designed and certified to be installed on Exchange. An Enterprise BES is not.

[QUOTE=sunray73;1211500][QUOTE=TreeDude;1211229]QFT. It is specifically stated in the installation documentation that Exchange should not be on the same server as the BES. If you called RIM for support they would tell you to move it off.

We have BlackBerry Professional Server which they specifically made for running on the Exchange server from my understanding. These are the Event ID's we are consistantly getting...

ALL FROM BLACKBERRY:
20265
20472
45058
50000
50097
50092
50090
56001
35006
35005
35004
35003
35002
35001

[CarterTan]

It is not recommended to have more than 15users on a BES which is residing on the Exchange.

This applies to BPS as well because imagine the impact on the Exchange and BES when the workload of emails are high for the Exchange.

The BlackBerry Enterprise Server will suffer the impact as well.

I will suggest check you permissions on your Exchange as well, if it is propergated down to the Exchange mailbox store. There are incidents that the permissions were not propergated.