[dpenley]

I have a bunch of new users, all with AT&T 8310s who can receive but not send. Whenever someone tries to send I get the following errors in the event log of the BES server.

Any ideas or assistance would be greatly appreciated!!!

Exchange 2003 SP2

BES 4.0

Event Type: Warning
Event Source: BlackBerry Messaging Agent BLACKBERRY Agent 1
Event Category: None
Event ID: 20000
Date: 6/12/2008
Time: 4:15:35 PM
User: N/A
Computer: BLACKBERRY
Description:
{[email protected]} Send() failed: SUCCESS, Tag=464382

Event Type: Warning
Event Source: BlackBerry Messaging Agent BLACKBERRY Agent 1
Event Category: None
Event ID: 20265
Date: 6/12/2008
Time: 4:15:35 PM
User: N/A
Computer: BLACKBERRY
Description:
{[email protected]} MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80070005) failed.


Event Type: Warning
Event Source: BlackBerry Messaging Agent BLACKBERRY Agent 1
Event Category: None
Event ID: 20265
Date: 6/12/2008
Time: 4:15:35 PM
User: N/A
Computer: BLACKBERRY
Description:
{[email protected]} MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80070005) failed.



These messages are in the MAGT log

[40000] (06/12 16:15:17):{0x176C} [BIPP] Received datagram, Tag=464381
[40700] (06/12 16:15:17):{0x1038} {[email protected]} Receiving packet from device, size=49, TransactionId=-277209286, Tag=464381, content type=CMIME, cmd=0x3
[40698] (06/12 16:15:17):{0x1038} {[email protected]} Receiving OTAFM request from device, Tag=464381, TransactionId=-277209286
[40572] (06/12 16:15:17):{0x1038} {[email protected]} Receiving MESSAGE_STATUS_UPDATE request from device, Tag=464381, TransactionId=-277209286, RefId=-915210045, MsgStatus=1
[40182] (06/12 16:15:17):{0x1038} {[email protected]} MAPIMailbox::RefIDtoEntryID - Found RefId=-915210045.
[40699] (06/12 16:15:17):{0x1038} {[email protected]} OTAFM request from device processed
[40279] (06/12 16:15:17):{0x1038} {[email protected]} SubmitToRelaySendQ, Tag=464381
[40000] (06/12 16:15:17):{0x4A4} [BIPP] Send status DATA_ACCEPTED, Tag=464381
[40702] (06/12 16:15:34):{0xADC} {[email protected]} Starting message rescan
[40703] (06/12 16:15:34):{0xADC} {[email protected]} Message rescan completed
[40000] (06/12 16:15:35):{0x176C} [BIPP] Received datagram, Tag=464382
[40700] (06/12 16:15:35):{0x16DC} {[email protected]} Receiving packet from device, size=147, TransactionId=-277209285, Tag=464382, content type=CMIME, cmd=0x3
[30112] (06/12 16:15:35):{0x16DC} {[email protected]} Receiving message from device, RefId=1514080901, Tag=464382, TransactionId=-277209285
[40291] (06/12 16:15:35):{0x16DC} {[email protected]} Refers to original message, RefId=-915210045
[40182] (06/12 16:15:35):{0x16DC} {[email protected]} MAPIMailbox::RefIDtoEntryID - Found RefId=-915210045.
[20265] (06/12 16:15:35):{0x16DC} {[email protected]} MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80070005) failed.
[40182] (06/12 16:15:35):{0x16DC} {[email protected]} MAPIMailbox::RefIDtoEntryID - Found RefId=-915210045.
[20265] (06/12 16:15:35):{0x16DC} {[email protected]} MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80070005) failed.
[20000] (06/12 16:15:35):{0x16DC} {[email protected]} Send() failed: SUCCESS, Tag=464382
[40277] (06/12 16:15:35):{0x16DC} {[email protected]} Sending message error to device for message 1514080901
[40583] (06/12 16:15:35):{0x16DC} {[email protected]} Sending packet to device, Size=47, Tag=421980, TransactionId=-934189119
[40279] (06/12 16:15:35):{0x16DC} {[email protected]} SubmitToRelaySendQ, Tag=421980
[40279] (06/12 16:15:35):{0x16DC} {[email protected]} SubmitToRelaySendQ, Tag=464382
[40000] (06/12 16:15:35):{0x4A4} [BIPP] Send data, Tag=421980
[40000] (06/12 16:15:35):{0x4A4} [BIPP] Send status DATA_ACCEPTED, Tag=464382

DISP logs show the following

[30222] (06/12 16:15:17):{0x1424} {[email protected]} MFH: contentType=CMIME, sizeOTA=58, sizeOTW=13, TransactionId=-277209286, Tag=372089
[30308] (06/12 16:15:17):{0x1424} [BIPP] {[email protected]} Forwarding data to BES Agent, size=49, intTag=464381, Tag=372089
[30311] (06/12 16:15:17):{0x1428} {[email protected]} Forwarding status to relay, intTag=464381, Tag=372089, Status=1
[30222] (06/12 16:15:35):{0x1458} {[email protected]} MFH: contentType=CMIME, sizeOTA=154, sizeOTW=111, TransactionId=-277209285, Tag=372091
[30308] (06/12 16:15:35):{0x1458} [BIPP] {[email protected]} Forwarding data to BES Agent, size=147, intTag=464382, Tag=372091
[30222] (06/12 16:15:35):{0x145C} {[email protected]} MTH: contentType=CMIME, sizeOTA=58, sizeOTW=13, TransactionId=-934189119, Tag=150929
[30310] (06/12 16:15:35):{0x145C} {[email protected]} Forwarding internal data to device, contentType=CMIME, routing=S52834853, device=246F29B0, size=95, cmd=0x3, ack=0, TransactionId=-934189119, intTag=421980, Tag=150929, Submit=1
[30311] (06/12 16:15:35):{0x1460} {[email protected]} Forwarding status to relay, intTag=464382, Tag=372091, Status=1
[30368] (06/12 16:15:36):{0x1464} {[email protected]} Packet has been delivered to device, Tag=150929
[30388] (06/12 16:15:36):{0x1464} [BIPP] {[email protected]} Forwarding status to BES Agent, intTag=421980, extTag=150929

Exchange 2003 SP2

BES 4.0

[acnst]

The "Send as" permissions are not set correctly. Use the search and you will find instructions how to solve the issue.

[dpenley]

Originally Posted by acnst

The "Send as" permissions are not set correctly. Use the search and you will find instructions how to solve the issue.

I tried everything I saw regarding the "Send As" problem, yet still the users can not send. They get a "Unlisted Message Error" on the handset.

The besadmin definitely has Send As permissions on the organization and in AD on the Users folder, and all of the BB users are in that folder.

I'm at a loss here. Is there a way I can test this on my own? I have VPN access to their servers but no Blackberry devices. They're all remote users so I have to email them every time I make a change to test it and I would like to be able to do it on my own. Thanks for the help!!

[knottyrope]

Send as permission was set in exchange system manager if I remember right.

Also it can take a lil time to propagate.

[dpenley]

as it turns out, there was a provisioning issue that AT&T is now in the process of manually fixing. IT WASN'T MY FAULT!!!!!! YYYAAAAAYYYYYYY

[knottyrope]

I hope its true, but did you check permissions in ESM?