Product:
IBM Cognos TM1 10.2.2
PLANANALYTICS_Update_version=PLANANALYTICS-AW64-ML-RTM-10.2.5250.191-0
Windows 2012 R2 server

Symptom:
When try to run the test script to call a Java code from a TI process outlined here
http://www.ibm.com/support/knowledgecenter/en/SS9RXT_10.3.0/com.ibm.swg.ba.cognos.tm1_turb.10.3.0.doc/t_ti_configure_eclipse_java_ee_ide.html
get an error in the TI process.

Error message:
Error: Prolog procedure line (11): Errors occurred during execution of process “my.scripts.MyTestTI”. Check error log file for that process for more details

…java.lang.ClassNotFoundException…

Solution:

Check the tm1serverlog file for text like this;
2472 [] INFO 2016-07-25 13:30:30.643 TM1.Process [com.ibm.cognos.tm1.jos.extensions.ExtensionManager] – Insert new extension: C:\Program Files\ibm\cognos\tm1_64\bin64\javaextensions\user\myextension.jar
2472 [] ERROR 2016-07-25 13:30:31.018 TM1.Process [com.ibm.cognos.tm1.jos.extensions.JarFileExtensionRecord] – Extension has invalid extension.xml: C:\Program Files\ibm\cognos\tm1_64\bin64\javaextensions\user\myextension.jar
org.xml.sax.SAXParseException: Premature end of file.
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
at com.ibm.cognos.tm1.jos.extensions.ExtensionXml.parseFromXML(ExtensionXml.java:86)
at com.ibm.cognos.tm1.jos.extensions.JarFileExtensionRecord.load(JarFileExtensionRecord.java:83)
at com.ibm.cognos.tm1.jos.extensions.ExtensionManager.insertExtension(ExtensionManager.java:96)
at com.ibm.cognos.tm1.jos.extensions.LocalJarRepository.scan(LocalJarRepository.java:72)
at com.ibm.cognos.tm1.jos.extensions.ExtensionManager.addRepository(ExtensionManager.java:51)
at com.ibm.cognos.tm1.jos.Main.addLocalRepository(Main.java:156)
at com.ibm.cognos.tm1.jos.Main.main(Main.java:127)

This mean that the jar file is corrupt.
Stop your TM1 application and then from the JAVA IDE recompile the file with ANT.
This is done by save the project after a small change.
Remember to stop the TM1 application service before any change to the jar file.

It is good to only have the jar file in one folder, in the example it should be in folder for your Tm1 application, can be like this:
C:\Tm1apps\Tm1Beginner\data\}javaextensions\user

More information:
https://www.ibm.com/developerworks/community/forums/html/forum?id=9cd3aebf-c4bb-4059-91f1-9f0925b6b959&ps=25#topicsPg=1

Product:
Cognos TM1 10.1.1
Microsoft Windows 2012 server

Problem:
Error when saving in TM1 Cognos Configuration, after adding a new TM1 server.

Error message:
[ ERROR ] The cryptography information was not generated.
or
[Validation]
[ ERROR ] CAM-CRP-1064 Unable to process the PKCS #7 data because of an internal error. Unable to find the encryption certificate with alias ‘encryption’ in the keystore ‘D:/Program Files/ibm/cognos/tm1_64/configuration/encryptkeypair\jEncKeystore’.
The parameter named ‘User ID and password’ located in ‘TM1 Application Server’ is currently invalid.

Possible solution:
In the Cognos configuration, remove the TM1 server you are trying to add…or re-add.

This is for TM1 10.1.1
Then save the configuration in plain text.
Select File – Export to clear text file
Select a folder to save the file in, like d:\temp
Name the file to cogstartup_backup.xml
Stop the Cognos TM1 servers (including IBM Cognos TM1 Application Server) on that physical server.
Close the TM1 configuration.
Go to the following install folder: Driver_letter:\Program Files\ibm\cognos\tm1_64\configuration.
Rename the CSK, SIGNKEYPAIR, and ENCRYPTKEYPAIR folders (add _old after the name).
Rename the cogstartup.xml to cogstartup.xml.old
Copy the file d:\temp\cogstartup_backup.xml to folder \Program Files\ibm\cognos\tm1_64\configuration\
Rename cogstartup_backup.xml to cogstartup.xml
Open the Configuration tool.
Click save, to test that it works now.
This should allow the encryption files to be recreated.
Then add your TM1 server and save your settings.

Below how to update the keys for CA11 or PA2 Local:

Steps to regenerate the cryptographic keys are as follows:
1. Stop the running of your service in Cognos Configuration.

2. On the Content Manager computer, click ‘File > Export As’.

3. Choose ‘Yes’ at the prompt and save the file. For example, name it ‘backup.xml’ which will be stored in the c11\configuration folder.

4. Close Cognos Configuration.

5. On the Content Manager computer, create a backup of the following files and directories before moving them to a different, secure location (as during the cryptographic keys regeneration process they will be re-created):

The files are:

· c11/configuration/cogstartup.xml

· c11/configuration/caSerial

· c11/configuration/certs/CAMCrypto.status

· c11/configuration/certs/CAMKeystore

· c11/configuration/certs/CAMKeystore.lock

· c11/temp/cam/freshness
The directory is

· c11/configuration/csk

6. In the c11\configuration folder, rename ‘backup.xml’ to ‘cogstartup.xml’.

7. Open Cognos Configuration, save the configuration and start the services.

More Information
http://www-01.ibm.com/support/docview.wss?uid=swg21648832

http://www-01.ibm.com/support/docview.wss?uid=swg21995088

http://www-01.ibm.com/support/docview.wss?uid=swg21694322

Product:
Cognos TM1 10.2.2
Windows 2012 R2 server

Symptom:
When try to login to TM1 Application web (pmpsvc) you get an error 500 message.
To surf to TM1WEB is works fine, and you can enter the TM1 application from TM1 architect.

Error message:
HTTP Status 500 –
type Exception report
message java.lang.NullPointerException
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: java.lang.NullPointerException
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:502)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:430)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

root cause
java.lang.NullPointerException
com.ibm.cognos.fpmsvc.config.FPMConfig.getResourceManager(FPMConfig.java:612)
com.ibm.cognos.fpmsvc.exception.FPMSVCException.getMessageText(FPMSVCException.java:93)
com.ibm.cognos.fpmsvc.exception.FPMSVCException.getMessageText(FPMSVCException.java:89)
com.ibm.cognos.fpmsvc.exception.FPMSVCException.(FPMSVCException.java:30)
com.ibm.cognos.fpmsvc.session.FPMSessionManager.checkSessionPassport(FPMSessionManager.java:555)
com.ibm.cognos.fpmsvc.session.FPMSessionManager.checkSessionPassport(FPMSessionManager.java:439)
org.apache.jsp.applications_jsp._jspService(applications_jsp.java:188)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:388)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

note The full stack trace of the root cause is available in the Apache Tomcat/6.0.35 logs.
Apache Tomcat/6.0.35

Solution:
On the TM1 server – stop the IBM Cognos TM1 Application server.
In windows explorer go to folder C:\Program Files\ibm\cognos\tm1_64\webapps\pmpsvc\WEB-INF\configuration\

Rename the file fpmsvc_config.xml to fpmsvc_config.xml.old
Rename the file fpmsvc_config.xml.new to fpmsvc_config.xml
Start the IBM Cognos TM1 Application server.

Surf to http://localhost:9510/pmpsvc
And enter new TM1 applications to the server.

The file fpmsvc_config.xml can have been corrupt when you added a new TM1 instance.

Product:
IBM Cognos TM1 10.2.2
Microsoft Windows 2012 R2 Server
Sterling Integrator / Connect Direct

Problem:
When calling a BAT file from a TM1 TI process, to call other program, to send files or other systems task.
You get not the result you wanted.
The BAT file works fine when run direct in DOS prompt, and then the job get done.
But when called from a TI process – there are no errors – but the job is not executed.

Example of TI code to call a BAT file:
SIpath = ‘C:\cdroot\processer\PW188\PW188.bat’;
ExecuteCommand ( SIpath, 0);

Possible solution:
On the Microsoft Windows 2012 server create this two folders (if they do not exist):
C:\Windows\System32\config\systemprofile\Desktop
C:\Windows\SysWOW64\config\systemprofile\Desktop

This folders are needed when you run Applications without a user logged in, in Windows.

Product:
Cognos TM1 10.2.2
PLANANALYTICS_Update_version=PLANANALYTICS-AW64-ML-RTM-10.2.5240.167-0
Microsoft Windows 2012 R2 Server

Problem:
Error message when surf to PMHUB at http://windowsserver.domain.se:9510/pmhub/pm/admin

Error message:
HTTP Status 500 – Servlet.init() for servlet equinoxbridgeservlet threw exception

Solution:
Go to IBM Cognos Configuration for TM1 on the server.
Right click on TM1 Applications server and select STOP.
(You can also stop the IBM Cognos TM1 Application server from the Windows Services)
Delete folder pmhub at C:\Program Files\IBM\cognos\tm1_64\tomcat\work\Catalina\localhost\pmhub
Start TM1 Applications Server from inside IBM Cognos Configuration program.

