CogKnowHow

Product:
Planning Analytics 2.0.3
IBM Cognos TM1 Applications
Microsoft Windows 2016 server

Issue:
When publishing a updated TM1 application in Performance Modeler to the TM1 Applications web (contributor web portal), the application is deleted.

Error can be:
[DeployApplicationThread:9b649fa9-1cf1-46f7-9bae-5f2fde393121] ERROR () com.ibm.cognos.pmpsvc.PMPService – deployApplication Throwable
com.ibm.cognos.pmpsvc.PMPSVCException: An exception occurred on the server. Please contact your system administrator. :com.ibm.cognos.pmpsvc.handler.PMPTM1Exception: TI_NODE_NOT_EXIST[CAMID(“CDS:u:uid=roger,ou=people,ou=eu”) | }tp_modify_application_attribute | }ElementAttributes_}tp_applications, BounceMode ] :EXCEPTION

Solution:
There is a chance that there are “left-overs” from a old application with similar name in the portal, therefor the application is deleted before a new is created. The first time you publish a TM1 application to a new PMPSVC (contributor) web server, you need to ensure there is not a old application there since a previous crash.

Before republishing a old TM1 10.2.2 application to a new PA 2.0.3 server do this;
— stop the TM1 instance windows service.
— erase the log folder for the tm1 instance.
— copy a new fresh data folder from the TM1 10.2.2 application.
— surf to http://paservername.domain.com:9510/pmpsvc and remove the old application with the same name from the list of applications. You do this from the TM1 applications configuration page. You must be ADMIN in the TM1 instance you try to remove.
Check in the file TM1InstallRoot\webapps\pmpsvc\WEB-INF\configuration\fpmsvc_config.xml that the application is not listed any more.
— stop the IBM Cognos TM1 windows service (tm1web and pmpsvc service).
— surf to Cognos Analytics http://caservername.domain.com/ibmcognos and go to Team Content – IBM Cognos TM1 Applications – My Applications. Remove the link to your published application. PM can not publish a application if there already exist on with the same name.
— start the IBM Cognos TM1 Windows service (pmpsvc service).
— start the TM1 instance, that you had issues with.
— Surf to http://paservername.domain.com:9510/pmpsvc and add the TM1 instance to the portal, and make it a application you can work with from PM tool.
— Log into Performance Modeler as a ADMIN in your TM1 application. Open up and see the application you have built before, validate the application first. Then try to publish it again.

If you have a working TM1 instance, then above should solve the issue, because you start from a fresh working data folder. There should not be any corrupt files you need to delete. Surf to http://paservername.domain.com:9510/pmpsvc to see if it worked.

More Information:
https://www.ibm.com/support/knowledgecenter/en/SS9RXT_10.2.2/com.ibm.swg.ba.cognos.tm1_inst.10.2.2.doc/c_tm1_inst_contrib_strtlnk.html

If you Run the }tp_admin_delete_all process from Architect, then all applications can be erased, and you may have to recreate them.

Product:
Planning Analytics 2.0.3
IBM Cognos TM1 Applications
Microsoft Windows 2016 server

Issue:
When user inside Cognos TM1 Applications (contributor) are reporting there numbers. Then they click on X to close the window, they get a error message: 54: ObjectNameInvalid, when they press OK the application exits as it should.

Only when you use CAM authentication.

Suggested Solution:
You are using Internet Explorer in wrong emulation mode.

Press F12.
Select Emulation.
Change Document mode to Edge or 10, from 11.
Go into the node again and test.

To get to TM1 Applications you surf to http://paservername.domain.com:9510/pmpsvc

This error can also be found if the name of the TM1 application is to long, so the total length of the temp files BLB is more than 255 characters on the Windows server. During start of the Contributor session a blb file is created with the user name as filename in the datafiles folder, if this file is not created (due to its name is to long), when you exit your Planning Analytics Contributor application you get above error, because TM1 can not find the file and erase it.  All work, but you get a irritating error.

Solution is to have TM1 instances installed with short names like d:\tm1server\112\datafiles or similar.

You can also find in the tm1server.log error like this NAME INVALID error and that causes TM1.Blob FileCreateOpenDelete.

