Known Issues › CAFApp.war Deployment Fails

CAFApp.war Deployment Fails

Symptom:

The CAFApp.war deployment fails with an authentication error.

Solution:

This problem is due to not setting the proper business objects credentials in the setReportType.jsp file. Deploy the Client Access Framework (CAF) page WAR files.

Error on CA Configuration Automation Upgrade with Oracle Database

Symptom:

The following error appears during an CA Configuration Automation upgrade on an Oracle database:

Error: A tablespace with name “acmdata” not found, use an existing tablespace name

Solution:

If the CA Configuration Automation Server is using an Oracle database for its backend, and the Data Tablespace name and Index Tablespace name used are different from “acmdata” or “acmindex”, the current upgrade installer does not identify the data and index correctly.

Execute the installer from the command line with the correct data and index names as follows:

installserver.exe -DDATATSNAME=acmcmdbdata -DINDEXTSNAME=acmcmdbindex

Export of Relationship with Unmanaged Server Causes Error in GRLoader

Symptom:

The following error appears when exporting a relationship with the Include servers not listed in Server Table option enabled on the CA Business Intelligence interface:

Provider CI not found

Solution:

Disable the option “Include servers not listed in Server Table” to filter out the export of relationships associated with servers that are not in the CA Configuration Automation Server table. Also, you can discover the server by adding it to the CA Configuration Automation Server table.

Extracting Virtual Machine and Provider Relationships Causes Error in XML Files

Symptom:

The Provider CI not found error appears in the XML error file (<SpecifiedFileName_err.XML) and GRLoader.log file when the integration attempts to extract a relationship between a virtual machine and its provider (such as VMware ESX Host).

Solution:

• Verify that CA Configuration Automation discovered the VMware ESX Host.
• Verify that you added the VMware ESX Host, the VMware vCenter Server credentials, or both, to the credential vault within CA Configuration Automation. After you add the credentials, run Network Discovery again using a Network Scan that includes the Softagent (for example, Pingsweep Scan with Softagent).