Known issues in 12.0.x

In Cognos Analytics on Cloud On-Demand, when you click the Product tour button on the Welcome page, the product tour may not appear.

After a deployment is imported, users may find that some of their Favorites and Recent items are either broken, not imported, or overwritten.

• Broken connections to Favorites or Recent items

  This problem occurs if someone renames and/or moves an asset before every user who references that asset has logged in. To resolve the issue, restore the name and location of the asset to its exported state. After every user who references that asset has logged out of CA and then logged back in, you can then safely rename the asset to any name and its Favorites or Recent connection will not be broken.

• Favorites are not imported from a partial deployment

  When you import a partial deployment to an environment that has or had Favorites, none of the Favorites in the deployment are imported.

• Recent items are not imported from a partial deployment

  When you import a partial deployment to an environment that has or had Recent items, none of the Recent items in the deployment are imported.

• Existing Favorites and Recent items are overwritten during a full deployment import

  When you import a full content store or full tenant content deployment, affected accounts are populated with Favorites and Recent items from the import.

When you modify existing truncated text of an asset's name or description from the Properties page in the Content view, your updated text may not display properly.

Solution

To resolve this issue, refresh your browser.

Exported deployments do not contain assets that were listed in the Favorites tab (as of version 12.0.1) and the Recent tab (as of version 11.0). The issue occurs when you import a deployment into a fresh content store.

When Cognos Analytics and Jupyter Notebook Server are configured to use HTTPS and you try to create a notebook or open a notebook sample, the following message appears:

A secure connection can't be established between the Cognos Analytics server and the Jupyter server. Verify that each server has valid SSL certificates installed.

This error occurs even though all SSL certificates were set up correctly.

When you try to import a deployment that is not password-protected into a fresh content store, error messages appear similar to the following:

CM-REQ-4111 Object "/Team Content/DBCERT_AZURESQL_N/model" (of class "model") was not imported. CM-REQ-4163 The import operation was unable to add an object. CM-SYS-5149 Content Manager is unable to process your request because a data error occurred in the content store database subsystem. Try to determine the report that triggered the error by checking log files in the ./logs directory. An error occurred while reading the value from the stream object. Error: "java.util.zip.ZipException: invalid stored block lengths"modelCM-REQ-4111 Object "/Team Content/DBCERT_AZURESQL_N/model/[].[securityViews].[DBCERT_AZURESQL_N]" (of class "modelView") was not imported. CM-REQ-4163 The import operation was unable to add an object. CM-REQ-4191 The parent path for the object does not exist. The missing parent path is "/Team Content/DBCERT_AZURESQL_N/model".

This issue is caused by faulty versions of the Java Runtime Environment (JRE) that are included in the following Cognos Analytics releases:

• 12.0.2 (caused by JRE 8.0.8.10)
• 12.0.1 (caused by JRE 8.0.8.5)

Workaround

To resolve this issue, ensure that your deployment archive is encrypted:

• If you create the deployment using the Manage component, you are already required to set an encryption password:

  Click Manage > Content > New backup

• If you create a partial deployment using the legacy Administration console, ensure that you click Set the encryption password when prompted.

  For more information, see step 15 in Creating a new export deployment specification.

If you try to upgrade your 11.2.4 FP3 content to version 12.0.0, 12.0.1, or 12.0.2, you may need to run specialized scripts before you can do another upgrade to version 12.0.3 or later.

DPR-ERR-2079 Firewall Security Rejection

The issue occurs when you try to access the View run history details page or the View archive versions page for a selected report.

Workaround

You can view the missing run history information by navigating to these pages:

• Content_location > report_name > Actions menu > View versions > Open Details panel
• Content_location > report_name > Actions menu > Run details

The following information is available:

• Request, start, and completion Times
• Report paths
• Archive versions
• Format type
• Language
• Output download links

The file .ca_base_preserve.txt specifies files to be preserved when you upgrade to a new version of Cognos Analytics. However, in releases 12.0.0, 12.0.1, and 12.0.2, .ca_base_preserve.txt is missing references to the following files:

• install_location/templates/ps/portal/variables_TM1.xml
• install_location/templates/ps/portal/variables_plan.xml
• install_location/templates/ps/portal/icon_active_application.gif
• install_location/webcontent/planning.html
• install_location/webcontent/pmhub.html
• install_location/webcontent/tm1/web/tm1web.html
• install_location/templates/ps/system.xml
• install_location/templates/ps/portal/system.xml

Workaround

1. Go to the folder install_location/configuration/preserve.
2. In a text editor, do one of the following:
   • Open the file preserve.txt, if it already exists.

     or

   • Open the file preserve.txt.template.
