Planning Analytics Workspace 73
Microsoft Windows 2016 server

When user browse to PAW portal, some of the text is in other language than English.

The edit fields are controlled by the settings in your web browser.

How change language in Chrome:

Go to Settings

Expand Advanced

Click on Languages – expand the dialog

Add the language you want the text in PAW toolbar to be the chosen language for your browser.


You create translated values by adding a caption attribute, and then by assigning caption values for every language that you want to make available. You add caption attributes and caption values by creating TurboIntegrator processes.

Planning Analytics Workspace uses the browser language setting to determine which language to display, so a user can view cubes, views, dimensions, and so on, in their own language without needing any additional configuration.

If you enabled the display of translated names on your TM1 server, then cubes, dimensions, elements, and attributes display in your local language as determined by the language setting of your Web browser. If translation is not enabled, object names appear as they were originally created on the TM1 server. In websheets, only elements that are returned by SUBNM or TM1RptRow functions are translated. All other element and object names in websheets display as originally created.

More information:

IBM Planning Analytics Tips & Tricks: Captions

Cognos Controller 10.4.2 if8 CONTRL_UPDATE_version=CCR-AW64-ML-RTM-10.4.2000.1064-0
Microsoft Windows 2016 server
Planning Analytics  TM1-AW64-ML-RTM-11.0.911.20-0

After upgrade of TM1 (Planning Analytics) to a newer version than then the Cognos Controller FAP does not work.
The FAP IP stop with a error.

The TM1ProcessError can be:

Cannot convert field number 17, value “123456” to a real number

Error: Data procedure line (0): 01004[Microsoft][ODBC SQL Server Driver]String data, right truncation


Upgrade Cognos Controller software to a later version.

  1. Install Controller 10.4.2 IF 17
  2. Stop the Windows service of the TM1 server that is connected to FAP.
  3. Stop the Windows service IBM Cognos FAP Service.
  4. Manually delete the existing <…>MonthlyCompanyDetails_TextImportData TI process from inside TM1 Architect.
  5. Start the Windows service of the TM1 server that is connected to FAP.
  6. Start the Windows service IBM Cognos FAP Service.
  7. Do a full FAP IP.


More information:

These errors occur because Planning Analytics and later does not support FAP jobs with comments containing more than 2047 characters.  The existing <…>MonthlyCompanyDetails_TextImportData TI process that you upgraded from your previous TM1 environment does not adhere to this new limitation.

If you upgrade Planning Analytics 2.0.9, you must upgrade Cognos Controller 10.4.2 to a later version.

Cognos Controller 10.4.2
Microsoft Windows 2016 server


We need to install a fix pack/interim fix to cognos controller – do we also need to upgrade the cognos controller client?

Suggested solution:

Do a test upgrade in your test environment, and see if the client works without upgrade the Cognos Controller client.

When you do a installation of a new version, you must upgrade the cognos controller client. But if you only install a Interim fix then the client installed can be used without upgrading.

Any fixes that are in the client side, like help – content issues, will not be solved.

Recommendation is to always upgrade the cognos controller client too.

Before installation we had in the client this version:

IBM Cognos Controller Version 10.4.2000.293
Integration Version 10.4.2000.145
Installer/Updater Kit Version 10.4.2000.1064

after installation we had this in cognos controller client – help – system info:

IBM Cognos Controller Version 10.4.2000.293
Integration Version 10.4.2000.145
Installer/Updater Kit Version 10.4.2000.1111

The client looks like it is working, but not any bugfixes that are in the Cognos Controller client code is not part of the solution.

Supported is to have both cognos controller client and cognos controller server at the same version.

You can check the version of cognos installed in the cmplst.txt file, often found in folder D:\Program Files\ibm\cognos\ccr_64

CONTRL_UPDATE_name=IBM Cognos Controller Update
[Main Applications]

When doing a upgrade of cognos controller to a interimfix it is important that you;

Note down cognos controller configuration for report server URL.

Specifically, stop the following Windows services:

  • IBM Cognos
  • IBM Cognos Controller Batch Service
  • IBM Cognos Controller Consolidation
  • IBM Cognos Controller Java Proxy
  • IBM Cognos Controller Reports
  • IBM Cognos Controller Web
  • IBM Cognos Controller Web Spreadsheet Service
  • IBM Cognos Controller Web UI
  • IBM Cognos FAP Service
  • WWW service