This will recreate the application in TOMCAT and it will work again.

When you apply a FIX PACK to TM1 you must;
Stop the services.
Delete the config.ini file found in folder C:\Program Files\IBM\cognos\tm1_64\tomcat\work\Catalina\localhost\pmhub\eclipse\configuration\
Open Cognos Configuration and click SAVE.
Then you can start the TM1 services again.

Product:
IBM Cognos TM1 10.2.2
Microsoft Windows 2008 R2 Server

Problem:
How to setup CAFE to work with SSO and TM1.

Download Cognos CAFE from here
http://www-01.ibm.com/support/docview.wss?uid=swg24036964

Download the latest Service pack from here
http://www-01.ibm.com/support/docview.wss?uid=swg24041748
You can install the CAFE fix pack direct on you workstation.

Solution:
Setup Cognos BI to work with AD login with SSO.
Setup TM1 to work with AD login in the application.

Check to ensure the TM1 cam files are on the BI server;
Logon to the Cognos BI server
Ensure that file \templates\ps\portal\variables_tm1.xml contains the values to point to the TM1 server.

If you have a older version of Cognos BI than of Cognos TM1, then you may need to do this step:
In Windows Explorer, navigate to the following directory: ‘\webapps\pmpsvc\gateway_files\’
Extract the ‘planning_gateway.zip’ file, and copy the ‘/webcontent/pmhub.html’ file from within
In Windows Explorer, navigate to the following directory: ‘\webcontent\’ and paste the copied ‘pmhub.html’ file.

Open pmhub.html in notepad and change to the server name to that of the TM1 server.
(For all SSO to work, you need to update the right files on the Cognos BI server to point to your Cognos TM1 server. Check other instructions to get SSO to work with Cognos TM1)

Setup the values in PMHUB for the CAFE client.
Launch the PMHub via the following URL: http://yourservername.domain.com:9510/pmhub/pm/admin/
On the left hand side, expand ‘com.ibm.ba.pm.resource.security’. Then, click ‘com.ibm.ba.pm.resource.security.dictionary’ to open the properties pane.
In the properties pane on the right hand side, configure any of the server related URIs to match your own.
Exit the PMHub

On the Client computer ensure that Microsoft NET framework 4 is installed, this is needed for CAFE client.
Also ensure that Primary Interop assemblies are installed with Office on the workstation.
To install the PIAs when you install Office;

Ensure that you have a version of the .NET Framework that is no older than 2.0.

Install Microsoft Office and make sure that the .NET Programmability Support feature is selected for the applications you want to extend (this feature is included in the default installation).

Install the CAFE program on the client by running \install\download\cor_win32_10.2.5250.21_ml.tar\win32\issetup.exe
This will install the CAFE program in your Excel installation.

In Microsoft Excel you must allow the plug in, to get it to work.

Run script to update file in folder C:\Users\%username%\AppData\Local\Cognos\Office Connection
The file is CommManagerSettings.xml

Content to change are

<?xml version=”1.0″ encoding=”utf-16″?><Servers><Server Dll=”Framework.Provider.TM1Rest.dll” gateway=”http://donaldduck:9510″ friendlyname=”KALLETM1″ /></Servers>
True
False
False
300
True

Other files in folder are;
COCSettings.xml
CommManagerSettings.xml
Config.xml
FrameworkSettings.xml

Update below script with your name and the setting for SSO, paste it into NOTEPAD on server and save it as CAFEUPDATE.PS1

$path = ‘C:\Users\username\AppData\Local\Cognos\Office Connection\CommManagerSettings.xml’

(
(Get-Content $path )| Foreach-Object { $_ -replace ‘True‘, ‘False‘ } | Set-Content $path
)

You cannot edit the SERVERNAME with above script. Get-Content works only on a row at a time. You need to create something that can search and replace in the whole file.

Here is some help:
http://windowsitpro.com/scripting/replacing-strings-files-using-powershell

You can use any script tool to update the CommManagerSettings.xml file with your company settings. Use the tool you are familiar with.
Good Luck.

Error message in CAFE when you click Login;
error 404 = wrong value in PMHUB, misspelled server name or use of cognos.cgi
If you still have issues, then it may be needed changes in IIS to make SSO to work.

More Information:
http://www.cogknowhow.com/index.php/knowledge-articles/61-ibm-cognos-tm1/585-how-to-setup-sso-against-active-directory-with-tm1-and-cam-security
http://www-01.ibm.com/support/docview.wss?uid=swg27041505#tab_1022FP4
http://www.ibm.com/support/knowledgecenter/SSHM9K_10.2.2/com.ibm.swg.ba.cognos.ig_cxr.10.2.2.doc/c_ug_cor_trblshtng_config_issues.html%23ug_cor_trblshtng_config_issues
https://powershell.org/forums/topic/edit-ini-files/

Product:
IBM Cognos TM1 10.2.2 CAFÉ
Cognos for Microsoft Office

Problem:
In Citrix we have Microsoft Excel installed with English menu, but when a Swedish user login to Citrix server session, and then regional settings are in Swedish, and then the CAFÉ menu inside Excel are in Swedish. How do I change the Cognos Analysis For Excel to be in English?

Solution:
CAFÉ menu dialog is controlled by Regional Settings.
You need change the Regional Settings to English to get English menu in CAFÉ.

If it is not desirable, you can change the name of the folder where the Swedish language files are, so the CAFÉ program will default to the English menus. Then you can keep local language in Regional Settings.

On the Citrix server change the folder c:\program files (x86)\ibm\cognos\cognos for Microsoft office\sv to be sv_notused.

Product:
TM1 9.4 on MS Server 2003 with IIS6

Symptom:
ERROR Applix.TM1.Web.Page.TM1WebPageUtils –

Problem:
A problem occurs when TM1Web session is terminated after (x) minutes and user must login repeatedly.
TM1Web session is terminated after 20 minutes with message “Session timed out. Please login again”.
TM1Web keeps timing out despite increasing TM1 Web Session Timeout.

Cause:
Timeout parameter in web.config and IIS worker process are defined with Default Parameter.
(Web Session Timeout=20 min, IdleConnectionTimeOutSeconds=120 sec, IdleTimeout=20 min).

Timeouts can be configured at three different “levels” (TM1Web & TM1 Server & MS IIS):
1. TM1Web timeout settings – web.config, tm1web web app
2. TM1 Server timeout settings – tm1s.cfg
3. MS IIS settings for timeout of worker processes – IIS w3wp.exe + DefaultAppPool + machine.cfg

The setting in the tm1s.cfg file applies at the server level, while the web.config applies to accessing the virtual directory for TM1Web.
The IdleConnectionTimeOutSeconds will disconnect a user’s TM1 session, while the timeout parameter in the web.config only applies to a user’s connection to the TM1Web website.

Unexpected timeouts may occur when Default Parameter is changed or “Precedence of settings” is causing unexpected behaviour. The setting in the web.config file takes precedence over idle timeout in IIS and machine.config. When timeout is missing in web.config then setting from machine.config takes precedence.

Solution:
To prevent a TM1Web session from timing out configure your Timeout Parameter according to business requirements and “precedence of timeout settings” (best practice is not to change the default parameters).
Check web.config and tm1s.cfg file timeout parameter information. Check if you have a setting in your tm1s.cfg as it could be impacting your timeout if you do (note that no entry = never timeout). IdleConnectionTimeOut Seconds specifies a timeout limit for idle client connections, in seconds.For example, if you include the line IdleConnectionTimeOutSeconds=900 in tm1s.cfg, the server disconnects idle client connections after 900 seconds.

Timeout Parameter in TM1 & Microsoft IIS & TM1Web
0. Increase timeout IdleConnectionTimeOutSeconds (tm1s.cfg) from 900 sec to 7200 sec (= 120 min)
1. Increase timeout of IIS worker process from sec (=20 min) to 7200 sec (= 120 min)
cscript %SystemDrive%\Inetpub\AdminScripts\adsutil.vbs set W3SVC/AppPools/ApplicationPoolName n
2. Increase timeout DefaultAppPool from default 20 min to 120 min
3. Increase timeout TM1 Web Session (web.config) from default 20 min to 120 min
4. httpRuntime executionTimeout=”7200″ (web.config)
6. restart IIS after changing timeout settings

Another category of Session Timeouts, the ones where immediately after logon (or a short time later) the Session Timeout hits the user, is due to the default setting in IIS Version 6 webserver of MS Windows Server 2003:
Go to Control Panel -> Administrative Tools ->IIS Manager -> Application Pool -> Default Application Pool (DefaultAppPool) -> right mouse click to open context menu, selectProperties -> tab Performance -> Web Garden: Maximum number of worker processes -> Change from default value of 4 to 1.

On newer version of TM1 this settings are elsewhere, because TM1 do not use IIS.

Product:
Cognos TM1 9.5.1 web and contributor

Symptom:
You can not login to the TM1web when you are using the Cognos 8 security

Cause:
To allow users to successfully log in to TM1 Web when a TM1 server uses IBM Cognos 8 authentication, a variables_TM1.xml file must be present in the c8_location\templates\ps\portal directory. The variables_TM1.xml file must be configured to include the URL of the web server used to deliver TM1 Web

