|
|
|
 |
04-24-2009, 02:34 PM
|
#1
|
|
New Member
Join Date: Apr 2009
Location: Markham, ON, Canada
Model: 8330
PIN: N/A
Carrier: TELUS Mobility
Posts: 8
|
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
|
|
|
04-24-2009, 02:47 PM
|
#2
|
|
BlackBerry Elite
Join Date: Jan 2008
Location: Massachusetts
Model: DT60
OS: 123456789
PIN: t of blood has been taken
Carrier: AT&T-US with I dee ten tee errors
Posts: 7,325
|
__________________
I had to fall
To lose it all
But in the end
It doesn't even matter
Rocking the Motion with out lotion.
|
|
Offline
|
|
|
04-28-2009, 11:51 AM
|
#3
|
|
New Member
Join Date: Apr 2009
Location: Markham, ON, Canada
Model: 8330
PIN: N/A
Carrier: TELUS Mobility
Posts: 8
|
Been there done that big time. ( I have Ex 2003 SP2)
No progress.
__________________
Rasika Wickramage
Markham, ON, Canada
|
|
Offline
|
|
|
04-28-2009, 12:43 PM
|
#4
|
|
Knows Where the Search Button Is
Join Date: Apr 2005
Model: 8700
Carrier: cingular
Posts: 32
|
Just curious Rasi if this Bell device is being activated for a new user or for an existing user receiving a new device?
|
|
Offline
|
|
|
04-28-2009, 03:16 PM
|
#5
|
|
BlackBerry Elite
Join Date: Jan 2008
Location: Massachusetts
Model: DT60
OS: 123456789
PIN: t of blood has been taken
Carrier: AT&T-US with I dee ten tee errors
Posts: 7,325
|
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.
__________________
I had to fall
To lose it all
But in the end
It doesn't even matter
Rocking the Motion with out lotion.
|
|
Offline
|
|
|
04-29-2009, 02:50 AM
|
#6
|
|
Knows Where the Search Button Is
Join Date: Mar 2008
Location: Netherlands
Model: 8900
PIN: N/A
Carrier: vodafone
Posts: 46
|
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" |
|
Offline
|
|
|
05-06-2009, 03:58 PM
|
#7
|
|
New Member
Join Date: Apr 2009
Location: Markham, ON, Canada
Model: 8330
PIN: N/A
Carrier: TELUS Mobility
Posts: 8
|
Quote:
Originally Posted by cartwfh
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
|
|
|
06-05-2009, 11:27 AM
|
#8
|
|
New Member
Join Date: Apr 2009
Location: Markham, ON, Canada
Model: 8330
PIN: N/A
Carrier: TELUS Mobility
Posts: 8
|
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
|
|
|
07-06-2009, 09:06 AM
|
#9
|
|
New Member
Join Date: Feb 2009
Location: WI
Model: 9000
PIN: N/A
Carrier: AT&T
Posts: 14
|
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
|
|
|
09-21-2009, 03:35 PM
|
#10
|
|
New Member
Join Date: Jul 2008
Model: 8830
PIN: N/A
Carrier: MTS Allstream
Posts: 11
|
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
|
|
|
|
