Release Notes › Known Issues › Miscellaneous

Miscellaneous

The following are the miscellaneous known issues.

CA User Activity Reporting Module Is Sometimes Non-Responsive

Symptom:

Sometimes CA User Activity Reporting Module is non-responsive. That is, the user interface does not respond to user requests and internal requests from the agent to agent manager stop. However, log collection continues.

Solution:

Use the following procedure to stop the iGateway process and restart it:

1. Log on to the non-responsive CA User Activity Reporting Module server through ssh as the caelmadmin user.
2. Switch users to the root account with the following command and provide the root password:

   su -
   

3. Navigate to the $IGW_LOC directory.

   By default, iGateway resides in the directory, /opt/CA/SharedComponents/iTechnology.

4. Stop the iGateway process with the following command:

   ./S99igateway stop
   

5. Start the iGateway process with the following command:

   ./S99igateway start
   

Events Export to PostgreSQL Fails with Fatal Error

Symptom:

When you export events to PostgreSQL using the DBExport utility, the following error is displayed in the self-monitoring events:

FATAL: sorry, too many clients already

Solution:

To resolve the issue, restart the PostgreSQL service.

Custom ODBC Database Connection Fails

Symptom:

A custom connection set up to allow you to query an ODBC database fails.

Solution:

This issue occurs when ODBC Schema names are entered in lower-case letters during configuration. Make sure that when you configure an ODBC connection in the Report Service interface, you enter any schema names in all capital letters.

Display Time is Wrong

Symptom:

Display time is wrong after CA User Activity Reporting Module server is provisioned using the Virtual Appliance.

Solution:

Use the following workaround to resolve this issue:

1. Stop the iGateway.
2. Set the display time manually.
3. Restart the iGateway.

Event Collection Profiles Fail to Appear on Upgrade

Symptom:

After you upgrade to the 12.5.02 release from a previous release, subscription Event Collection Profiles fail to appear in the user interface.

Solution:

This issue occurs when the Content upgrade module is not the final module installed. To resolve the issue, repeat the upgrade process with only the Content module selected. When the content-only upgrade is complete, the Event Collection profiles appear properly.

More information:

Upgrading to CA User Activity Reporting Module Version 12.5 through Subscription

Upgrading to CA User Activity Reporting Module Version 12.5 through Offline Subscription

High Contrast Settings for Monitor

Symptom:

In Windows, the only supported high contrast setting is High Contrast Black; the other three high contrast options are not supported. High contrast options include High Contrast #1, High Contrast #2, High Contrast Black, and High Contrast White.

Solution:

Select the High Contrast Black setting, when a high contrast setting is needed. To set this option, select Display from the Control Panel. This accessibility option is set on the Display Properties dialog, Appearance tab, Color scheme drop-down list.

iGateway Continuously Stopping and Restarting

Symptom:

The CA User Activity Reporting Module interface occasionally stops responding during operations. Checking the CA User Activity Reporting Module server reveals that the iGateway process is stopping and restarting but failing to stay up. Use the following process to check the iGateway process:

1. Access a command prompt on the CA User Activity Reporting Module server.
2. Log in with the caelmadmin account credentials.
3. Switch users to the root account with the following command:

   su - root
   

4. Use the following command to verify that the iGateway process is running:

   ps -ef | grep igateway
   

   The operating system returns the iGateway process information and a list of processes running under iGateway.

Solution:

Use the following workaround to resolve the problem:

1. Go to $IGW_LOC (/opt/CA/SharedComponents/iTechnology), and locate the following file:

   saf_epSIM.*
   

   There are multiple versions, numbered sequentially, for example, saf_epSIM.1, saf_epSIM.2, saf_epSIM.3, and so on.

2. Rename the lowest-numbered file and save it in another location for transmission to CA Technologies support.
3. If iGateway does not automatically restart, restart it:
   1. Log in as the root user.
   2. Access a command prompt and enter the following command:

      /opt/CA/SharedComponents/iTechnology/S99igateway start
      

Keyed Lists Configured Locally Fail to Appear After Upgrade

Symptom:

After upgrading to CA User Activity Reporting Module version r12.5, when you examine the available Keyed Value list under Administration > Library > Keyed Lists > Subscription, some Keyed Values no longer appear.

Solution:

In CA User Activity Reporting Module version r12.5, Keyed Value lists have been moved from Services to Library, under Administration. If you had previously specified a Keyed Value as local to a specific server, rather than global for your entire CA User Activity Reporting Module environment, that Keyed Value is not retained after upgrade to version r12.5.

To avoid losing Keyed Values, before upgrading to version r12.5, set all Keyed Values to global configuration.

Max Disk Space for Virtual CA User Activity Reporting Module Is Too Small

Symptom:

Not able to create a virtual machine with an allocated disk space of 512 GB in VMware ESX Server v3.5. My virtual CA User Activity Reporting Module server needs more than the 256 GB maximum to handle event volume.

Solution:

VMWare ESX Server uses a default Block Size of 1 MB, and calculates the maximum disk space using this value. When the block size is set to 1 MB, the maximum disk space defaults to 256 GB. If you want to configure more than 256 GB of virtual disk space, you can increase the default block size.

To create a larger virtual disk

1. Access the service console on the VMware ESX Server.
2. Increase the Block Size to 2 MB with the following command:

   vmkfstools --createfs vmfs3 --blocksize 2M vmhba0:0:0:3
   

   In this command, the value 2M means 512 GB (2 x 256).

3. Restart the VMware ESX Server.
4. Create a new virtual machine with disk space set to 512 GB.

Out of Memory Error on Machines with Low Memory

Symptom:

The download of a subscription update to a computer with less than the recommended 8 GB of memory fails with a Java out of memory error.

Solution:

If you install CA User Activity Reporting Module on hardware with less than the recommended 8 GB of memory, change the JVM heap size setting by editing the caelm-java.group file.

To change the JVM heap size setting

1. Log on to the CA User Activity Reporting Module server as caelmadmin.
2. Navigate to the iGateway folder.
3. Open the caelm-java.group file and locate the the JVM settings section.
4. Add the new line, as shown in the following illustration in bold:

     <JVMSettings>
   

                   <loadjvm>true</loadjvm>
   

                   <javahome>/usr/java/latest/jre</javahome>
   

                   <Properties name="java.endorsed.dirs=/opt/CA/SharedComponents/iTechnology/endorsed">
   

                           <system-properties>java.endorsed.dirs=/opt/CA/SharedComponents/iTechnology/endorsed</system-properties>
   

                   </Properties>
   

           <Properties name="maxmemory"><jvm-property>-Xmx1250M</jvm-property></Properties>
   

           </JVMSettings>
   

5. Save and close the caelm-java.group file

Important! Setting the JVM heap size can cause problems when using the Export to PDF option with large data sets. Thus, this option is best used on only small computers, which run with less than the recommended RAM and processing power.

Refreshing Browser Logs User Out of CA User Activity Reporting Module

Symptom:

Refreshing your browser while logged in to CA User Activity Reporting Module ends your session, logging you out.

Solution:

CA User Activity Reporting Module does not support browser refresh because of Flex limitations. Avoid refreshing your browser.

EE_POZERROR Repository Error Appears on Login When Using Remote EEM

Symptom:

When you open the CA User Activity Reporting Module interface in an environment using a remote EEM server, the interface may fail to display properly. Instead an "EE_POZERROR Repository Error" appears.

Solution:

Close and reopen the browser to resolve the issue.

Screen Captures May Show CA User Activity Reporting Module Title

Screen captures inlcuded in the 12.5.02 release documentation may show the CA Enterprise Log Manager title, rather the the CA User Activity Reporting Module title. This change is purely cosmetic. Navigation and functionality are unchanged.

Service or Explorer Interface Error May Occur After iGateway Restart

Symptom:

If you click on an object in the CA User Activity Reporting Module interface services or explorer trees immediately after an iGateway restart, you may see an error message reading "Network error on receive" rather than the requested content.

Solution:

This error occurs if you attempt to access one of the specified objects while they are still being reloaded after the iGateway restart. Wait five minutes to allow the reload to finish and click the services or explorer item you want.

Uploads and Imports Fail with any Non-IE Browser

Symptom:

When you browse to CA User Activity Reporting Module with Mozilla Firefox, Safari, or Chrome, you can perform most CA User Activity Reporting Module tasks successfully. However, any upload or import tasks fail when using any of these browsers. Examples follow:

• Importing a query definition fails with an "IO Error: Request Failure" message.
• Uploading a CSV file with the bulk connector deployment wizard fails, despite the message, "Uploading file."

Solution:

Browse to CA User Activity Reporting Module with Microsoft Internet Explorer when you want to upload or import files.

User Interface Unexpectedly Fails to Display Properly on Installation with Remote EEM

Symptom:

When installing CA User Activity Reporting Module with a remote EEM server, the user interface occasionally fails to display properly on initial login. Reviewing the iGateway log files reveals that the agentmanager, calmreporter, subscclient and subscproxy services have not started.

You may see log file syntax similar to this:

[1087523728] 09/23/09 20:35:32 ERROR :: Certificate::loadp12 : etpki_file_to_p12 failed [ errorcode : -1 ] 

[1087523728] 09/23/09 20:35:32 ERROR :: Certificate::loadp12 : etpki_file_to_p12 failed [ errorcode : -1 ] 

[1087523728] 09/23/09 20:35:32 ERROR :: Certificate::loadp12 : etpki_file_to_p12 failed [ errorcode : -1 ] 

[1087527824] 09/23/09 17:00:07 ERROR :: OutProcessSponsorManager::stopSponsorGroup : terminating safetynet process for SponsorGroup [ caelm-msgbroker ] didn't respond OK for the termination call 

[1087527824] 09/23/09 17:00:07 ERROR :: OutProcessSponsorManager::stopSponsorGroup : terminating safetynet process for SponsorGroup [ caelm-oaserver ] didn't reaspond OK for the termination call 

[1087527824] 09/23/09 17:00:07 ERROR :: OutProcessSponsorManager::stopSponsorGroup : terminating safetynet process for SponsorGroup [ caelm-sapicollector ] didn't reaspond OK for the termination call 

[1087527824] 09/23/09 17:07:46 ERROR :: OutProcessSponsorManager::start : SponsorGroup [ caelm-java ] failed to start ] 

[1087527824] 09/23/09 17:07:49 ERROR :: SponsorManager::start : Sponsor [ agentmanager ] failed to load 

[1087527824] 09/23/09 17:07:49 ERROR :: SponsorManager::start : Sponsor [ calmreporter ] failed to load 

[1087527824] 09/23/09 17:07:49 ERROR :: SponsorManager::start : Sponsor [ subscclient ] failed to load 

[1087527824] 09/23/09 17:07:49 ERROR :: SponsorManager::start : Sponsor [ subscproxy ] failed to load 

Solution:

You can resolve this problem by restarting iGateway, and logging in to the interface again.

To restart the iGateway service

1. Click the Administration tab and then click the Services subtab.
2. Expand the System Status entry.
3. Select a specific CA User Activity Reporting Module server.
4. Click the service's Administration tab.
5. Click Restart iGateway.

Upgrade to 12.5.x From Earlier Versions Fails

Symptom:

When you update CA User Activity Reporting Module from a release before 12.5.0 to release 12.5.0 or later using the CA User Activity Reporting Module subscription system, you may experience errors or upgrade failure.

Solution:

