[kidkan]

Hello,

I have a client that bought 5 8300s through Alltel. All supposedly have the data plan. I have installed the Blackberry Professional Software (light version of BES) and it is working fine. Two of the five phones work great. The other three can recieve emails (work email acounts - exchange 2003 sp2 on SBS). They can send and recieve PINs and phone calls. They can not send, reply or forward emails. When they try it appears to be going and then they get a red x. If I open the email and scroll to the top the message says: Desktop email program unable to submit message.

I have verified that all three users are not members of any groups with admin rights, that all permissions (Send As) are set correctly, activated with BES, deleted users and phone info from BES, readded users and reactivated phones via Enterprise Activation. Still no luck. The only common thread I can find is that when setting up the phone initially they can't enter their email address. It fails to recognize it. I have created an account via the wesite and tried that also with no luck.

Any suggestions or ideas would be much appreciated.

Thanks.

[penguin3107]

You should call Alltel and verify that you have the CORRECT data plan provisioned on those lines.
It needs to be an Enterprise BlackBerry Data Plan. If it's just a personal BlackBerry data plan, it won't work with BPS.

[akg]

Wirelessly posted (BlackBerry 9000)

Either that or permissions really aren't set correctly. A problem with the 'send as' permission is usually the cause of this. If this permission does have to be reset, the BB Dispatcher service should be stopped for 20 minutes and restarted to clear the cache.

[kidkan]

Thanks for the input. I think it may be a combination of both. Yesterday all accounts showed the SendAs permisson for the bb support account. Today it's gone. Readd it and it disappears. None of these accounts are admin accounts.

However, I can't browse the net on the phone I'm currently using either.

Thanks.

[kidkan]

Got it.

Data plan was purchased but not activated. That solved half the problem. The other half came from nested groups. One of the groups these users were in was nested in the admin group. Removed it from the admin group and all is well.

Thanks again for the help.