Product:
Planning Analytics 2.0.3
Planning Analytics Workspace  (ipa_workspace_local_2.0.29.1080.2.zip)
Microsoft Windows 2016 server
Red Hat Linux server

Problem:
When inside PAW, and you try to expand a node of a TM1 instance, you get a error message.

Error:
Session can not be established for server proven_techniques 500 (internal server error) “code” “explorer” “refID” “message” .”Failed to get children for server cubes”. “cause”.”java.net.NoRouteToHostException: No route to host”.

Solution:
In one case this is because of DNS and routing problems in network. The PAW server and PA server have both two network cards, and can only communication on one of them.
You must in TM1S.CFG tell Tm1 instance what network card it should use.

Add the line
IPAddressV4=”10.200.30.40″
in TM1S.CFG and restart the TM1 instance.

Replace the ip number with the correct ip address of your Planning Analytics server.
Important that the IP address are inside ” double quotation mark.

Product:
Planning Analytics Workspace
Planning Analytics 2.0.3
Microsoft Windows 2016 Server

Problem:
When user surf to the PAW, they are not administrator and can not add other users.
Surf to http://pawservername.domain.com
Click on the user — and see there is not a option for Administration.
This is a new PAW setup with CAM authentications.

Solution:
The first users that you add in a TM1 instance as ADMIN will be admin in paw when you login to paw. Therefor you must add CAM users to a native TM1 instance first.

Open up a Tm1 application in Native mode. Like Proven_Techniques.
Open C:\Program Files\ibm\cognos\tm1_64\samples\tm1\Proven_Techniques\tm1s.cfg in notepad++.
Add the lines;
IntegratedSecurityMode=2
ServerCAMURI=http://caservername.domain.com:9300/p2pd/servlet/dispatch
ClientCAMURI=http://caservername.domain.com:80/ibmcognos/bi/v1/disp
Close TM1 architect.
Update the C:\Users\%username%\AppData\Roaming\Applix\tm1\tm1p.ini file with
AllowImportCAMClients = T
CognosGatewayURI = http://caservername.domain.com:80/ibmcognos/bi/v1/disp

Start PAW administration console and surf to http://pawservername.domain.com:8888
Setup like this (change to your servers name);
TM1 Admin Server URI: https://paservername.domain.com:5898
TM1 Application Server Gateway URI: http://paservername.domain.com:9510
Authentication Mode: TM1
TM1 Login Server URI: https://paservername.domain.com:5011
Click validate and update.

(This TM1 instance you point out with the HTTPport number is the instance that will define the first ADMIN in paw, even if you use security mode 5).

Start TM1 Architect and login to Proven_Techniques as Admin.
Go to Security – Client/Groups. From menu Clients select Add New Client.
Add your CAM user from your AD domain, that you want to be ADMIN in paw.
Mark the user to be ADMIN in TM1 Architect. Click OK.
Exit Tm1 Architect.

Open C:\Program Files\ibm\cognos\tm1_64\samples\tm1\Proven_Techniques\tm1s.cfg in notepad++.
Change; IntegratedSecurityMode=5
Save the file and restart the TM1 instance.
Now TM1 instance is using CAM authentication.

Update PAW admin console by surf to http://pawservername.domain.com:8888
TM1 Admin Server URI: https://paservername.domain.com:5898
TM1 Application Server Gateway URI: http://paservername.domain.com:9510
Change to Authentication Mode: CAM
Set IBM Cognos BI Gateway URI: http://caservername.domain.com:80/ibmcognos
Set IBM Cognos BI Dispatcher URI: http://caservername.domain.com:9300/p2pd/servlet/dispatch
Set IBM Cognos BI Authentication Namespace ID: AD
Click Validate and update.
Click on status tab – wait until CPU usage is below 1%.

Surf to http://pawservername.domain.com
Login as the CAM user you have given ADMIN rights in Proven_Techniques.
This user should now have a ADMINISTRATOR option under its name.

The list will only show name for people who have already try to login.

More Information:
https://www.ibm.com/support/knowledgecenter/en/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_prism_gs.2.0.0.doc/c_paw_administration_top_level.html