The variables_TM1.xml file is included as part of the TM1 Viewer Portlets installation

Solution:
Unpack the C8_TM1_Portlets_win32_x.x.x.x.tar  file to it´s own folder.

Run the setup.exe from that folder to install the portlets on the Cognos BI servers.

Open file variables_tm1.xml in folder c:\Program Files\cognos\c8\templates\ps\portal

Add the URL to the TM1 server in the file, like below:

<urls>

<url>http://tm1servername/tm1web/TM1WebLoginHandler.aspx</url>

<url>http://tm1servername/tm1web/TM1WebMain.aspx</url>

<url>http://servername.domain.se/tm1web/TM1WebLoginHandler.aspx</url>

<url>http:// servername.domain.se/tm1web/TM1WebMain.aspx</url>

</urls>

Save the file and restart the Cognos BI services.

Please note that you must also in the TM1 cube file tm1s.cfg change these parameters;

IntegratedSecurityMode=5

.

ServerCAMURI=http://biservername:9300/p2pd/servlet/dispatch

ClientCAMURI=http://biservergatewayname/cognos8/cgi-bin/cognos.cgi

ClientPingCAMPassport=900

CAMPortalVariableFile=portal\variables_TM1.xml

Product:
Cognos TM1 9.5.2
Microsoft Windows 2008 R2 server

Symptom:
User have to login to TM1 again after they have been away from the computer

Cause:
Unexpected timeouts may occur when the Default Parameter is changed or when the precedence of settings results in unexpected behavior. The setting in the web.config file takes precedence over idle timeout in IIS and machine.config. When timeout is missing in web.config then the setting from machine.config takes precedence.

For best results, do not change the default settings. To prevent a TM1Web session from timing out, if you do change the default setting, take into account your business requirements and the precedence of timeout settings.

To diagnose a timeout problem, be sure a setting has been made in the tm1s.cfg. No timeout setting means you never time out.

IdleConnectionTimeOut Seconds specifies a timeout limit for idle client connections in seconds. For example, if you include the line IdleConnectionTimeOutSeconds=900 in tm1s.cfg, the server disconnects idle client connections after 900 seconds.

Solution:
Increase the different time out values in the Cognos solution to two hours;

1)
Go to the folder for you TM1 application
Open tm1s.cfg in notepad
Increase timeout IdleConnectionTimeOutSeconds (tm1s.cfg) from 900 sec to 7200 sec (= 120 min).
Save the tm1s.cfg file.
Restart the TM1 application service from inside TM1 Architect.

(if the TM1 cube is to be used with Controller FAP recommendion to increase the value to IdleConnectionTimeOutSeconds=36000)

2)
Start Internet Information Service (IIS) manager and click on default web site.
On the right side click on Limits to open “Edit Web Site Limits” dialog.
Enter 7200 as value for “Connection timeout ( in seconds )”
Click OK

3)
Click on Application Pools
Click on the application pool used by cognos (cgi-bin) and the DefaultAppPool
On the right side click on Advance Settings
Change Idle-time out (in minutes) from 20 to 120.
Click OK

4)
Edit Web.config in the c:\inetpub\wwwroot\TM1Web folder.
Locate the following code:

<!–  SESSION STATE SETTINGS

By default ASP.NET uses cookies to identify which requests
belong to a particular session.
If cookies are not available, a session can be tracked
by adding a session identifier to the URL.
To disable cookies, set sessionState cookieless=”true”.

–>

<sessionState
mode=”InProc”
stateConnectionString=”tcpip=127.0.0.1:42424″
sqlConnectionString=”data source=127.0.0.1;Trusted_Connection=yes
cookieless=”false”
timeout=”120″
/>

Change the timeout value (in minutes) from 20 to 120.
Save Web.config.

5)
Open web.config and find executionTimeout

<system.web>

<!– asp.net request execution timeout, compilation debug must be set to false –>

<httpRuntime executionTimeout=”110″ />

change the value to “7200” instead of “110” seconds.
Save Web.config

6)
Increase timeout of IIS worker process from sec (=20 min) to 7200 sec (= 120 min) with:

cscript %SystemDrive%\Inetpub\AdminScripts\adsutil.vbs set W3SVC/AppPools/ApplicationPoolName n

7)
Inside Internet information service (IIS) manager
Click on the ibmcognos folder (or tm1web folder)
Double-click on CGI to configure CGI time-out settings
Change behavior time-out (hh.mm.ss) from 00:15:00 to 02:00:00
Click on Apply

Restart IIS after changing timeout settings.