Known Issues › Failed to Open Connection

Failed to Open Connection

Symptom:

When I run a report in InfoView, one or more of the following messages appear:

Failed to open Connection

Incorrect logon parameters

Incomplete database logon information

Solution:

The report database log-on information is incomplete or the CAFPage is not configured properly. To resolve these problems, perform the following steps:

1. Identify the database that the universe uses.
2. Test the universe connection to verify that the universe is responding correctly.
3. (Oracle database only) Verify that the CA Business Intelligence system has the Oracle client installed properly and that the TNS entry matches the one provided in the universe.

   The following TNS entry is an example:

   orcl =
     (DESCRIPTION =
       (ADDRESS_LIST =
         (ADDRESS = (PROTOCOL = TCP)(HOST = abcd-tm-114)(PORT = 1521))
       )
       (CONNECT_DATA =
         (SERVICE_NAME = orcl)
   

4. (SQL Server database only) Verify that the oledb.sbo file is configured properly. Use the OLE DB network layer to import the BIAR file into the Business Objects enterprise.
5. Verify that the setReportType.jsp is edited correctly with the BusinessObject credentials. Verify that the database.properties file is using the CA Configuration Automation r12.8 database that you want to use for reporting. After you modify the database.properties file, restart the Tomcat server or the web application server of the BusinessObjects system.
6. If the CAFPage is not working, browse to the log file in the logs folder of the web application server of BusinessObjects, for example:

   C:\Program Files\Business Objects\Tomcat55\logs\CAFApp.log
   

7. Review the log. If the log shows the following error message, the Oracle JDBC *.jar file is not found in the classpath of the system:

   If the error is ClassNotFoundException: OracleJDBCDriver not found
   

   Set the path of the Oracle JDBC driver in the CLASSPATH variable of the system.

Not Enough Memory for Operation

Symptom:

When the database does not have sufficient memory for operation, the following system problems can occur:

• The schedule hangs in the Pending state.
• The view on demand hangs while loading.

Solution:

Correct one or more of the following problems:

• The system that is running the report is of low configuration.
• The network of the system does not have a good response.
• (Oracle) The TNS name is not recognized. Verify that the TNSlistener is running on the database server and that it is responding.
• The temp folder or the cache is full with the servers that are responsible for the scheduling process.
• The WebiProcessing server is shut down.
• CA Business Intelligence is not installed correctly.

Use the following recommended settings or the minimum requirements to avoid memory issues:

• When the database is large, select only a few servers for your report criteria.
• Verify the space on the local drives on the computer. Increase the space on these drives.
• Increase the RAM size on the computer. A minimum of 2 GB of RAM is required.
• Increase the memory of Java Tomcat as follows:
  1. Select Start, Programs, Tomcat, Configuration, Java tab.
  2. Set the Initial size to 512, and set the Maximum size to 1024.
  3. Restart Tomcat and verify that the correct number of pages are in the report after you refresh the report.
• On the server, review and adjust the page/file size as follows:

  1. Select My Computer Properties, Advanced tab, Performance Settings.

  The Performance Options dialog appears.

  2. Select the Advanced tab and click the Virtual Memory Change button.

  3. Adjust the Paging file size (initial and maximum) for your C and D drives.

• Delete files from the windows temp directory as follows:

  1. Select Start, run.

  2. Enter %temp% and click OK.

  Note: If you are exporting or saving a large report on the local computer, review the size of the temp directory.

• Change the maximum cache size as follows:

  1. Open the properties for the Crystal Report Cache Server and stop the server.

  1. Add the -deleteCache option to the end of the command line.

  2. Change the maximum cache size from 256000 to 768000.

  3. Start the server.

• Delete or move the contents from the following cache folder:

  <Install Dir>\Program Files\Business Objects\BusinessObjects Enterprise 12.0\Data\
  

Note: For more troubleshooting tips for various types of memory errors, see the www.sdn.sap.com website.