
Workaround: When you type the user's display name, do not include the apostrophe.
If you configure a BlackBerry Administration Service pool and you restart multiple BlackBerry Administration Service instances
at a time, the BlackBerry Administration Service instances might not identify a singleton and errors might occur. (DT 613238)
Workaround: Start BlackBerry Administration Service instances one at a time.
In certain circumstances, if you push a software configuration out to a large number of users (for example, 2000), the BlackBerry
Administration Service uses more than its maximum of 670 threads and stops unexpectedly with an out of memory error. (DT
608647)
In certain circumstances, when you reconcile IT policies for large groups (for example, 30,000 users), the reconciliation process
might stop unexpectedly. (DT 605175)
When you access the BlackBerry Administration Service and the BlackBerry Monitoring Service in two different tabs in the
same Windows® Internet Explorer® window, the BlackBerry Administration Service times out. (DT 605059)
Workaround: Access the BlackBerry Administration Service and the BlackBerry Monitoring Service in two different windows.
When you enable Microsoft Active Directory authentication for a large group of users, you must configure each user account
individually, which might take a long time. (DT 602402)
Workaround: Use the BlackBerry® Enterprise Server Resource Kit to configure large groups of user accounts. For more
information, see the documentation for the BlackBerry Enterprise Server Resource Kit.
If you install the BlackBerry Enterprise Server in a failover configuration, install the BlackBerry database notification system,
and activate a user account, reconciliation might not work and the following messages might appear in the BlackBerry
Administration Service - Application Server log file:
(04/16 15:45:19:119):{WorkManager(2)-143} [org.hibernate.util.JDBCExceptionReporter] [WARN] SQL Error: 8162, SQLState:
S0002
(04/16 15:45:19:119):{WorkManager(2)-143} [org.hibernate.util.JDBCExceptionReporter] [ERROR] The formal parameter
"@IdIntCustom" was not declared as an OUTPUT parameter, but the actual parameter passed in requested output.
(04/16 15:45:19:135):{WorkManager(2)-143} [com.rim.bes.bas.BASExceptionStackInterceptor] [WARN] [BBAS-2007]
{u=SystemUser, t=6584} Caught unhandled RuntimeException in org.jboss.ejb3.EJBContainerInvocation method
clearReconciledSoftwareConfigurationForUserLocal - org.hibernate.exception.SQLGrammarException: could not delete:
[com.rim.bes.bas.devicemanager.entity.HandheldConfigEntity#1] (DT 602227)
Workaround: Remove the BlackBerry database notification system. You might need to wait 24 hours for failed reconciliation
tasks to be removed from the BlackBerry Configuration Database.
Release Notes
BlackBerry Administration Service known issues
26
Comentarios a estos manuales