To avoid these errors, you can manually install the 12.5 preupgrade package, using the following procedure. This procedure can be used for both Subscription and Offline upgrades. It replaces the preupgrade package installation procedures described in the appropriate sections of this document.

To install the CA User Activity Reporting Module 12.5.x preupgrade package manually

1. Navigate to the FTP offline subscription site:

   ftp://ftp.ca.com/pub/elm/connectors/ftp/outgoing/pub/elm/ELM_Offline_Subscription

   The directory index displays a folder for each CA User Activity Reporting Module release.

2. Select the 12.5.xx_Offline_Subscription folder, and the Pre_12.5_Upgrade folder.
3. Download the pre-12.5 offline subscription update package. The file name follows the following format:

   subscription_12_5_xx_yy.tar

4. Using physical media such as a disk, or using scp, manually copy the .tar file to the CA User Activity Reporting Module appliance. We recommend a partition with a large amount of available space, such as /data/temp.
5. Untar the subscription file in your chosen directory.

   The main .tar file package contains four update.zip files:

   • iGateway
   • Java
   • EEM
   • ELM binary
6. Manually open each of these zip files using jar -xf. You can do so in any order, but the ELM binary package must be last.

   Each zip file contains an update shell script that installs the contents of the package. For example, EEM_update.sh

7. Locate and run each of these update scripts, ending with the ELM update, Upgrade_Server.sh.

   A message containing the target update version appears.

8. Enter yes to continue, and wait for the upgrade to complete.

   Return to the CA User Activity Reporting Module interface to confirm the upgrade.

When you have finished this procedure, you can complete your Subscription upgrade or Offline upgrade.

An Undefined Server Name Replaces the Primary CA User Activity Reporting Module Server Name

Symptom:

When you deploy CA User Activity Reporting Module as a virtual appliance, the name of the primary CA User Activity Reporting Module server is displayed as ca-elm on the Subscription Dashboard.

Solution:

You can resolve this issue by performing the following steps:

1. Click the Administration tab, the Services subtab, and the Subscription Service folder.

   The Global Service Configuration: Subscription Service page is displayed.

2. Type the name of the primary CA User Activity Reporting Module server in Default Subscription Proxy.
3. Select the name of the primary CA User Activity Reporting Module server from the Subscription Proxy(s) for Client Updates.
4. Select the name of the primary CA User Activity Reporting Module server from the Subscription Proxy(s) for Content Updates.
5. Click Save.

DSN Creation Fails on a Windows 64-bit Machine

Symptom:

When you install the ODBC DataDirect installer on a 64-bit machine, you cannot add a DSN from the ODBC Data Sources.

Solution:

You can resolve this issue by performing the following steps:

1. Navigate to C:\Windows\sysWOW64\odbccad32.dll.
2. Add the DSN.

The Path /opt/CA/LogManager/help Contains Connector Guides for Unsupported Integrations

Symptom:

The path /opt/CA/LogManager/help contains connector guides for integrations that are not supported in CA User Activity Reporting Module 12.5.03 and later versions.

Solution:

CA User Activity Reporting Module 12.5.03 and later versions support limited integrations to align with the Identify and Access Management strategy, so the UI displays the connector guides for only the supported integrations. However, the path /opt/CA/LogManager/help contains the connector guides for unsupported integrations too because CA User Activity Reporting Module stores the connector guides for all the integrations supported by CA User Activity Reporting Module 12.0 through 12.5.04 in /opt/CA/LogManager/help.

CPU Throttling is not Functioning

Symptom:

When you configure the CPU throttling feature after you upgrade the CA User Activity Reporting Module server to CA User Activity Reporting Module 12.5.04, the CPU throttling feature does not function.

Solution:

This issue occurs if you upgrade only the CA User Activity Reporting Module server but you do not upgrade the CA User Activity Reporting Module agent. If you upgrade only the CA User Activity Reporting Module server, you can configure the CPU throttling feature but CA User Activity Reporting Module agent does not support the feature.