[val7250]

Hello,

I have a few people who are on a different domain and different e-mail domain than the rest of our blackberry users on our bes server. They cannot send messages they keep getting a red X whenever they try to send messages. I ran the setsendaspermission on the server and get a few odd errors, that I think may be the cause.

[30000] (03/12 09:37:46.726):{0x884} [DIAG] EVENT=Register_thread, THREADID=0x884, THREADNAME="TimerThread"
[40000] (03/12 09:37:46.726):{0x884} [DEBUG] EVENTMSG="TimerThread thread started"
[30000] (03/12 09:37:46.804):{0x1A04} Set the Send As Permission in Active Directory tool Version 4.1.2.6
[30000] (03/12 09:37:46.804):{0x1A04} Copyright (c) Research In Motion, Ltd. 2000-2007. All rights reserved.
[30000] (03/12 09:37:46.804):{0x1A04} Modification date: Feb 8 2007
[20000] (03/12 09:37:46.804):{0x1A04} SMTP address:
[40000] (03/12 09:37:46.820):{0x1A04} DSRoot :DC=val,DC=vlss,DC=local:
[40000] (03/12 09:37:46.820):{0x1A04} DomainContainer :DC=val,DC=vlss,DC=local:
[40000] (03/12 09:37:46.820):{0x1A04} LDAPQuery :<LDAP://DC=val,DC=vlss,DC=local>;(&(objectCategory=person) (proxyAddresses=smtp:KroegerD@peppromotions.com)); adspath;subtree:
[40000] (03/12 09:37:46.835):{0x1A04} GetSize :0:
[20000] (03/12 09:37:46.835):{0x1A04} FAIL
[10000] (03/12 09:37:46.835):{0x1A04} SetSendAsPermission(): Unable to find user
[30000] (03/12 09:37:46.835):{0x1A04} Done.
[30000] (03/12 09:38:28.023):{0x16EC} Current Date: 2007/03/12
[30000] (03/12 09:38:28.023):{0x16EC} [DIAG] EVENT=Thread_report, THREADID=0x16EC, THREADNAME="DebugLogger"
[30000] (03/12 09:38:28.023):{0x16EC} [ENV] Current Process: C:\TEMP\SetSendAsPermission.exe
[30000] (03/12 09:38:28.023):{0x16EC} [ENV] Current Process logged on as: VAL\besadmin, Start Time: Mar 12 2007 09:38:28, Uptime (seconds): 0
[30000] (03/12 09:38:28.023):{0x16EC} [ENV] Current Process id: 7344
[30000] (03/12 09:38:28.023):{0x16EC} [ENV] Computer Host Name: VAL-07-CORP-01, OS Version: 5.2, Build number 3790, ServicePack Major 1, ServicePack Minor 0
[30000] (03/12 09:38:28.023):{0x16EC} [ENV] Processor Identifier: x86 Family 15 Model 4 Stepping 3
[30000] (03/12 09:38:28.023):{0x16EC} [ENV] Processor Vendor Identifier: GenuineIntel
[30000] (03/12 09:38:28.023):{0x16EC} [ENV] Processor Name String: Intel(R) Xeon(TM) CPU 3.40GHz
[30000] (03/12 09:38:28.023):{0x16EC} [ENV] Number of Processors: 4
[30000] (03/12 09:38:28.023):{0x16EC} [ENV] 53 percent of memory in use.
[30000] (03/12 09:38:28.023):{0x16EC} [ENV] Total size of physical memory: 2096400 KB
[30000] (03/12 09:38:28.023):{0x16EC} [ENV] Size of physical memory available: 976088 KB
[30000] (03/12 09:38:28.023):{0x16EC} [ENV] Size of the committed memory limit: 4038612 KB
[30000] (03/12 09:38:28.023):{0x16EC} [ENV] Size of available memory to commit: 2949124 KB
[30000] (03/12 09:38:28.023):{0x16EC} [ENV] Total size of the user mode portion of the virtual address space of the BES process: 2097024 KB
[30000] (03/12 09:38:28.023):{0x16EC} [ENV] Size of unreserved and uncommitted memory in the user mode portion of the virtual address space of the BES process: 2067188 KB
[30000] (03/12 09:38:28.023):{0x16EC} [ENV] Total HD bytes: 21237672448, Total free bytes = 9985222144
[30000] (03/12 09:38:28.023):{0x16EC} [ENV] System up time: 4 days 20 hrs 29 mins 17 secs
[30000] (03/12 09:38:28.023):{0x16EC} [ENV] Local Time Zone: Eastern Daylight Time (GMT-05:00)
[30000] (03/12 09:38:28.023):{0x16EC} [ENV] TCP/IP provider (Winsock) File Version: 5.2.3790.0 (C:\WINDOWS\System32\wsock32.dll)
[30000] (03/12 09:38:28.023):{0x16EC} [ENV] Unable to provide HostName
[30000] (03/12 09:38:28.039):{0x16EC} [ENV] Winsock2 file: Network Location Awareness (NLA) Namespace, Version: 5.2.3790.1830 (C:\WINDOWS\System32\mswsock.dll)
[30000] (03/12 09:38:28.039):{0x16EC} [ENV] Microsoft XML Parser 4.0: C:\WINDOWS\system32\msxml4.dll, Version: 4.20.9841.0

Any advice would be appreciated since it's a VIP. I tried calling RIM and they said they are experiencing high call volumes and disconnected me.

[ama.harper]

Here is what we found when we had a similar issue. Maybe this will be of help.

We gave the users send as permissions however we could not do it for our IS group. We found that the all members of our IS department were members of a group 'IS' and that group was a member of a protected AD group 'Print Operators'. We removed the 'IS' group from the 'Print Operators' group then added 'send as' permissions. After it replicated out it worked.

Here were the groups we found as protected:

xxx8226; Enterprise Admins
xxx8226; Schema Admins
xxx8226; Domain Admins
xxx8226; Administrators
xxx8226; Administrators
xxx8226; Account Operators
xxx8226; Server Operators
xxx8226; Print Operators
xxx8226; Backup Operators
xxx8226; Domain Admins
xxx8226; Schema Admins
xxx8226; Enterprise Admins
xxx8226; Cert Publishers

Additionally, the following users are considered protected:

xxx8226; Administrator
xxx8226; Krbtgt

Additionally, user accounts or groups that have been delegated the following roles in Exchange are considered protected:

xxx8226; Exchange View Only Administrator
xxx8226; Exchange Administrator
xxx8226; Exchange Full Administrator

[Davidland]

I have the permissions holding for besadmin for send as and recieve, everything was working then it stopped. Rebooted the server and i can recieve again but the red x is back. Please help i can't take much more

I am not sure how to use the dsacls tool and that might fix my problem anyone

[val7250]

thanks, I ended up logging in as bes admin on my workstation and setting up the users e-mail profile and messed around with the send as permissions until it allowed me to send a message.

[mischief007]

You also have to make sure to stop the BlackBerry Router for 20 minutes in order for the cached permissions to clear out.

[ladydi]

Send as permissions will not apply to any account that is part of a "built-in" group. We discovered this recently as well.

[theitdude]

Mine stopped working too - actually it NEVER worked. I've changed the dacls and the BES service account is still holding the Send AS and Receive As permissions for Admins.

I'm not impressed with BES
If my Exchange Org was this flakey, I'd kill myself.

[ladydi]

its not flakey, its "sophisticated" ;)

Just don't put your admins in any of the built-in account groups.

[minx]

I read someone post: "be patient".

I had the same problem, I applied the patch for exchange Monday night, register cdo and reboot both servers without modified the permission. I tested to send email was OK.
Wednesday afternoon one of the users couldn't send email, yesterday nobody couldn't send email
After I changed the permission for each user and ran dacls, wait for 30 minutes, turn back on the router service, I still couldn't send email. I did that many times (change the permission etc), finally I tried on one of regular users, and it works!
Took almost 5 hours to make my device works, the other admins (1 hour and the other one around 4.30h)
So again, just be patient and try with other user's device.