BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 04-24-2009, 02:34 PM   #1 (permalink)
New Member
 
Join Date: Apr 2009
Location: Markham, ON, Canada
Model: 8330
PIN: N/A
Carrier: TELUS Mobility
Posts: 8
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default Desktop Email Program unable to submit message

Please Login to Remove!

I have:
BES 4.1.6 MR4 (Rollup) BUndle 105)
windows server 2003
Exchange Server 2003

PLenty of different RIM devices are working fine with my installation.
But when I add my device (8703e) with Bell Mobility, Ent activation completes successfully. Calendar, contacts and notes get synced.
Problem:
When i compose a new message from device and send it, the following error occurs:
"Desktop Email Program unable to submit message"

Here's what I have done, but didnt help.
1. Re register device with wireless carrier (from host routing table)
2. Resent service books from BES

my user account has domain admin rights in AD and I know that It could be a problem here, but there is another user on BES with domain admin rights, but he has no issues.

Any help is much apprecuated!
__________________
Rasika Wickramage
Markham, ON, Canada
Offline  
Old 04-24-2009, 02:47 PM   #2 (permalink)
BlackBerry Elite
 
knottyrope's Avatar
 
Join Date: Jan 2008
Location: Massachusetts
Model: Z30
OS: 10.2.1
PIN: t of blood has been taken
Carrier: AT&T-US with I dee ten tee errors
Posts: 6,645
Post Thanks: 264
Thanked 270 Times in 256 Posts
Default

read this
View Document
__________________
irony : many old timer posters have de-evolved into the trolls they once fought
I am on http://supportforums.blackberry.com
BES 10 running sweet for my Z30, Z10 and Q10
Offline  
Old 04-28-2009, 11:51 AM   #3 (permalink)
New Member
 
Join Date: Apr 2009
Location: Markham, ON, Canada
Model: 8330
PIN: N/A
Carrier: TELUS Mobility
Posts: 8
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Been there done that big time. ( I have Ex 2003 SP2)
No progress.
__________________
Rasika Wickramage
Markham, ON, Canada
Offline  
Old 04-28-2009, 12:43 PM   #4 (permalink)
Knows Where the Search Button Is
 
Join Date: Apr 2005
Model: 8700
Carrier: cingular
Posts: 32
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Just curious Rasi if this Bell device is being activated for a new user or for an existing user receiving a new device?
Offline  
Old 04-28-2009, 03:16 PM   #5 (permalink)
BlackBerry Elite
 
knottyrope's Avatar
 
Join Date: Jan 2008
Location: Massachusetts
Model: Z30
OS: 10.2.1
PIN: t of blood has been taken
Carrier: AT&T-US with I dee ten tee errors
Posts: 6,645
Post Thanks: 264
Thanked 270 Times in 256 Posts
Default

It might be best to remove the domain admin rights from the user and setup an admin account that does knot get email so she/he can still get the work done.

RDP and SendAs are your best friends.
__________________
irony : many old timer posters have de-evolved into the trolls they once fought
I am on http://supportforums.blackberry.com
BES 10 running sweet for my Z30, Z10 and Q10
Offline  
Old 04-29-2009, 02:50 AM   #6 (permalink)
Knows Where the Search Button Is
 
Join Date: Mar 2008
Location: Netherlands
Model: 8900
PIN: N/A
Carrier: vodafone
Posts: 46
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

just try an use the DSACLS tool again.
also check the mailbox limit on that user (close o the limit? )

tool can be found here...http://www.pocketmailsupport.com/php.../file.php?id=7


dsacls "cn=adminsdholder,cn=system,dc=DOMAIN,dc=local " /G "DOMAIN\BESadmin:CA;Send As"
__________________
support engineer for Exchange 2000/2003/2007 and BES 4.0/4.1/5.0

http://www.pocketmailsupport.com
Offline  
Old 05-06-2009, 03:58 PM   #7 (permalink)
New Member
 
Join Date: Apr 2009
Location: Markham, ON, Canada
Model: 8330
PIN: N/A
Carrier: TELUS Mobility
Posts: 8
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by cartwfh View Post
Just curious Rasi if this Bell device is being activated for a new user or for an existing user receiving a new device?
I have been using this bell device with BIS and moving him to BES.
__________________
Rasika Wickramage
Markham, ON, Canada
Offline  
Old 06-05-2009, 11:27 AM   #8 (permalink)
New Member
 
Join Date: Apr 2009
Location: Markham, ON, Canada
Model: 8330
PIN: N/A
Carrier: TELUS Mobility
Posts: 8
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default Resolved

I had to remove myself from Domain Admins.
And BESadmin has to have send as permissions properly propagated to my AD account. (and also to my AD container)
__________________
Rasika Wickramage
Markham, ON, Canada
Offline  
Old 07-06-2009, 09:06 AM   #9 (permalink)
New Member
 
Join Date: Feb 2009
Location: WI
Model: 9000
PIN: N/A
Carrier: AT&T
Posts: 14
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

I ran into this same error message using Bes 4.1.6 and found out that only a couple of our users did not get the BESADMIN "sendas" permissions propogated down correctly. My exchange admin swore up and down that the permissions were there and they were applied to the group. I spent a couple of days working with remote users and carriers, finally RIM, all to end up back where I started the investigation. I was pretty hot when he said "oh, I guess they do not have the permission, that's wierd"!

Never hurts to double check the obvious!
Offline  
Old 09-21-2009, 03:35 PM   #10 (permalink)
New Member
 
Join Date: Jul 2008
Model: 8830
PIN: N/A
Carrier: MTS Allstream
Posts: 11
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

I recently encountered the same problem. After spending the entire day searching the WWW and talking with my provider, I discovered that permissions was the issue.

The user had made himself a part of a group that removed inheritable permissions. This removed the besadmin account with the "send as" permission. Every time I added the BESADMIN account it would disappear minutes later. After removing him from the group the besadmin changes would now stick.

Problem was still not solved. I restarted the BES several times but still had the same message. I then removed the battery from the device, restarted the BES, reloaded the user, and waited for 1/2 an hour for the permissions cache to flush the bad entry.

Battery reinstalled and all is good for now.

Hope this helps
Offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





Copyright 2004-2014 BlackBerryForums.com.
The names RIM and BlackBerry are registered Trademarks of BlackBerry Inc.