errors on SRM after new CABI install "Unable to render HTML for parameter"......

Document ID : KB000046133
Last Modified Date : 14/02/2018
Show Technical Document Details


after installing CABI and successfully testing the integration on the OC web page, we cannot run reports and get the following errors 

"Unable to render HTML for parameter "WKP_AlarmActivityUSers". 

"Unable to render HTML for parameter "WKP_CustomLogo" 


In the CABI customparams.log, we found a connection error as follows:

Program Files\CA\SC\CommonReporting3\Tomcat7\logs\


2016-07-19 11:19:04,630 [http-8080-3] ERROR () 5335888176 - Unable to render parameter's HTML. 

Name: WKP_CustomLogo 


Report Name:   org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Communications link failure 


This indicates that we can't connect to mysql on the SRM server from the CABI server.

Trying is to telnet to port 3306 from the CABI system to the SRM fails to remain open.




OneClick/ReportManager - Solaris 10 OS. 

CABI 3.3 SP1 windows 2008 SP2 (64-bit) 

no firewall between 

CMS port is 6400 

BO tomcat 8080 

SIA 6410 





There are various causes for these errors and one is  that the OS host file was not populated correctly or has become corrupted. 




The /etc/hosts files needs to be populated on the CABI server before installation as a prerequisite or it will fail. 

Your server host IP should be properly configured in /etc/hosts file so that there is no IP resolution problem.

You should check /etc/hosts before running the installation. The follow entries should occur once:

IP-Address Full-Qualified-Hostname Short-Hostname

For example, if the hostname is abc0008, the domain is, and the IP is, the following entries display: abc0008 localhost

Ensure there are no duplicate entries for each of the host names. Once you have configured the file, restart the network.

Important! If /etc/hosts is not configured properly, the installation fails.

When installing BusinessObjects Enterprise on multiple computers, ensure that each target computer is able to communicate over TCP/IP with the computer that is running as your Central Management Server (CMS).

Note: If you are installing BusinessObjects Enterprise in a firewall environment, you must be aware of additional configuration details.



Additional Information: