Log Files

When you are troubleshooting, several files can help you:

The ccr.log file

This file records technical information about activities performed in IBM® Cognos® Controller. The ccr.log file is located in the C:\Program Files\ibm\cognos\ccr_64\log directory. You can use this file to troubleshoot technical problems, and when contacting technical support.

The Transfer Log File

This file records the activities that the installation wizard performed while transferring files. The transfer log file is located in the C:\Program Files\ibm\cognos\ccr_64\instlog directory. The file name identifies the product name, version, and build number, and includes a time stamp. The following is an example of the file name format:

tl-CNTRL-10.3-1100.213-20171027_0956.txt

The Transfer Summary-Error Log File

This file records the components you installed, disk space information, the selections you made in the transfer dialogs, and any errors the installation wizard encountered while transferring components. The transfer summary-error log file is located in the C:\Program Files\ibm\cognos\ccr_64\instlog directory. The file name identifies the product name, version, and build number, and includes a time stamp. The following is an example of the file name format:

tl-CNTRL-10.3-1100.213-20171027_0956_summary_error.txt

The Startup Configuration File

This file records your configuration choices each time you save your property settings. The file name is cogstartup.xml. If you are unable to save your configuration, or are having problems you can revert to a previously saved configuration file. The backup configuration files are located in the C:\Program Files\ibm\cognos\analytics\configuration directory. The following is an example of the file name format for backup configuration files:

cogstartup_200211231540.xml

The Locale Configuration File

This file records the configuration choices you make in Cognos Configuration for product and content locales, locale mapping, and currency support. If you experience problems with language support in the user interface or in reports, use these files to track your changes. The backup configuration files are located in the C:\Program Files\ibm\cognos\analytics\configuration directory. The following is an example of the file name format:

coglocale_200211231540.xml

The Run-Time Log File

The default Cognos log file named cogserver.log file, or other log files that you configure to receive log messages from the log server, record information after you start the IBM Cognos service. They are located in the ca_or_bi_install_path\logs directory. If you configured another destination for log messages, check the appropriate file or database.

Some log messages indicate problems. Most messages provide information only, but others can help you to diagnose problems in your run-time environment.

The Uninstallation Log File

This file records the activities that the Uninstall wizard performed while uninstalling files. You can use the log file to troubleshoot problems related to uninstalling IBM Cognos components. The location for the file varies with the type on uninstall. If you do a partial uninstall, the file is in controller_install_path\instlog. If you do a full uninstall, the files is in %temp% and the file name is cognos_unist_log.txt.

Windows Event Viewer

Windows Event Viewer provides information about program, security, and system events. For example, if the IBM Cognos service fails to start, this fact is recorded in the event log.

For information about how to use Windows Event Viewer, see the Windows help.

Microsoft Internet Information Services (IIS) Log File

This file records Microsoft Internet Information Services (IIS) activities. The log file is found in the installation_location/windows/system32/logFiles/W3SVC1 directory. You can use this log file to troubleshoot problems related to your IIS Web server. For example:

  • Code 404 is a page not found error.

    Your virtual directory may not be configured correctly.

  • Code 304 is a security credential error.

    Your directory security may not be configured correctly.

  • Code 200 indicates that IIS is working correctly.

    The problem you are encountering is not related to your IIS Web server.

For more information, see the Microsoft Internet Information Services help.