Problem:
TM1 Architect is connecting the TM1 applications on the wrong network card on the Microsoft Windows server.

Possible solution:
The default network card with the lowest metric value is selected from all network cards to be the default network card. Use Get-NetIPInterface to see metrics.

Start Powershell on the Windows server
Enter: Get-NetIPInterface
This will list the network interfaces on the server.
Check the value for ifIndex and InterfaceMetric (A low value indicates a higher priority.)
The card with lowest value for InterfaceMetric will be used by TM1.
Is this the correct one? or is it for a backup network?

Problem:
In a Planning Analytics (TM1) environment where native security is used, you get a error when you try to add content to workspace from the PA databases on left side of screen.

Error Message:
unable to fetch data for content tree. Session can not be established for server: BUDGET 401 (Unauthorized) (“errorMessage”.””.”query”.”https://…..

Possible Solution:
Log out from Workspace
Go into TM1 Architect.
Set a password for all users, do not use blank (empty) as a password. That will not work for workspace. Also ensure that the ADMIN account have a password like apple.

After the user have a password set, exit TM1 Architect and surf to Planning Analytics Workspace again.

Solution:
Start PUTTY and login to the Linux server
Enter sudo -su to a root user.
Go to the ../paw folder.
Go to the /paw/config folder.
Enter more paw.env to see the settings used in Planning Analytics Administration Tool listed on screen. They are saved to this file paw.env
Enter nano paw.env to be able to edit the file.
Change the IBM Cognos BI Gateway URI and IBM Cognos BI Dispatcher URI fields, to both end with /bi/v1/disp

Two lines in paw.env should look like this;export IBMCognosGatewayURL=”http://caservername.domain.com:80/ibmcognos/bi/v1/disp”export IBMCognosServlet=”http://caservername.domain.com:9300/bi/v1/disp”

Press CTRL+X to exit the NANO editor in linux.
Press Y to save the changes to paw.env file.

In the paw/scripts folder enter ./paw.sh down to stop the PAW services.
In the paw/scripts folder enter ./paw.sh to load the PAW services again.
In the paw/scripts folder enter ./paw.sh start to start the PAW services.
Wait 10 minutes.
Surf to http://pawservername.domain.com to test if it works.

This change can also be done in the Planning Analytics Administration Tool, but then you first need to turn off SSO in IIS and change to security mode 1 in tm1s.cfg file.

Troubleshoot:
Use the scripts/paw.ps1 script instead of Administration tool from power shell prompt.
Enter scripts/paw.ps1 to ensure all services are running and up-to-date.
Enter scripts/paw.ps1 ps to see status of all services.

Above may show that you have a pa-gateway already running.
Check that no other application is using port 80 and 443.
Start IE on the server and surf to http://localhost/ – what does that give?

Stop all PAW with scripts/paw.ps1 down
Then start it again with scripts/paw.ps1

Did it help?

Enter docker ps -a to see all running containers. Any duplicates?
Then to remove a container enter docker stop <container-id> ; then docker rm <container-id>.

Check the log files in folder D:\install\paw\log\pa-gateway\error.log
If you see this; AH00558: httpd.exe: Could not reliably determine the server’s fully qualified domain name, using fe80::5db7:f898:8a1:858c. Set the ‘ServerName’ directive globally to suppress this message. Then that is nothing to be concerned about.

You can recreate the docker network with below commands (try this first):
Stop the docker service: stop-service docker
Make sure the hns service is running: start-service hns
Now run this PowerShell command: get-containernetwork | remove-containernetwork
Start the docker service again: start-service docker

If it still doesn’t work, you can also try the same steps except with get-netnat | remove-netnat:

Stop the docker service: stop-service docker
Make sure the hns service is running: start-service hns
Now run this PowerShell command: get-netnat | remove-netnat
Start the docker service again: start-service docker

After that is done, go to the d:\install\paw\scripts folder in power shell.
Start the PAW with ./paw.ps1 start.

Check the file D:\install\paw\config\paw.ps1 contain the values you have set in the administration tool before. Should look similar to this;
# paw.ps1 file generated by the Administration Tool
$env:TM1Location=”https://labwin2012ca.lab.local:5898″
$env:TM1ApplicationsLocation=”http://labwin2012ca.lab.local:9510″
$env:PAAuthMode=”tm1basic”
$env:TM1LoginServerURL=”https://labwin2012ca.lab.local:8010″

Surf to servername to see if paw is working e.g. http://labwin2012ca.lab.local/

To get more detail debug info on screen,
stop the docker service.
Run the Docker daemon in debug mode:
C:\Program Files\Docker\dockerd -D

April 26, 2018 by Roger·Comments Off on IIS version 7.0 or greater is required to install Microsoft External Cache

Product:
Cognos Analytics 11.0.10
Microsoft Windows 2016 Server

Issue:
When you try to install the ExternalDiskCache_amd64_en-US.msi you get a error.

Error Message:
IIS version 7.0 or greater is required to install Microsoft External Cache Version 1 for IIS 7

Workaround:
You can resolve this problem by modifying registry.

Open run dialog and enter regedit, to open the Registry Editor.
Find MajorVersion in the path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters.
Open the value MajorVersion and select Decimal radiobutton.
Change Its value from 10 to 9.
Click OK.

Issue:
When you in powershell run ./Start.ps1 from paw_2.0.4_win16_ml folder you get a error.

Error message:
unable to invoke ‘docker-compose’. Ensure docker-compose is installed and is on the PATH

Possible solution:
Check that the file docker-compose.exe exist in folder c:\program files\docker
Enter PATH at a DOS prompt to check that c:\program files\docker is part of your path string.
In a DOS prompt enter DOCKER-COMPOSE VERSION, do you get a message that
‘docker-compose’ is not a recognized as an internal or external command, operable program or batch file?
Go to the docker folder with command cd \program files\docker and try the DOCKER-COMPOSE again.
Same error, try enter DOCKER-COMPOSE.EXE. Does that work?
If you get a list of possible docker commands, it works.
But the DOCKER-COMPOSE.EXE file can be corrupt.
Erase the DOCKER-COMPOSE.EXE file and copy a new file to the docker folder.
Rename the new DOCKER-COMPOSE-Windows-x86_64.exe file to DOCKER-COMPOSE.EXE and try again to enter only DOCKER-COMPOSE.
If that works, and you get a list of commands, then the file was corrupt.
Please try ./Start.ps1 again from your powershell session.

Possible Solution:
Port 9510 is not open in the local Windows Firewall on the server.
Go to Control Panel
Go to Windows Firewall
Go to Advanced Settings
Click on Inbound Rules
Click on New Rule
Select Port and click Next
At Specific local ports enter 80,443,9510,5495,5498,8888, 12345,12354,53333,5011,12346,8010 and click Next. The last port numbers depend on what you have set in your tm1s.cfg file.
Click Next at Allow the connection
Click Next when the rule apply for all (Domain, Private, Public)
Enter a name like Cognos TM1 and click Finish
Check the validate again.

Issue:
When you in PA Workspace Administration Tool click on validate you get a error for TM1 Admin Server URI.

Error Message:
Error: connect ECONNREFUSED 127.0.0.1 443

Possible Solution:
The text you have entered in the field for TM1 Admin Server URI is not correct.
You have installed PA and PAW on a Windows server you have named DonaldDuck.
In the field you have entered:
https:/donaldduck.domain.com:5898

Note that you have missed one / at the https:/ point where it should be https://