Stop COM+ object for Cognos Controller.

Backup the controller web folder

D:\Program Files\ibm\cognos\ccr_64\fcmweb and D:\Program Files\ibm\cognos\ccr_64\frontend

Check that no JAVA processes is running, before you start the upgrade.

After upgrade, Cognos Controller Web need to be reconfigured.

More information:

Currently Supported Versions of Controller (incl. Interim Fixes):

Updater Kit Build CCR Version DB Version Comment
10.4.2000.1111 10.4.2000.311 10.4.2 IF17 1010 Generally available (FixCentral)
10.4.2000.1108 10.4.2000.300 10.4.2 IF16 1010 Generally available (FixCentral)
10.4.2000.1098 10.4.2000.300 10.4.2 IF15 1010 Generally available (FixCentral)
10.4.2000.1079 10.4.2000.300 10.4.2 IF14 1010
10.4.2000.1078 10.4.2000.300 10.4.2 IF13 1010
10.4.2000.1076 10.4.2000.300 10.4.2 IF12 1010
10.4.2000.1073 10.4.2000.300 10.4.2 IF11GA 1010 Generally available (FixCentral)
10.4.2000.1070 10.4.2000.296 10.4.2 IF10 1010
10.4.2000.1067 10.4.2000.296 10.4.2 IF9 1010
10.4.2000.1064 10.4.2000.293 10.4.2 IF8 1010
10.4.2000.1063 10.4.2000.292 10.4.2 IF7GA 1010 Generally available (FixCentral)
10.4.2000.1018 10.4.2000.270 10.4.2 IF3 1010  
10.4.2000.1013 10.4.2000.267 10.4.2 IF2 1010  
10.4.2000.1002 10.4.2000.259 10.4.2 IF1GA 1010 Generally available (FixCentral)
10.4.2000.185 10.4.2000.252 10.4.2 RTM 1010 Available via Passport Adv. (full install)


Cognos Controller 10.4.2

Microsoft Windows 2019 server


At new installation, i after selection of database, in cognos controller client, are then stuck.

No more information.


The cognos controller client uses port 80 to talk to the cognos controller server, but after the selection of database, it will if SSO is active, connect to Cognos BI to validate the user.

This happens on the port listed in Cognos Controller Configuration as Report Server.

If this is port 9300, then port 9300 need to be open in firewall between server and client. This is not the normal case.

You should instead change the Cognos Controller Configuration for Report server to use port 80.

Wrong line at report server:

Correct line at report server:

More information:

Planning Analytics Workspace 74

Microsoft Windows 2019 server


After migrate reports from old PAW to new PAW; some workspace does not show, they are blank instead of showing the table or graph.

Possible solution:

Ensure that inside Planning Analytics Workspace Administration, that the URL for TM1 Application Server Gateway URI point to your TM1WEB server and port.

This settings are also found in file d:\IBM\PAW74\config\paw.ps1

PAW uses the TM1WEB to render the websheets, so this must point to correct port.

If it point to the pmpsvc instead, you will get a blank page, where there should be a websheet in the dashboard.

You migrate the books and reports with the PAW lifecycle function from old PAW to new PAW; but the web sheets are migrated with the TM1 data folder.


If there is only the websheet that are blank in the PAW book, then it can be the IBM Cognos BI Gateway URI that point wrong, it should point to the IIS weburl in case when you use SSO in your Tm1 application. It should match the settings in the TM1S.CFG file. Try by change it to:

from the old value;

The IBM Cognos BI Dispatcher URI should always be;


The other valus in the IBM Planning Analytics Workspace Administration Tool ( ) should be:

The TM1 Admin Server URI

TM1 Application Server Gateway URI  (port depending on setup as listed above)


More information:

Websheet is blank in PAW

Planning Analytics Workspace 74
Microsoft Windows 2019 Server


Can not expand proven_techniques in databases under modeling tools in Planning Analytics Workspace.

Other TM1 instance work.

Possible solution:

The TM1 instance HTTPportnumber is not open in the firewall.

PAW uses REST API, HTTPportnumber, to communicate with the TM1 instances.

