Product:
Cognos Controller 10.3
Microsoft Windows 2012 R2 server

Problem:
One user does not get the Cognos Controller menu to work inside Microsoft Excel 365.
When user try to add the COM add in there is a error like COM import fail.

Solution:
Close Excel and Close Cognos Controller Client.
Enter REGEDIT on run command on start menu on users laptop.
Inside [HKEY_CURRENT_USER\Software\Microsoft\Office\Excel]
Right click on Excel branch and select export

Save the file as regbackup.reg in a location you can find (d:\temp)
The delete the rows below addins, that is for Cognos Controller.
[HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins]

Start Cognos Controller client on your laptop and login in.
Click on the icon for excel inside Cognos Controller client.
This should start the Excel program locally, and also install the Controller link to excel again. This take time, as the start of Excel is slow. When excel is fully started, check that the controller menu work.

More information
https://www.ibm.com/support/pages/controller-excel-link-microsoft-excel-addin-was-disabled-when-opening-data-entry-form
https://www.ibm.com/support/pages/troubleshooting-failed-register-excellink-addin-add-method-addins-class-failed-error-when-using-excel-link
https://www.ibm.com/support/pages/troubleshooting-controller-excel-link-com-add-disappears-each-time-excel-closed-relaunched

Product:
Cognos Controller 10.4.2
Microsoft SQL 2019 database

Problem:
When from inside Microsoft SQL Management Studio do a restore on top of a existing database (ControllerTest) from a backup of a other database (ControllerProd) you get an error.

Restore of database “ControllerTest” failed.
Additional information:
System.Data.SQLClient.SQLError: Exclusive access could not be obtained because the database is in use.

Solution:
On the Cognos Controller server, stop the IBM Cognos Controller Batch Service. When that is stopped, then normally there should not be any sessions from the Cognos Controller server to the Database server – as long there is no person inside Cognos Controller Client working.

More information:
https://www.ibm.com/support/pages/how-backup-and-restore-db2-databases-use-cognos-controller
https://www.ibm.com/support/pages/how-migrate-upgrade-upsize-existing-database-new-later-version-controller

To check if there are missing SQL logins inside the restored controller database run below command from Query window in Microsoft SQL Management studio for that particular database.
EXEC sp_change_users_login ‘Report’;

If the SQL login for controller is listed, run below command to connect it.
EXEC sp_change_users_login ‘Auto_Fix’, ‘cognos’;

http://dbadiaries.com/using-sp_change_users_login-to-fix-sql-server-orphaned-users

Product:
Cognos Controller 10.4.2
Microsoft Windows 2016 server
Microsoft SQL 2019 database

Problem:
When try to connect to the database with the DBCONV tool you get a error. The data connection test inside Controller Configuration worked fine.
ERROR: com.microsoft.sqlserver.jdbc.SQLServerException:
Login failed for user ‘cognos’.
ClientConnectionId:ca120094-…

Solution:
The SQL login has a period in the password. Please use only Letters and numbers in the password used for Cognos Controller.

Go into Microsoft SQL Management studio.
Select the SQL login used for the controller database.
Change the password to a simpler one.
Update the password in Controller Configuration.
Test and save again.
Click on the icon to convert the database.
Click on connect.
Click on upgrade.

More information:
https://www.ibm.com/support/pages/how-migrate-upgrade-upsize-existing-database-new-later-version-controller

Product:
Cognos Controller 10.3.1
Microsoft Windows 2016 server

Problem:
New users can not login to Cognos Controller. The client program stop after selection of database.
There are no error messages.

Solution:
The new users are on a different company, that have there own Windows Domain. When the cognos controller client start up, after selection of database, it talks to the Cognos Analytics server even do you use NATIVE security, as it will run the Cognos Reports on the CA server.
If Cognos Configuration is setup with only server-name and not FQDN (fully qualified domain names) e.g. servername.domain.com then the client computer can not find the cognos server and time out.
There are no error messages.

Workaround is to at the new company create a DNS alias, so that server is accessible within there domain. If CA11SERVER.COMPANY1.COM should be reached from COMPANY2.COM you need to create a alias in DNS server at COMPANY2.
Alias name: CA11SERVER
FQDN: CA11SERVER.COMPANY2.COM
FQDN for target host: CA11SERVER.COMPANY1.COM
This give a computer on COMPANY2 domain can browse to CA11SERVER, as it is found in the DNS.

Solution is to setup Cognos Configuration with FQDN always.

You can use this URL to test access to server in a browser (replace servername with your servername)
http://servername:9300/p2pd/servlet
http://servername:80/ibmcognos/controllerserver/ccrws.asmx

More Information:
https://www.mustbegeek.com/add-cname-record-in-windows-dns-server/
https://www.ibm.com/support/pages/remote-name-could-not-be-resolved-when-launching-controller-client

Product:
Cognos Controller 10.4.2 IF4 (CONTRL_UPDATE_version=CCR-AW64-ML-RTM-10.4.2000.1020-0)
Cognos Analytics 11.0.13
Microsoft Windows 2012 R2 server

Problem:
How setup Controller web in the new version?
When the Windows IIS server for CA11 is using HTTPS.

Solution:
Follow the official instructions here https://www.ibm.com/support/pages/how-install-controller-web
https://www.ibm.com/support/pages/how-configure-controller-web-use-cognos-cam-authentication
https://www.ibm.com/support/pages/how-configure-controller-web-use-ssl-https

This are the steps;
Ensure that you during setup can browse to cognos analytics iis server on both http and https.
Controller web frontend and backend are installed on the same Windows server.
Open server.env file from folder C:\Program Files\IBM\cognos\ccr_64\fcmweb\wlp\etc\
Change to: JAVA_HOME=C:/Program Files/IBM/cognos/ccr_64/fcmweb/jre
Open jvm.options file from folder C:\Program Files\IBM\cognos\ccr_64\fcmweb\wlp\etc\
Change last in file to:
-Xms4g
-Xmx8g
(depending on number of users and memory on the Windows Server)
Save the files.
Start a CMD command prompt as Administrator
Go to folder C:\Program Files\IBM\cognos\ccr_64\fcmweb
Enter command:  SyncDBConf.bat  ..\Data  wlp\usr\shared\config\datasources
In file explorer go to C:\Program Files\IBM\cognos\ccr_64\fcmweb\wlp\usr\servers\fcm.web

Open com.ibm.cognos.fcm.web.properties file in notepad++
Change to: ccrwsUrl=http://cognosserver.company.com/ibmcognos/controllerserver/ccrws.asmx
and update also;
biUrl=http://cognosserver.company.com/ibmcognos/bi/v1/disp
biDispatchEndpoint=http://cognosserver.company.com:9300/p2pd/servlet/dispatch
loginMode=CAM
logoutMode.logoutCam=true
# pdfFont=C:/windows/fonts/Arial.ttf
Save the files with this changes.
Map up the c drive of the cognos analytics server and go to folder C:\Program Files\IBM\cognos\analytics\templates\ps\portal\ and create the text file variables_CCRWeb.xml
In notepad++ enter this values:

<CRNenv c_cmd=”http://controllerwebserver.company.com:443/#!/CamLogin”>
<cookies>
<param name=”cam_passport”/>
</cookies>
</CRNenv>

Save it inside file variables_CCRWeb.xml.
Restart the IBM Cognos Controller Web Windows service.
Go to folder C:\Program Files\IBM\cognos\ccr_64\frontend
Open config.js file in Notepad++

Change first host value to “host”: “controllerwebserver.company.com“,
Change second host value to “host”: “controllerwebserver.company.com“, //interface used by Controller Web UI Service
Change the port to 443 from 9080.
Save the file.
Restart the IBM Cognos Controller Web UI Windows Service.
Try to browse to http://controllerwebserver.company.com:443/ from client laptop.
Check that the windows firewall on the server allow ports 80,443,9300
If you are using SSO modify the IIS website’s controllerserver virtual directory to use anonymous authentication, only have Windows authentication on the sso virtual directory.

 

