by ·Comments Off on Failed to populate the authentication

Product:
Cognos Analytics 11.1.7
Microsoft Windows 2019 Server

Issue:
After change to use HTTPS in Cognos Configuration, you get a error when you save.

[Populate authentication settings] [ WARNING ] Failed to populate the authentication settings to server

Solution:
When change values in Cognos Configuration that have with certificates, you need to first stop the “IBM Cognos” windows service.
Then you can save the configuration without warnings.

 

More Information:

To active Cognos internal certificate, you need to inside Cognos Configuration on your Content Manager server change HTTP to HTTPS under environment – group properties.
Check that server FQDN is at Cognos – Cryptography ;DNS names and Server common name.
Save will create the certificate files.

Start CMD, and move to folder C:\Program Files\ibm\cognos\analytics\bin
Run this to export the Cognos certificate
ThirdPartyCertificateTool.bat -E -T -p NoPassWordSet -r ca.cer

Start MMC on your Windows server where Cognos Gateway is installed, and certificates and go to “Trusted Root Certification Authority”. Right click to Import certs.
Select the ca.cer file and import it.

Inside IIS manager, go to \ibmcognos\bi folder and click on URL Rewrite icon.
Click on Reverse proxy Rules to edit.
At action properties – Rewrite URL: change the http to https

https://servername.domain.com:9300/bi/{R:0}
Click apply in the right corner.
Exit IIS manager.

On PA server open Command Prompt as an Administrator and navigate to the \bin64\ directory.

Execute the following command to import/trust the certificate for Tm1 admin:
gsk8capicmd_64 -cert -add -db “C:\Program Files\ibm\cognos\tm1_64\bin64\ssl\ibmtm1.kdb” -stashed -label caRoot -file “C:\Program Files\ibm\cognos\tm1_64\bin64\ssl\ca.cer” -format ascii -trust enable

Go to \bin64\jre\bin\ to import it to PMPSVC java keystore.
keytool.exe -import -trustcacerts -file “C:\Program
Files\ibm\cognos\tm1_64\bin64\ssl\ca.cer” -keystore “C:\Program
Files\ibm\cognos\tm1_64\bin64\ssl\tm1store” -alias caRoot -storepass applix

You need also to add the ca.cer file to the correct keystore for TM1WEB.

 

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

Configure Planning Analytics 2.0 TM1 Server with SSL Cognos BI Dispatcher (ibm.com)

How to Configure Planning Analytics to Connect to an SSL Secured Cognos Dispatcher (ibm.com)

Configuring TM1 Server to trust the SSL certificate on CA Side (ibm.com)

https://www.ibm.com/support/pages/configuring-ibm-cognos-analyticsbi-https-enabled-web-server

https://www.ibm.com/docs/en/cognos-analytics/11.0.0?topic=components-configuring-ssl-cognos

by ·Comments Off on an authentication error has occurred

Product:
Microsoft Windows 2019 server

Issue:
Problem to connect to Remote Desktop from old laptop.

Solution:

Newer Microsoft Windows server has the possible to harden the communication, to not use old security protocols, then it will not allow connections from Windows 2012 or Windows 7 computers.

Try to connect from a Windows 10 computer with the latest service packs.

 

More information:

https://support.microsoft.com/en-us/topic/microsoft-security-advisory-update-for-disabling-rc4-479fd6f0-c7b5-0671-975b-c45c3f2c0540

https://support.microsoft.com/en-us/topic/rc4-cipher-is-no-longer-supported-in-internet-explorer-11-or-microsoft-edge-f8687bc1-1f88-9abe-5c81-b00c26290f36#bkmk_more

https://death-to-ie11.com/

https://www.syvik.com/multidesk/documentation.en.html

by ·Comments Off on Missing icons after import of content store

Product:
Planning Analytics 2.0.9
Cognos Analytics 11.1.7
Microsoft Windows 2019 server

Issue:
After import of the full content store to a new installed Cognos server, the icons for Tm1 App Web (PMPSVC) is not working.

Solution:
The old Cognos BI 10 solution may have used SKINS for the users.
Check the old server in folder d:\program files\ibm\cognos\c10_64\webcontent\skins for any unique folders that you do not have in your new cognos server. Copy that unique folder over to d:\program files\cognos\tm1_64\webapps\pmpsvc\skins folder.
Looks like the new TM1 needs the old custom skins files to work.

You can also click on icon for My Preferences and change Style to “modern” and click OK.

Below the default style skins that come with the product. If you have more folders in your Cognos BI installation, then they should be copied over to the new cognos server.

More information:
Inside Cognos Analytics – Administrator page – if you are only see text and miss the icons and color, it is possible the same issue, you need to copy the company unique skins folder to the new server.

https://www.cognoise.com/index.php?topic=32055.0

What you’re seeing is related to content (images and css files) not being found.
The person who has selected a custom skin as their default will get this.

If your custom skin is named MyCustomSkin, which doesn’t exist on the Cognos Analytics server.

On the Cognos Analytics server…
Copy <install_location>\webcontent\skins\corporate to <install_location>\webcontent\skins\MyCustomSkin.
Copy <install_location>\webcontent\bi\skins\corporate to <install_location>\webcontent\bi\skins\MyCustomSkin.

No restart is required. Once these are in place, the browser will find the styles and images and Cognos Analytics will be functional and more aesthetically pleasing.

https://www.ibm.com/support/pages/changing-skins-cognos-8-cognos-connection

https://www.ibm.com/support/pages/unable-see-icons-banner-tm1-contributortm1-applications