Change to a port you now the firewall let trough, by edit the tm1s.cfg file.


Save the TM1S.CFG file and try again.

PAW have access to the TM1 Admin service, therefor the TM1 instance is listed in the tree.

More information:


Cognos Controller Web 10.4.2

Microsoft Windows 2019 server


Controller Web does not work.

When you check the log file in folder D:\Program\ibm\cognos\ccr_64\fcmweb\wlp\usr\servers\fcm.web\logs you see text like

2022-04-11 15:47:15 | | ERROR | [] CCR WS API not initialized yet [error=2 counts of InaccessibleWSDLException.
]. Retrying in 1000 ms…


Go to folder D:\Program\ibm\cognos\ccr_64\fcmweb\wlp\usr\servers\fcm.web

Open file in notepad++

Ensure that the ccrwsUrl= points to the correct server.

More Information:


Planning Analytics Workspace 74

Microsoft Windows 2019 server


How move user from on PAW installation to a other PAW installation?

Suggested solution:

Browse to the from PAW server and login as administrator.

Click on Administration icon.

Click on Users tab.

Click on Export Users.  (this will export all users to a csv file)

The file will be in you download folder, on your computer.

Close the web browser and logout from the old PAW server.

Open the all-users.csv file in notepad++ and add names to all blank columns. There is not allowed to be blank columns in the csv file when loading it up to the PAW.

Start the web browser and go to the new PAW, where the users should be inserted.

Login as administrator.

Click on Administration icon.

Click on Users and Groups.

Click on upload users from csv file icon.

Drag the all-users.csv file to the drop zone.

Done, if you not have blank columns, then you get a error.

But the rows with correct information is loaded to PAW.


More Information:


Cognos Analytics 11.1.7

Microsoft Windows 2019 server


What firewall ports should be open in windows firewall to make Cognos work?


These are the ports that is used by Cognos products:

Cognos Analytics 11.1.7

80 for client access to cognos portal
443 for client access (https/ssl/tls)
9300 Cognos dispatcher
4300 Sync configuration between CA11 servers
5701 Sync CA11 servers to a group of CA11 servers
9301 CA11 uses this port at start
9362 Cognos log server
9080 WebSphere transport port
8172 IIS Server Farms port to check windows servers


Cognos Controller 10.4.2

80 for controller client access to controller server
443 for client access (https/ssl/tls)
9300 Contact to CA dispatcher
9080 Client to controller web
9082 Client to controller report service
9081 if installed on same server as CA11
3000 Controller web backend port


Planning Analytics

80 for client access to PAW
443 for client access (https/ssl/tls) to PAW
9300 Contact to CA dispatcher
9510 Client access to TM1WEB
9511 Tm1 app web (pmpsvc)
9012 PAA agent
5495 Tm1 architect contact with TM1 Admin service
5498 Tm1 architect contact with TM1 Admin service (ssl)
5895 TM1 Admin Server -> TM1 REST API (HTTP)
5898 TM1 Admin Server -> TM1 REST API (HTTPS)
12300-12400 TM1 instance port range
8888 Administration port for PAW
9513 Shutdown port



More Information:


Cognos Analytics 11.1.7

Microsoft Windows 2019 server


After new installation, when you browse to http://servername/ibmcognos you get an error.

If you browse to http://servername:9300/bi/v1/disp, then CA11 works fine.

When it do not work, you see in the URL: http://localhost/ibmcognos/bi/bi

Error message:

The webpage cannot be found


You have run the CA_IIS_Config.bat file first, without installing requestrouter_amd64.msi or rewrite_amd64_en-US.msi. The Rewrite module need to be installed first.

CA_IIS_Config.bat file is found in folder D:\Program\ibm\cognos\analytics\cgi-bin\templates\IIS

Download the needed files, this is a new version for Windows 2019, from here:

Install them on the Microsoft Windows 2019 server.

You should have in control panel – “Program and Features”;

IIS URL Rewrite Module 2 version 7.2.1993

Microsoft Application Request Routing 3.0 version 3.0.05311

Then run the CA_IIS_Config.bat file, again from a command prompt.

Check in Internet Information Services (IIS) Manager that the URL rewrite exists.

(if rule SSO login is disabled – you do not have SSO with Cognos Analytics).

More Information: