 Thread Author
# 1

12-23-2009, 06:04 PM
|
| CrackBerry Newbie Device(s): 8130 (Pearl) Carrier: AT&T/Cingular | | Join Date: Dec 2009 Posts: 1 Likes Received: 0
Thanked 0 Times in 0 Posts
| |
Persistent - Desktop Email program unable to submit message _ multi-domain setup note
Issue:
Immediate red X next to (un)sent mail on a BlackBerry phone, with the note: "Desktop Email program unable to submit message"
There are several resolutions to this problem, all of them revolving around BESAdmin permissions and/or DST 2007 patching of SBS 2003.
I found another caveat I'd like to share my experience with (and it may seem dumb, but here goes):
We are a small business and have a single SBS 2003 managing DC, Exchange, and now BES. After following several guides, all following RIM KB 04707 information, among others, the issue was which domain I was using the do Enterprise Activiation on the phone.
In order of ownership / setup:
domain1.com
domain2.com
We use and our user setup sends / receives by default from First.Last@domain2.com.
The server is setup as such:
server.domain1.local
In attempting to do Enterprise Activation via First.Last@domain2.com, everything sync'ed-down, but the phone could not send or up-sync anything.
Resolution entailed doing a "Erase all data and disable phone" and doing Enterprise Activation with First@domain1.com ... seeing how this is how MAPI is setup on our client mail, though this is our secondary send/receive addressing.
I know this has to do with other technical setup issues and aspects with SBS & DC's, and there might be an AD or DC work-around ... though I'm thinking it has to do primarily with MAPI and initial domain setup configuration / parameters.
If anyone has any technical questions, feel free, but do attempt to try the above mentioned KB first, as it seems to fix everyone's issues. And I'm a proponent of not just RTFM, but also following step-by-step, to the letter, print it off, check off every crossed-t and dotted-i.
If this post belongs somewhere else, feel free to move it or flag it and remove it ... whatever ... thought I'd share my abstract experience with the community. (Now that it is working seamlessly ... my boss LOVES it ... he's a crackberry addict, I'm the abuser.)
|