CogKnowHow

Product:
Cognos TM1 version 9.5.1

This is a few old recommended actions to do at all Cognos TM1 installations.

1) Same folder structure in test and productions servers:
Recommended that you on the TM1 server create a folder named: tm1servers
Below that folder create a folder for each TM1 server you want to create;
• C:\tm1servers\tm1planning
• C:\tm1servers\tm1controller

By keeping the folder structure same on all TM1 servers it is easy to move scripts between the servers.

2) Create a separate folder for log files:
Below your TM1 folder for you custom TM1 server create a log folder named: LogFiles
Updatera din tm1s.cfg file med raden;
LoggingDirectory=C:\tm1servers\tm1planning\LogFiles

3) Create a separate folder for data files:
Below your TM1 folder for you custom TM1 server create a log folder named: DataFiles
Updatera din tm1s.cfg file med raden;
DataBaseDirectory=C:\tm1servers\tm1planning\DataFiles

To the data folder you should also create a copy of the tm1s.cfg file and place there as “copy of tm1s.cfg” file.

4) Create a script that saves the TM1 data to disc every day:

Go into TM1 Architect program as administrator.
Expand the TM1 application and go to processes tab.
Right click and select “create new process”
Go to the Advance tab
Go to the Prolog tab
Enter a blank row
Enter the statement
Savedataall;
Enter a blank row

Should look like this in prolog:
#****Begin: Generated Statements***
#****End: Generated Statements****
savedataall;

Click on the SAVE icon and name the solution to be SAVEDATA
Go to the Schedule tab
Click in “Schedule this Process as a Chore Named:”
Enter the name SAVEDATA
Enter 1 for run every 1 Days.
Check the local time to show 23:00:00
(this will make it to run every night)
Click on the SAVE icon

Select FILE – EXIT in Turbo Integrator to get back to TM1 Architect.
Then you should now have a process named SAVEDATA
And that chores named SAVEDATA.
Best to also create a TI process that copy the data folder to a different location as a backup.

5) Change the timeout for the TM1web:
On the TM1 server with IIS 6 from Windows 2003
Go to folder C:\Inetpub\wwwroot\TM1Web
Open web.config in notepad
Search for

Below system.web and before the line of <!—DYNAMIC DEBUG….. enter this line

Save and close the web.config file.
Restart the TM1 server and check that all is working.

Product:
TM1web version 9.5.1
Windows 2003 or 2008 x64 version

Symptom:
User attempts to export to PDF from TM1Web and receives an error.

Message:
Export in process, Please wait…
‘PDFcamp Printer’ was not installed properly

Cause:
PDF camp Printer was not installed properly – it needs to be default printer for that windows account that runs the TM1 Excel Service.

Solution:
Make sure that the PDFcamp Printer is set as default and then restart the TM1ExcelService, even if the printer was set as default.
If this does not resolve it, uninstall PDFCamp by using the 64-bit uninstaller executable at \bin\PDFcamp\unpdfxp64.exe
Then reinstall the PDFcamp Printer using the installer executable at \bin\PDFcamp\setupx64.exe.
Set the PDFcamp Printer as default and restart the TM1ExcelService again.

Product:
TM1 9.5.1 Contributor

Symptom:
Can not log into TM1 Contributor

Problem:
When logging into TM1 Contributor with integrated CAM authentication, after putting in your credentials you receive the following error: PRS-PRH-0221 The Portal/variables_plan.xml could not be opened.

Cause:
Two main reasons can be the source of this error:
1- The appropriate files have not been moved to the proper directory.
2- In a distributed environment, the files from the CAdmin folder in the TM1 installation directory are on the wrong server.

Resolving the problem
In a distributed Cognos environment where the Gateway and Application servers are on different machines:

1- Ensure that the pmpsvc.war file is on the C8\webapps folder on the Application servers.

2- Ensure that the planning.html, variables_plan.xml, and the icon_active_application.gif are in the C8\webcontent, C8\templates\ps\portal and C8\webcontent\ps\portal\images respectively on the Gateway server.

These files can be found under the TM1 install directory in the \Cadmin and \Cadmin\gateway folders.

NOTE:
If the gateway and dispatcher are on different servers, copy the variables_plan.xml to the dispatcher server.

3- Also, it is occasionally required that the CAMPortalVariableFile parameter in the tm1s.cfg file be changed from:
CAMPortalVariableFile=templates\ps\portal\variables_TM1.xml
to:
CAMPortalVariableFile=portal\variables_TM1.xml

Restart the TM1 server to activate the change in parameters.

Product:
Cognos TM1 10.2.2
Microsoft Windows 2012 R2 server

Symptom:
The TI function SCAN does not find a match of data in a variable in the TI process.
After checking with ASCIIOUTPUT found that the word is with small letters and we search for capital letters.

Cause:
The TM1 function SCAN is case sensitive.
Other functions that are case sensitive or space sensitive are;
TIMST are case sensitive. TIMST(366.0000, ‘\M \D, \Y’) returns ‘JAN 1, 1961’.
LONG and SUBST and Filter by Wildcard in subset editor is space sensitive.

Solution:
Add UPPER to your question.

Change from
nLOB = SCAN (‘_LoB’ , vITEM);
to
nLOB = SCAN (‘_LOB’, UPPER (vITEM));

More information:
From http://www.tm1forum.com/viewtopic.php?t=1683

Here are examples:
# Will return 4
l1 = Scan ( ‘def’, ‘abcdef’);

# Will return 0
l2 = Scan ( ‘def’, ‘ABCDEF’);

#Will return 0
l3 = Scan (‘def’, ‘a    b    c    d    e    f’);

# Will return Match
If ( ‘def’ @= ‘DEF’);
s1 = ‘Match’;
Else;
s1 = ‘No Match’;
EndIf;

# Will return Match
If ( ‘def’ @= ‘d e f ‘);
s2 = ‘Match’;
Else;
s2 = ‘No Match’;
EndIf;

#Proof
AsciiOutput (‘F:\Temp\Outputs.txt’, NumberToString (l1), NumberToString (l2), NumberToString (l3), s1, s2 );