"Page cannot be displayed" when attempting to log into the BlackBerry Administration Service console and the BAS-AS and BAS-NCC processes does not go beyond 75K to 80K of memory usage

• BlackBerry® Enterprise Server 5.0
• Microsoft® SQL Server® 2008 Standard Edition and R2
• Java® 1.6.0 Update 29 and higher

Page cannot be displayed when attempting to access the BlackBerry® Administration Service console. In addition, the BAS-AS and BAS-NCC processes does not increase beyond 75K to 80K of memory usage.

Similar log lines are shown within BBAS-AS:

(07/20 17:34:24:665):{Timer-10} [com.rim.bes.bas.singletondeploymentbarrier.SingletonDeploymentBarrierManagerUtilities] [WARN] [BBAS-2069] {unknown} heartbeatTimerEvent CLUSTER:   caught exception while writing heartbeat, com.rim.bes.bas.util.BASCouldNotCompleteRequestRollbackException: Caught unhandled RuntimeException in org.jboss.ejb3.EJBContainerInvocation method heartbeatInNewTransactionLocal - org.hibernate.exception.GenericJDBCException: could not execute query
(07/20 17:34:31:821):{Stop Thread} [STDERR] [ERROR] Could not obtain a connection to the database. Will keep trying for another 285235ms
(07/20 17:34:31:821):{Stop Thread} [STDOUT] [INFO] Could not obtain a connection to the database. Will keep trying for another 285235ms
(07/20 17:34:35:540):{Timer-13} [org.hibernate.util.JDBCExceptionReporter] [WARN] SQL Error: 0, SQLState: null
(07/20 17:34:35:540):{Timer-13} [org.hibernate.util.JDBCExceptionReporter] [ERROR] The connection is closed.
(07/20 17:34:35:540):{Timer-13} [com.rim.bes.bas.BASExceptionStackInterceptor] [WARN] [BBAS-2007] {u=SystemUser, t=1187716} Caught unhandled RuntimeException in org.jboss.ejb3.EJBContainerInvocation method findTraitLocal - could not execute query

In addition, new BAS-AS and  BAS-NCC logs are not being generated even after restarting those services.

For Microsoft SQL Server 2008 Standard Edition, apply Service Pack 3 followed by Cumulative Update Package 4 or higher. For Microsoft SQL server 2008 R2, apply Service Pack 1 follow by Cumulative Update Package 6 or higher.

Note: The Microsoft SQL server must be restarted to complete the update.

Disable Force Encryption on the SQL server.

Steps:

1. On the server where SQL is installed, launch  SQL Server Configuration Manager.
2. Expand SQL Server Network Configuration.
3. Right click on Protocols for MSSQLSERVER and select  Properties.
4. Under the Flag tab, set  Force Encryption to No.
5. Hit Apply and OK.

Note: This is a global setting and either the SQL services has to be restarted or the SQL server has to be rebooted for this change to take effect.

For more information regarding this see http://blogs.msdn.com/b/jdbcteam/archive/2012/01/19/patch-available-for-sql-server-and-java-6-update-30.aspx