3. Add the following lines:

   #TM1 files
   templates/ps/portal/variables_TM1.xml
   templates/ps/portal/variables_plan.xml
   templates/ps/portal/icon_active_application.gif
   webcontent/planning.html
   webcontent/PMHub.html
   webcontent/tm1/web/tm1web.html
   
   #CA files
   templates/ps/system.xml
   templates/ps/portal/system.xml

4. Save the file as preserve.txt.

For more information, see Preserved files and folders when upgrading Cognos Analytics.

After a Daylight Saving Time change, the start time of daily schedules may unexpectedly shift by one hour.

For more information, see COGNOS ANALYTICS - DAYLIGHT SAVINGS TIME CHANGE RESULTS IN AN UNEXPECTED SHIFT IN SCHEDULE START TIMES (https://www.ibm.com/support/pages/node/7052876).

In Cognos Analytics on Cloud On-Demand, when you try to log in to the Cognos Analytics server from Framework Manager, the following error message appears:

An error has occurred in the script on this page.
Error: Invalid character

Solution

To resolve this issue, you must enable WebView2. For more information, see Alternate web technology support for Framework Manager authentication (Microsoft Edge WebView2).

When you modify existing truncated text of an asset's name or description from the Properties page in the Content view, your updated text may not display properly.

Solution

To resolve this issue, refresh your browser.

After you install Transformer using a French, German, or Japanese locale, the following issues occur:

• In Cognos Configuration, when you select Help > About IBM Cognos Configuration, the displayed version is 11.0 instead of 12.0 and the copyright year is 2017 instead of 2024.
• In Transformer, when you select Help > About Transformer, the copyright year is 2017 instead of 2024.

After you install Transformer using a German locale, the following issues occur:

• In Cognos Configuration, the entire user interface is in English. This includes the About IBM Cognos Configuration box and the splash screen.
• In Transformer, when you select Help > About Transformer, the text appears in English.

If you upgraded customized themes to release 12.0.1, you may notice differences in the appearance of Cognos Analytics that did not exist in the previous release. For example, elements of the application bar or the Navigation bar might now be blue instead of green.

This problem exists because legacy themes do not contain the parameter paletteId, which is introduced in 12.0.1.

Solution

To resolve this issue, follow these steps:

1. Download your customized theme.
2. Extract the .zip file.
3. Edit the extracted spec.json file and add the following line:

   "paletteId":"IBM"

4. Upload your modified theme and then apply it as the default.

For more information, see Modifying and uploading your own theme.

You cannot apply a top or bottom filter to a field if auto-group is enabled or to a data group. Conversely, you cannot apply auto-group to a field if you enabled the top or bottom filter. This is to prevent certain errors from appearing in dashboards.

Existing dashboards that had these settings applied together did not change. However, if users disable the top or bottom filter, they cannot reapply the top or bottom filter unless they disable auto-group. Conversely, if users disable auto-group, they cannot reapply the auto-group unless they remove the top or bottom filter.

Solution

If you removed a top or bottom filter from a field and cannot add the filter again, you must disable auto-group before applying the filter.

If you disabled auto-group from a field and cannot enable auto-group again, you must remove the top or bottom filter before enabling auto-group.

If you have a group of widgets and change the position of the widget group by using the position properties (in the General > Position section of the Properties page), the widgets change their positions but do not keep their respective positions to each other (for example, the widgets might overlap).

Workaround

To work around this issue, use the mouse to move the grouped widgets on the canvas instead of using the Properties page.

When using narrative insights with forecasting enabled on a dashboard visualization with at least two fact tables, you might receive a message in the XQE log file with the following error code:

Caught error in the Query Service: XQE-PLN-0503 The data item [query].[text_string] contains an operation across 2 fact streams and involves detail items. Please ensure that each term is aggregated before the operation is applied.

This error also displays in the Assistant if you ask the Assistant to show a visualization that has calculation columns across two fact tables.

Cause

This error occurs because narrative insights are adding additional aggregation operations on expressions that use multi-fact calculations that do not explicitly specify aggregation operations.

Solution

To address this error, follow these steps:

1. Use only one fact table in your dashboard visualization before you enable narrative insights or add explicit aggregations in multi-fact calculations.

   For example, instead of using this calculation:

   abs(sales_receipts.line_item_amount - (sales_targets.total_goal * 0.25))

   use this calculation instead:

   abs(total(sales_receipts.line_item_amount) - (average(sales_targets.total_goal) * 0.25))

2. Ensure that the Calculate after aggregation check box is selected: