Troubleshooting
Problem
An issue is encountered which requires further insight into the underlying processing of an Insight report or application behavior.
Diagnosing The Problem
It is useful to enable debug tracing in situations like these to be able to provide the administrator, or support, with further information as to the exact issue being encountered.
Resolving The Problem
You can enable debug tracing in Cognos Insight with the following steps:
1) Go to the installation directory:
Windows XP - C:\Documents and Settings\<username>\Application Data\IBM\Cognos Insight
Windows 7 - C:\Users\<username>\AppData\Roaming\IBM\Cognos Insight - OR -
C:\Users\\AppData\Local\Programs\IBM\Cognos Insight\
2) Make a backup of provagent_NOT.ini and rename it to provagent.ini
3) Open provagent.ini in a text editor and uncomment the "app-debug=true"
4) Save the modified provagent.ini
The log file should be created in <cognos_insight>\logs\provagent_<timestamp>.log, and additional debug information will be logged to the normal CognosInsight_10.1_<timestamp>.log file.
provagent_<timestamp>.log will contain information regarding java arguments passed to the product upon startup as well as environment information (e.g. working directory and command used to launch Cognos Insight).
CognosInsight_10.1_<timestamp>.log should now contain additional entries prefaced by "[main] DEBUG". This will log the full of list of processing being done by the underlying TM1 server in relation to query processing, data retrieval (e.g. new files being used within Cognos Insight), and will also capture the MDX of queries being executed.
Was this topic helpful?
Document Information
More support for:
Cognos Insight
Software version:
10.1
Operating system(s):
Windows
Document number:
204517
Modified date:
15 June 2018
UID
swg21584324