Get the Certificates for you controllerwebserver.company.com servers DNS alias from the company Certificate Authority. You need the root cert (root1.cer) and the intermediate cert (intermediate2.cer), also the pfx file for the servername and chain (servername3.pfx) with a password.
During setup use the same password for all keys and keystores, in our example we will use changeit.
Start a CMD command prompt as Administrator
Go to folder c:\Program Files\ibm\cognos\ccr_64\fcmweb\jre\bin
Update this command with your certificate files, before you run it:
keytool -keystore key.jks -importcert -file C:\temp\intermediate2.cer
Enter the password (must be the same as the password you got with the pfx file)
On question ‘Trust this certificate’ enter yes
Import the root1.cer file with command:
keytool -import -trustcacerts -alias issue -file c:\temp\root1.cer -keystore key.jks
Add the server-certificate with command:
keytool -importkeystore -destkeystore key.jks -srckeystore C:\temp\servername3.pfx -srcstoretype PKCS12 -srcstorepass changeit
(replace the changeit with the password you got with the pfx file and you used before)
Copy the file key.jks to folder C:\Program Files\IBM\cognos\ccr_64\fcmweb\jre\lib\security
Open C:\Program Files\ibm\cognos\ccr_64\fcmweb\wlp\usr\servers\fcm.web\server.xml in Notepad++
Replace the line <!– <feature>ssl-1.0</feature> –> with  <feature>ssl-1.0</feature>
Add a line at the bottom, like this:
</webApplication>
<keyStore id=”defaultKeyStore” password=”changeit” sslProtocol=”SSL_TLS” />
</server>
Save the file.
Restart the ‘IBM Cognos Controller Web UI’ and ‘IBM Cognos Controller Web
Copy the file key.jks to folder C:\Program Files\IBM\cognos\ccr_64\fcmweb\wlp\usr\servers\fcm.web\resources\security
Open C:\Program Files\IBM\cognos\ccr_64\analytics\templates\ps\portal\variables_CCRWeb.xml in notepad++ and change to https;

<CRNenv c_cmd=”https://controllerwebserver.company.com:443/#!/CamLogin”>
<cookies>
<param name=”cam_passport”/>
</cookies>
</CRNenv>

Open C:\Program Files\IBM\cognos\ccr_64\fcmweb\wlp\usr\servers\fcm.web\com.ibm.cognos.fcm.web.properties in notepad++

Change line ccrwsUrl=https://cognosserver.company.com/ibmcognos/controllerserver/ccrws.asmx and biUrl=https://cognosserver.company.com/ibmcognos/bi/v1/disp to use https if you only have SSL on the IIS server for CA11.
Save the file.
Delete the key.p12 file from folder C:\Program Files\IBM\cognos\ccr_64\fcmweb\wlp\usr\servers\fcm.web\resources\security

Reboot the controllerweb windows server.

Check filer C:\Program files\ibm\cognos\ccr_64\fcmweb\wlp\usr\servers\fcm.web\logs\messages.log for , if no error go one with next step.

One your laptop install openssl from here https://github.com/git-for-windows/git/releases/tag/v2.23.0.windows.1 – get the file Git-2.23.0-64-bit.exe. Run the installation with all default values.

Copy your servername3.pfx file to c:\workarea folder. Start a CMD command prompt as Administrator.
Run this command:

“C:\Program Files\git\mingw64\bin\openssl.exe” pkcs12 -in C:\workarea\servername3.pfx -clcerts -nokeys -out cert.crt

Enter the password you got with the pfx file.
“C:\Program Files\git\mingw64\bin\openssl.exe” pkcs12 -in C:\workarea\servername3.pfx -nocerts -out keyfile.key

Enter the password you got with the pfx file. Then you have to give a new password for the keyfile.key – for simplicity use the same password.
Copy cert.crt , keyfile.key files to C:\Program Files\ibm\cognos\ccr_64\frontend folder on your Controller Web server.

Open C:\Program Files\IBM\cognos\ccr_64\frontend\config.js file in Notepad++

Change the first port to “port”: 3443,
Change the protocol to “protocol”: “https:” //set https: for SSL
Change secure to “secure”: false //set this to false if Controller Web Backend is using Self Signed certificates
Remove /*   */   to uncomment the SSL section.
Change the “passphrase”:”changeit” to your password that you set before.
Save the file.
Restart the ‘IBM Cognos Controller Web UI’ and ‘IBM Cognos Controller Web
Try to browse to https://controllerwebserver.company.com/ from client laptop.

Check the log files in folder C:\Program Files\ibm\cognos\ccr_64\fcmweb\wlp\usr\servers\fcm.web\logs

This page can’t be displayed. Turn on TLS 1.0, TLS 1.1, and TLS 1.2 in Advanced settings and try connecting to https://hostname again. If this error persists, it is possible that this site uses an unsupported protocol or cipher suite such as RC4 (link for the details), which is not considered secure. Please contact your site administrator.
If you get above error, please try first with different web browser, like Firefox or Edge.

Error:

00000022 com.ibm.ws.ssl.provider.AbstractJSSEProvider                 E CWPKI0813E: Error while trying to initialize the keymanager for the keystore [C:/Program Files/ibm/cognos/ccr_64/fcmweb/wlp/usr/servers/fcm.web/resources/security/key.jks]. The private key password is not correct or the keystore has multiple private keys with different passwords.  This keystore can not be used for SSL.  Exception message is: [Cannot recover key].

00000022 com.ibm.ws.logging.internal.impl.IncidentImpl                I FFDC1015I: An FFDC Incident has been created: “java.security.UnrecoverableKeyException: Cannot recover key: invalid password for key in file ‘C:/Program Files/ibm/cognos/ccr_64/fcmweb/wlp/usr/servers/fcm.web/resources/security/key.jks’ com.ibm.ws.ssl.provider.IBMJSSEProvider getKeyTrustManagers” at

Solution:

The pfx file password was not used in creation of the key.jks file

Error:

00000022 com.ibm.ws.ssl.config.WSKeyStore                             E CWPKI0033E: The keystore located at C:/Program Files/ibm/cognos/ccr_64/fcmweb/wlp/usr/servers/fcm.web/resources/security/key.jks did not load because of the following error: Keystore was tampered with, or password was incorrect

00000022 com.ibm.ws.ssl.config.WSKeyStore                             W CWPKI0809W: There is a failure loading the defaultKeyStore keystore. If an SSL configuration references the defaultKeyStore keystore, then the SSL configuration will fail to initialize.

Solution:

The password in the server.xml file is not the same as the key.jks file.

Error:

00000022 com.ibm.ws.logging.internal.impl.IncidentImpl                I FFDC1015I: An FFDC Incident has been created: “java.security.UnrecoverableKeyException: Cannot recover key: invalid password for key in file ‘C:/Program Files/ibm/cognos/ccr_64/fcmweb/wlp/usr/servers/fcm.web/resources/security/key.jks’ com.ibm.ws.ssl.provider.IBMJSSEProvider getKeyTrustManagers” at

Solution:

Maybe you use different password in servername3.pfx and key.jks file

Error:

00000022 com.ibm.ws.ssl.config.WSKeyStore                             E CWPKI0033E: The keystore located at C:/Program Files/ibm/cognos/ccr_64/fcmweb/wlp/usr/servers/fcm.web/resources/security/key.jks did not load because of the following error: Keystore was tampered with, or password was incorrect

00000022 com.ibm.ws.ssl.config.WSKeyStore                             W CWPKI0809W: There is a failure loading the defaultKeyStore keystore. If an SSL configuration references the defaultKeyStore keystore, then the SSL configuration will fail to initialize

Solution:

The key.jks file is not copied to C:\Program Files\IBM\cognos\ccr_64\fcmweb\wlp\usr\servers\fcm.web\resources\security after update.

More Information:

https://www.ibm.com/support/pages/how-configure-controller-web-use-ssl-https

https://www.ibm.com/support/pages/node/563063

https://www.ibm.com/support/pages/node/156485

https://www.ibm.com/support/knowledgecenter/en/SSEP7J_11.0.0/com.ibm.swg.ba.cognos.inst_cr_winux.doc/t_configuresslforcognos8.html

https://www.ibm.com/support/pages/how-configure-force-controller-use-tls-12

https://www.ibm.com/support/pages/how-configure-controller-use-tls-formerly-ssl-connect-microsoft-sql-database-transit-database-encryption?lnk=hm

https://support.microsoft.com/en-us/help/17479/windows-internet-explorer-11-change-security-privacy-settings

Product:
Cognos Analytics 11.0.13
Microsoft Windows 2012 server

Problem:
Problem to login in Cognos Controller after TLS 1.2 demand on the CA11 server is implemented.

Error:
The underlying connection was closed: An unexpected error occurred on a send.
at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Cognos.Controller.ControllerSoapHttpClientProtocol.Invoke(String methodname, Object[] parameters)
at Cognos.Controller.Proxy.Light.WSLight.CheckServerConnection(String sGuid, String sUser)
at Cognos.Controller.Direct.ServerInfoD.CheckServerConnection()
at CCR.AppContext.CheckConnectionToServer()

Solution:
On cognos controller client computer
start a command prompt as administrator
Run below commands (to update the registry)

REG ADD HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 /v SchUseStrongCrypto /t REG_DWORD /d 1

REG ADD HKLM\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319 /v SchUseStrongCrypto /t REG_DWORD /d 1

More Information:
https://www.ibm.com/support/pages/how-configure-force-controller-use-tls-12
https://www.ibm.com/support/pages/error-occurred-while-trying-object-reference-not-set-repnetgetuserinfo-error-launching-controller-client-caused-tls-1011-disabled-ca-server

Product:
Cognos Controller 10.4.2
Cognos Analytics 11.0.13
Microsoft Windows 2012 server

Problem:
When run a standard report you get a error inside Cognos Controller only on a new database.

Error:
RQP-DEF-0177 An error occurred while performing operation
‘sqlPrepareWithOptions’ status=’-56′.
UDA-SQL-0115 inapproproeate SQL request
UDA-SQL-0564
invalid column name ‘lookupwebgrpename’

Possible Solution:
That you have setup the data source manually in Cognos Connection and are missing information.

1 Click Manage and go to the IBM Cognos Analytics Administration Console
2 Click on the Configuration Tab
3 Click on data source name and then on more… icon
4 Click Set properties
5 Click on Connection Tab
6 Click the pencil icon for Edit the connection string
7 Check that the sever name to database is correct.
8 If database name is missing – enter the correct database name.


9 Click OK
10 Click OK
11 Click Test the connection icon, far to the right.
12 Click Test
13 Click Close
14 Click Close
15 Click OK
16 Click OK

More information:
https://www.ibm.com/support/pages/error-rqp-def-0177-sqlpreparewithoptions-status-56-when-running-some-standard-reports
https://www.ibm.com/support/pages/error-rqp-def-0326-user-defined-sql-not-permitted-user-who-has-identity-when-running-controller-standard-reports
https://www.ibm.com/support/pages/how-manually-create-cognos-data-source-use-controller-standard-reports

Product:
Cognos Controller 10.3.1
Microsoft Windows 2016

Problem:
User is stuck inside Excel when using the buttons for the controller add-in.

Solution:
Close excel and cognos controller clients.
Login to Cognos Controller as the user with the problem.


Click “Maintain / User / Personal Defaults > tab Layout (2)”
Untick the box ‘Save Window Size’
Click Save
Logoff from Controller, and re-launch the Controller client.

Go to Company – data entry – and try again.

More Information:
https://www.ibm.com/support/pages/controller-hangs-freezes-crashes-when-click-intercompany-details-button-inside-data-entry-company-journals-caused-save-window-size-setting
https://www.ibm.com/support/pages/troubleshooting-errors-user-xyz-already-logged-database-and-no-licence-available-moment
https://www.ibm.com/support/pages/user-xyz-already-logged-database-triggered-closing-excel-wrong-time-earlier-solved-using-exceleagerload

Product:
Cognos Controller 10.3.1 interim fix 13
Microsoft Windows 2012 server

https://www.ibm.com/support/pages/cognos-controller-builds-ccr-name-and-database-version

Problem:
After update with a interim fix to Cognos Controller, user get a error when start of a JAVA based dialog, like JOBS DEFINE or COMMAND CENTER.

Solution:
On the IIS manager, for the application folder CONTROLLERSERVER set to allow “Anonymous Authentication”, and only have “Windows Authentication” on virtual folder IBMCOGNOS or SSO.

 

More Information:
https://www.ibm.com/support/pages/node/1119885
https://www.ibm.com/support/pages/how-upgrade-controller-1031x-later-interim-fix-if-fix-pack-patch-level

Product:
Cognos Controller 10.4.2
Microsoft Windows server 2012 R2
Microsoft SQL Server 2016

Problem:
After restore of one old Cognos Controller database backup, you get this error when you try to create a SQL account for the database.

Error:
The server principal ‘fastnet’ already exists

Solution:
Go into Microsoft SQL Server Management Studio as Administrator
Mark your newly restored controller database
Expand the Tables and check the schema name (mostly it is fastnet)
Click on “New Query”
Past in this code (edit the name and update the ‘ to be correct symbol)
EXEC sp_change_users_login ‘Auto_Fix’, ‘fastnet’
Click on Execute.

The row for user ‘fastnet’ will be fixed by updating its login link to a login already in existence.
The number of orphaned users fixed by updating users was 1.
The number of orphaned users fixed by adding new logins and then updating users was 0.

This should create and update the SQL server with the account used for the controller database.

More information:
https://sqlserverbuilds.blogspot.com/
https://www.crestwood.com/2017/05/24/error-creating-new-sql-user-server-principal-already-exists/