CA Business Intelligence (CABI) FILESTORE directory (SC\CommonReporting3\BusinessObjects Enterprise 12.0\FileStore) directory is occupying a large amount of disk space on the CABI server.

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

Description:

"Connection failed. The server has reached the maximum number of simultaneous connections. (Error: RWI 00239)" occurs when using CA Business Intelligence (CABI) Infoview.

Solution:

The FILESTORE INPUT folder holds the base CABI reports.
The FIELSTORE OUTPUT folder holds the instances of these reports.

If there are a lot of scheduled CABI reports or many users running CABI reports, you should perform housekeeping on the FILESTORE directory to avoid potentially running out of disk space on the CABI server.

To limit Instance History for scheduled CABI reports:

  1. Login to the Central Management Console (CMC) as an Administrator.

  2. Click on FOLDERS and navigate to the scheduled report.

  3. With the report highlighted, click on the ACTIONS->LIMITS menu.

  4. Configure the instance limits as desired.

    Figure 1

CABI uses Temporary Storage to store cached documents. Similar to report instance limits, limits can be implemented on the CABI Temporary Storage.
To Impose limits on CABI Temporary Storage:

  1. Login to the Central Management Console (CMC) as an Administrator.

  2. Click on TEMPORARY STORAGE.

  3. Click on LIMITS.

  4. Configure the limits as desired.

    Figure 2

Periodically, you should prune the FILESTORE Repository to remove empty directories.

Note: You should perform the pruning as part of scheduled CABI maintenance when CABI usage is low.

To prune the FILESTORE Repository to Remove Empty Directories:

  1. Login to the Central Management Console (CMC) as an Administrator.

  2. Click on SERVERS.

  3. Locate and highlight the Input File Repository server and click on the STOP SERVER button.

  4. Right-click on the Input File Repository server and select PROPERTIES. Add '-Prune' to the end of the Command Line Parameters section.
    For example: -loggingPath "C:/Program Files (x86)/CA/SC/CommonReporting3/BusinessObjects Enterprise 12.0/logging/" -Prune

  5. Perform the same steps for the Output File Repository server.

  6. Restart both the Input and Output Repository servers.

  7. Let the pruning process run for a few hours.

  8. Stop both the Input and Output Repository servers. Remove the '-Prune' option from the end of the Command Line Parameters section.

  9. Restart both the Input and Output Repository servers.