Using FCABAPP.LOGCSI and FCAB.LOGCSI to identify program issues

Alerts and notices

Scenario

FileCabinet CS uses the fcabapp.logcsi and fcab.logcsi log files to identify generic application issues, but they are not generally used to troubleshoot printing issues.

Note: These logs should only be used at the request of a Technical Support Representative. When the log files are collected they are sent to Support to review.

Solution

Follow these steps to create the fcabapp.logcsi and fcab.logcsi log files.

  1. Navigate to X:\WinCsi\Cabinet (where X is the drive letter where the application is installed) in Windows Explorer or My Computer.
  2. Choose File > New > Text Document and name the document fcabapp.logcsi. Repeat this step again and name the second document fcab.logcsi.

    Note: If you are not prompted to confirm that you want to change the filename extension, the file was not properly renamed. Choose Tools > Folder Options > View and verify that the Hide known file extensions checkbox is not marked so that you can see the filename for all files.

  3. Right-click on the fcabapp.logcsi file and choose Properties.
  4. On the Security tab, verify that the Everyone group is listed and has Full Control. If Everyone is not listed, add a new group as follows.
    1. Click the Edit button below the Group or user names pane.
    2. In the Permissions dialog, click the Add button, enter Everyone in the Enter the object names to select field, and then click OK.
    3. Mark the Allow checkbox for Full control in the Permissions for Everyone pane, and then click OK.
    4. In the Properties dialog, click OK to save the new group.
  5. Repeat steps 3 and 4 with the fcab.logcsi file.

To add entries to the log file:

  1. Open FileCabinet CS.
  2. Print—or perform whichever task is causing the issue—using the FileCabinet CS printer driver.
  3. Email the files to the Technical Support Representative assisting you.
  4. After you have sent the files to your Support Representative, delete the files from X:\WinCsi\Cabinet. If you don't delete the files, it can affect FileCabinet CS's performance.

Internal notes


Virtual Office CS and SaaS Note: Since the Cabinet directory is shared by all firms, we cannot do an "application-wide" log file. However, we can set up a special version of fcab.logcsi that is user-specific in VO/SaaS. In Y:\FCabSys create or have the Web CF create a file named Firm.<HashID>.do.log, where <HashID> is the Hash ID not the translated name. This will create the Firm.HashID_fcab.logcsi file automatically once you launch FileCabinet.

Share This