Product:

Cognos Controller 8.5.1532 FAP

Windows 2008

Cognos TM1 9.5.2

 

Symptom:

During IP for Controller FAP you get a error message that the FAP service can not login to the TM1 application. When you change client id and restart the FAP service, you get not error message, the FAP service is only hanging.

If you reboot the physical server, the FAP service will try to login once, and then fail.

There are no “fatalerror.log” in the FAP service folder on the server.

 

Background:

You have changed to use CAM ID and SSO to access Cognos Controller.

The servers and the users are in different Windows domains with trust between.

 

Error message:

Severity: CRITICAL

Description: Could not login to TM1, host: SERVERNAME, server name: TM1 SERVER NAME, user name: admin

If you hold the mouse over the error message in FAP manager, you see the text:

SystemServerNotFound

 

Cause:

The windows account that run the IBM Cognos Controller FAP server must be a domain account in the same domain that the Cognos BI server authenticate against. You must be able to surf to http://servername/cognos8 from the server logged in as the service account, and SSO should work.

 

Solution:

Create a new windows service account in the domain that contains the users

Make that new windows service account local admin on the FAP server

Change the windows account that start the FAP service, to use the new service account.

You may need to enter the account with domain\name in the field for name to the FAP service to make it possible for the FAP service to use the account.

Start FAP service again and test if the FAP publish works now.

In FAP Manager for the connection edit, ensure you enter the client name and domain in same capital letters as used for the namespace id in cognos configuration.  If the namespace ID is AD then you need to enter AD\username in the FAP manager for the TM1 connection.

Product:

Cognos BI 10.1.1

 

Symptom:

How do I change the Logo in Cognos Connection to be my company ?

 

Solution:

Download the company logo as a small GIF file.

In our example we call the company NIPPON, so save the gif file as NIPPON_logo.gif.

Go to your Cognos Gateway server, copy the folder \program files\ibm\cognos\c10_64\webcontent\skins\corporate and content to folder \program files\ibm\cognos\c10_64\webcontent\skins\NIPPON folder.

 

Place the NIPPON_logo.gif file in folder \program files\ibm\cognos\c10_64\webcontent\skins\NIPPON\branding.

 

Surf to your Cognos Connection.

Launch Cognos Administration.

Select Configuration tab.

Click on Styles (on the left side).

Click on the New Style icon (on the top right side).

Enter NIPPON as name and click next.

Enter NIPPON as Style resources location and click Finish.

 

Now you have your company NIPPON in the list of styles.

Click on icon for My area options (on the top right side).

Select My Preferences

From the drop down menu at Styles select your company NIPPON.

Click OK.

Click on HOME icon.

You account in Cognos Connection are now using the new style NIPPON.

But it look the same as corporate – because we have not changed anything.

 

Go to your Cognos BI report server.

Go to folder c:\program files\ibm\cognos\c10_64\templates\ps\portal

Make a backup copy of the file system.xml, name it system_org.xml.

Open your system.xml file in notepad.

Search for param name=”OEM”

 

………………………Below from original system.xml…………………….

 

<!– Custom OEM headers –>
<param name=”OEM”>
<!–
Specify custom Cognos Connection / Cognos Viewer left side header here in the form of XHTML snippets. Custom headers can be style-specific.
Example:
<customHeader showContext=”true” contextDelimiter=” – “>
<style styleFolderName=”corporate”>
<table style=”background-color:#ffffff”>
<tr>
<td><img src=”../skins/corporate/branding/my_logo.gif”/></td>
<td class=”headerTitle” style=”padding-right:2px;white-space:nowrap”> My company </td>
</tr>
</table>
</style>
<style styleFolderName=”classic”>
<table style=”background-color:#cccccc”>
<tr>
<td><img src=”../skins/classic/branding/my_logo.gif”/></td>
<td class=”headerTitle” style=”padding-right:2px;white-space:nowrap”> My company </td>
</tr>
</table>
</style>
</customHeader>

–>

</param>

 

……………………………………………………………………………..

Change above text to below instead;

<!– Custom OEM headers –>
<param name=”OEM”>
<customHeader showContext=”true” contextDelimiter=” – “>
<style styleFolderName=”NIPPON”>

<table style=”background-color:#fffff”>

<tr>

<td><img src=”../skins/NIPPON/branding/NIPPON_logo.gif”/></td>

 <td class=”headerTitle” style=”padding-right:2px;white-space:nowrap”></td>

 </tr>

  </table>         

</style>

</customHeader>

</param>

 

Save system.xml file in folder \program files\ibm\cognos\c10_64\templates\ps\portal\

Restart the IBM Cognos windows service on the Cognos BI report server.

 

Surf to Cognos Connection.

Go to my folders.

You should have the NIPPON logo in the top left corner.

Product:

Cognos BI 10.1.1

Windows 2008 R2

 

Symptom:

When you go to the administration dialog in Cognos Connection you get a error message.

 

Error message:

DPR-ERR-2088

The requested Server Group ‘<name>’ does not exist

 

Possible Cause:

One of the BI servers in the server group does not have all correct service set to true.

Check that the following IBM Cognos service are active:

Delivery service enabled

Event Management enabled

Presentation service enabled

 

Solution:

Open cognos configuration on the Cognos BI server

Check the cognos service – component properties

Set all component properties to true.

Save the configuration

Start the service

Surf to cognos connection

Remove the server group name from the BI dispatchers

Product:

Cognos BI 10.1.1

 

Problem:

How to move security settings from dev to prod environments ?

 

Cause:

If you export a deployment package with only directory content “include Cognos groups and roles” and set to “replace existing entries”.

Access permissions are set to “include access permissions” and “apply to new and existing entries”

External namespaces are set to “include references to external namespaces”.

Then only User, Groups and Roles are moved in that package.

Settings for Capabilities and User Interface Profiles are not moved in that package.

If a user or groups does not exist in the new environments LDAP, then that user or group is removed from the Cognos group. It does not show up.

So you can move all user and groups settings between environments to update groups and rolls security, and this will remove any previous users in the Cognos groups. You must exist Cognos Connection and login in again to see the updates of security, after you have imported the security package.

Remember to unselect the “include data sources and connections” in your deployment or you may lose your connections with the data sources.

Solution:

You need to deploy the whole content store with users to get the Capabilities and User Interface Profiles settings to come over to the new environment.

In Cognos BI 10.1.1 the folder System Administrators are merged, so any users or groups in that folder are not removed. Hopefully this save you from locking your out of the Cognos system by mistake.

This move is only recommended to do once, because it overwrites all reports and data sources.

If you want some other way of handle update of security in Cognos BI, it is recommended to create your own program with help of the Cognos SDK.

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

Product:

Cognos BI 10.1.1

Cognos TM1 9.5.2

Windows 2008 R2 Server

Symptom:

Some Cognos BI reports have stopped to work. They worked fine last month.

They give strange error about WebSphere, but this a Windows installation with default Cognos BI built-in tomcat engine.

Error Message:

CCL-BIT-0006

The connection closed before the request is processed. If you are using WebSphere Application Server, to reduce the frequency of this error, increase the Persistent Timeout parameter for the Web container transport chains in the administrative console. Increase the time in 10-15 second intervals until the error no longer or rarely occurs

Cause:

The error message is because the report process timeouts, but this can be of different issues.

In this case it is the TM1 application who disconnect the reports users process direct at start of the report.

If you time with a stop watch from you press RUN in the report after the prompt page, until the error message. If that is exactly 60 seconds, then it is Cognos BI that have time out.

You need to investigate further to find why the report does not work.

 

If the report is getting data from a TM1 cube, run the TM1TOP utility to that cube and monitor what happens when the report is run.

If you want to change the timeout value in Cognos BI – do this:

  1. Navigate to the <IBMCOGNOS home>/tomcat/conf directory
    2. Open server.xml
    3. Locate the following entry:

<!– Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 –>
<Connector className=”org.apache.coyote.tomcat4.CoyoteConnector” port=”9300″ minProcessors=”5″ maxProcessors=”75″ enableLookups=”true” redirectPort=”9443″ acceptCount=”100″ debug=”0″ connectionTimeout=”60000″ useURIValidationHack=”false” disableUploadTimeout=”true”/>
<!– Note : To disable connection timeouts, set connectionTimeout value
to -1 –>

–or–

 

<!– A “Connector” represents an endpoint by which requests are received

         and responses are returned. Documentation at :

         Java HTTP Connector: /docs/config/http.html (blocking & non-blocking)

         Java AJP  Connector: /docs/config/ajp.html

         APR (HTTP/AJP) Connector: /docs/apr.html

         Define a non-SSL HTTP/1.1 Connector on port 8080

    –>

    <Connector port=”9300″ protocol=”HTTP/1.1″

                   maxThreads=”500″

                   enableLookups=”true”

                   redirectPort=”9443″

                   acceptCount=”500″

                   debug=”0″

                   connectionTimeout=”60000″

                   disableUploadTimeout=”true”

                   maxHttpHeaderSize=”16384″/>


  1. Change the connectionTimeout value from 60000 to xxxxxx (in milliseconds)
    5. Save server.xml
    6. Restart Cognos BI service

If the TM1 cube is feed with data from Cognos Controller, any change to dimensions/accounts will be transferred over to the TM1 cube. If a report is built with the dimension name in Cognos Report Studio – that report will not know of the change of dimensions name, and stop working.

 

When the Cognos BI report ask for a field that does not exist, the TM1 Application disconnects the connection. And the Cognos BI Report will timeout.

 

Solution:

Run the report for different months – does it work for older months?

Make a copy of the Cognos BI report.

Remove parts of the Cognos BI report and run it again.

Repeat above until you find the part that is making the report not to work.

Check that value in the TM1 cube.

Have it changed since last month ?

 

Rebuild the report to contain correct fields/dimensions names.

Product:

IBM Cognos BI 10.1.1 64 bit version.

Microsoft Windows 2008 R2 standard server

with 24 GB of RAM and total of 8 cpu cores

(with hyper treading on it looks like 16 cpu cores in windows task manager)

Symptom:

How do I improve the Windows server for my Cognos BI solution ?

In most cases the Microsoft Windows server default values will do fine, but for some heavy loaded Cognos BI system you can gain better effect with this values.

 

Recommendation:

(There are other settings that also will help out)

Change the maximum memory in MB to 6000 for IBM Cognos Configuration Resource Properties. This is found in Cognos Configuration on the BI server.

Standard value is 768, but on a 64 Bit Windows server with more memory this should be increased.  But not above total memory in server. The new Cognos BI 10.1.1 uses more memory for the JAVA and DQM functions than earlier versions. Also the new Cognos BI 10.1.1 64 bit version can handle more memory. By default, the IBM Cognos service is configured to use minimal memory resources to optimize startup time.

 

The value Set the maximum memory used by the JVM.

Usually, the memory is set by adding or changing the initial and maximum Java heap size.

 

The JAVA heap size used by the Query service is set from cognos connection admin portal now.

Go to Administer Cognos Content

Go to configuration – dispatcher

Click on the dispatcher e.g. server name in the list

Click on the MORE for the Query service

Click on set properties

Click on settings

Change the value for JVM heap size limit for the query service (MB) to 4096.

Click OK


Logging

Logging for a production environment needs to be set to Basic level.

Check this by go to cognos connection

Launch Cognos Administration

Click on configuration and on dispatcher

Click on MORE for the BI server you want to check

Click on set properties

Click on settings

Change category to logging

Check that all values are set to BASIC

 

Ensure that there is no mark for:

Audit the native query for batch report service

Audit the native query for report service

 

After you changed any value click OK to save the change.


TCPIP ports

The following registry keys need to be set on all Windows Server that host Cognos BI components. These will increase the number of available sockets, as well as reduce the time for the Windows OS to free sockets up, once they are not in use anymore.

After the change a reboot is required for the Windows server.

 

Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters

Add key: MaxUserPort

use Dword

Set Decimal to 65536

Add key: TcpTimedWaitDelay

use Dword

Set Decimal to 30

Only change in registry if you know how to do it with the REGEDIT program.


Add the following CM advanced parameter to Content Manager:

CAMSEARCHDEFERREDLOCKING = true

 

This parameter will ensure that not the whole authentication namespace gets locked by 1 user when it comes to complex, long running queries against the authentication source.

 

Surf to Cognos Connection

Launch Cognos Administration

Click on status and on system

Click on CM server

Click on the CM server dispatcher to get a list of all services

Click on arrow for ContentManagerServer and select set properties

Click on settings

Click on EDIT for Environment  Advanced settings

Mark Override the settings acquired from the parent entry

Now you get a grid to enter new values.

Enter CAMSEARCHDEFERREDLOCKING in left column.

Enter True in right column.

Click OK.

Click OK


Cognos TOMCAT

Making sure that Tomcat does not run out of threads under load.

open up the following file in notepad:

<c10 location>\tomcat\conf\server.xml

Look for the following line:

 

<Connector port=”9300″ protocol=”HTTP/1.1″

                   maxThreads=”500″

                   enableLookups=”true”

                   redirectPort=”9443″

                   acceptCount=”500″

                   debug=”0″

                   connectionTimeout=”60000″

                   disableUploadTimeout=”true”

                   maxHttpHeaderSize=”16384″/>

 

Change it as follows:

<Connector port=”9300″ protocol=”HTTP/1.1″

                   maxThreads=”1000″

                   enableLookups=”true”

                   redirectPort=”9443″

                   acceptCount=”1000″

                   debug=”0″

                   connectionTimeout=”60000″

                   disableUploadTimeout=”true”

                   maxHttpHeaderSize=”16384″/>

 

maxThreads=”1000″ and acceptCount=”1000″ is increased on system for many users.

Save the file and restart the Cognos BI service to make the changes take affect.


Change Number of report processes / low affinity connections in cognos connection to use more of the hardware with Cognos BI. Recommendation is to lower Number of low affinity connections for the report service during peak period to 2 from default 4.

 

Rule of thumb:

2 report processes per core, with 2 low affinity each = 16 processes * 2 low affinity = 32 low affinity in total.

 

On a combined GW / report server, reduce this to 1 process per core, with 2 low affinity each = 8 processes * 2 low affinity = 16 low affinity in total.

For our exampel server with 8 cpu cores then the settings should be on a pure report server, set the number of processes to 16, and the number of low affinity connections to 2.

On a combined GW / report server with 8 cpu cores, set the number of processes to 8, and the number of low affinity connections to 2.

 

So you need to increase the value for “Maximum number of processes for the report service during peak period” in most modern servers.

Go to Cognos Connection

Click on status and on system

Click on BI report server

Click on arrow for the BI server and select set properties

Click on settings

Change category to tuning

Go to “Maximum number of processes for the report service during peak period”

by click on the arrow in top right of screen.

Set Maximum number of processes for the report service during peak period

to 16.

Above you find “Number of low affinity connections for the report service during peak period”

Set Number of low affinity connections for the report service during peak period

to 2.

Click OK

 

On the first page for category tuning settings:

Go to “Queue time limit of the report service (seconds)”

Change the value for Queue time limit of the report service (seconds)

from 240 to 360, to allow more time to collect data from data layer to the report.

Click OK

Do not change the other values for non-peak period from default settings.

Do the same changes for all the Cognos BI servers.

Product:
Cognos BI 10.1.1

Symptom:
Why do we get so many fails in the Presentation service ?
You can see number of fails in Cognos connection web portal if you go to;
Launch Cognos Administration
Click on status tab
Click on system
On the top right side you can expand the metrics
and find the Request – Presentation service
Note the Number of failed requests

Cause:
Presentation Service metrics deal with logons, display of reports and display of content (admin page/main portal page/portlets) within the portal.

If you have a user that for some reason are entering invalid userid/password information when trying to logon to the IBM Cognos portal, then this will be recorded as a failed presentation request and will show up as a failed request on the Presentation service. For this example, there may be 4 failed presentation requests generated. Users that cancel a report just as it is about to
be displayed will also register a failed presentation service request.

A high failure rate on Presentation service can probably be caused by the reinitialization of the XTS validation. (“PRS-PRO-0511 A partial reinitialization of the XTS processor is required.”) While the dispatcher is at the idle state, the XTS validator sends request out in a certain period for “health check” on dispatcher communication. If no other active you should find 2 failure
requests in Presentation service and then 3 XTS reinitialization from the log file.

“PRS-PRO-0511 A partial reinitialization of the XTS processor is required.” is the text to look for in cogserver.log file.

Solution:
The key thing is to do some baseline analysis of the metrics that are captured over a typical day (good day) or a typical week (good week) to see the # of request failures on average. Then knowing this and also understanding that the system was able to handle the running of
reports/jobs without any issues (errors or slow run times of reports) during the day or the week, you can adjust your thresholds to look for abnormally high failure rates above the typical failure rates in a good day or week.

So, it is important that you do not set thresholds that are two high/low depending on the metric being measured especially if the metric is measuring things such as failed logons or cancelled report runs.

More Information:
The system performance metrics are gathered from the individual services (batch, presentation service etc.) that are running and processing requests and summarized in the Administration page of IBM Cognos. The information is not stored in the audit database or the cogserver.log but within the content store database itself.

The intended workflow for investigating failed requests is to check the cogserver.log file and use the information there to identify the cause. If one opens the log using the /bin/logviewV2.exe tool then you can filter the log file to only show the entries for the service of interest. Failed requests are highlighted in red and from there you can get the details on what request(s) failed, and the associated messages and error codes can direct you to potential root cause for the failures. Additionally, the errors can then be searched (www.google.com) on in Cognos knowledge base for a TechNote that will help resolve the issue.

If it is still not clear why the request failed or what action to take to resolve the issue after that, you should then seek further assistance from Customer Support.

Product:

Cognos BI 10.1.1

Framework Manager

Oracle 11g

 

Symptom:

Data source connection in Cognos Connection is working.

Framework Manager is installed on a workstation.

But when you connect to a Oracle data source you get a error message.

Error Message:

QE-DEF-0285 The logon failed.
QE-DEF-0323 The DSN(ODBC)/ServiceName is invalid. Either the DSN is missing or the host is inaccessible.
RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in:
FM1
UDA-SQL-0031 Unable to access the “FM1” database.
UDA-SQL-0532 Data Source is not accessible: “DRPDB”.
ORA-12154: TNS:could not resolve the connect identifier specified

 

Above is when tnsnames.ora is missing.

 

Other error message:

QE-DEF-0285 The logon failed.
QE-DEF-0323 The DSN(ODBC)/ServiceName is invalid. Either the DSN is missing or the host is inaccessible.
RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in:
FM1

UDA-SQL-0432 Unable to locate the gateway “cogudaor”.

Above is when oracle client folder is not in windows path.

 

Solution:

Ensure you have installed the full 32 bit Oracle 11g administrator client on the computer where Cognos FrameWork Manager is installed. Framework Manager only works with the 32 bit Oracle client.

 

Ensure that you have the added the path to the bin folder of the Oracle client to windows system path e.g. \oracle\product\11.2.0\client_1\bin.

The path can be pointing to a old Oracle client installation, ensure the BIN folder exist in the path.

 

Ensure that the tnsnames.ora file is updated and contain the reference to the oracle database that is used in cognos connection. Best is to copy the tnsnames.ora file from the Cognos BI server to workstation where you have Cognos Framework manager installed. Place the tnsnames.ora file in folder \oracle\product\11.2.0\client_1\network\admin\.  Ensure that tnsnames.ora file is in the oracle client folder that is in use, and that are referenced from the path variable.

 

Exit Framework manager program before you test again, to ensure the changes have taken affect.

 

More information:

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

Product:

IBM Cognos BI 10.1.1

Windows 2008 R2 server

Microsoft SQL 2008 database server

 

Symptom:

Error when you run a report or test data source in Cognos connection.

Query Mode

Microsoft SQL server (SQL 2005 Native Client) /Compatible…. Failed

Microsoft SQL server (JDBC) / Dynamic………………………………. Succeeded

 

Error message:

QE-DEF-0322 The connection string is invalid.RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in: great_outdoors_sales UDA-SQL-0031 Unable to access the “great_outdoors_sales” database. Check that the connection parameters to the database are configured correctly. For example, ensure that the data source connection contains the signon information, such as a password, to connect to the database.UDA-SQL-0534 Invalid connection string.UDA-SQL-0206 The OLEDB driver returned the following value: HRESULT= -2147221164″.RSV-SRV-0042 Trace back:RSReportService.cpp(722): QFException: CCL_CAUGHT: RSReportService::process()RSReportServiceMethod.cpp(263): QFException: CCL_RETHROW: RSReportServiceMethod::process(): reportEditQuery_RequestRSASyncExecutionThread.cpp(808): QFException: RSASyncExecutionThread::checkExceptionRSASyncExecutionThread.cpp(260): QFException: CCL_CAUGHT: RSASyncExecutionThread::runImpl(): reportEditQuery_RequestRSASyncExecutionThread.cpp(864): QFException: CCL_RETHROW: RSASyncExecutionThread::processCommand(): reportEditQuery_RequestExecution/RSRenderExecution.cpp(670): QFException: CCL_RETHROW: RSRenderExecution::executeAssembly/RSDocAssemblyDispatch.cpp(291): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssemblyAssembly/RSLayoutAssembly.cpp(79): QFException: CCL_RETHROW: RSLayoutAssembly::assembleAssembly/RSDocAssemblyDispatch.cpp(358): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchChildrenAssemblyForwardAssembly/RSReportPagesAssembly.cpp(179): QFException: CCL_RETHROW: RSReportPagesAssembly::assembleAssembly/RSDocAssemblyDispatch.cpp(308): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssemblyAssembly/RSPageAssembly.cpp(303): QFException: CCL_RETHROW: RSPageAssembly::assembleAssembly/RSDocAssemblyDispatch.cpp(308): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssemblyAssembly/RSTableRowAssembly.cpp(177): QFException: CCL_RETHROW: RSTableRowAssembly::assembleAssembly/RSDocAssemblyDispatch.cpp(308): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssemblyAssembly/RSTableCellAssembly.cpp(137): QFException: CCL_RETHROW: RSTableCellAssembly::assembleAssembly/RSDocAssemblyDispatch.cpp(358): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchChildrenAssemblyForwardAssembly/RSDocAssemblyDispatch.cpp(308): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssemblyAssembly/RSAssembly.cpp(662): QFException: CCL_RETHROW: RSAssembly::createListIteratorAssembly/RSAssembly.cpp(717): QFException: CCL_RETHROW: RSAssembly::createListIteratorRSQueryMgr.cpp(1055): QFException: CCL_RETHROW: RSQueryMgr::getListIteratorRSQueryMgr.cpp(1131): QFException: CCL_RETHROW: RSQueryMgr::getResultSetIteratorRSQueryMgr.cpp(1295): QFException: CCL_RETHROW: RSQueryMgr::createIteratorRSQueryMgr.cpp(1569): QFException: CCL_RETHROW: RSQueryMgr::executeRsapiCommandRSQueryMgr.cpp(1559): QFException: CCL_RETHROW: RSQueryMgr::executeRsapiCommandRSQueryMgrExecutionHandlerImpl.cpp(168): QFException: CCL_RETHROW: RSQueryMgrExecutionHandlerImpl::execute()RSQueryMgrExecutionHandlerImpl.cpp(160): QFException: CCL_RETHROW: RSQueryMgrExecutionHandlerImpl::execute()QFSSession.cpp(1147): QFException: CCL_RETHROW: QFSSession::ProcessDoRequest()QFSSession.cpp(1145): QFException: CCL_CAUGHT: QFSSession::ProcessDoRequest()QFSSession.cpp(1102): QFException: CCL_RETHROW: QFSSession::ProcessDoRequest()QFSSession.cpp(1078): QFException: CCL_RETHROW: QFSSession::ProcessDoRequest()QFSConnection.cpp(788): QFException: CCL_RETHROW: QFSConnection::ExecuteQFSQuery.cpp(213): QFException: CCL_RETHROW: QFSQuery::Execute v2CoordinationQFSQuery.cpp(2024): QFException: CCL_RETHROW: QECoordinationQFSQuery.cpp(4350): QFException: CCL_RETHROW: CoordinationQFSQuery::CallProviderQFSQuery.cpp(246): QFException: CCL_RETHROW: QFSQuery::EXecute v3Source/RQP_QFSQuery.cpp(492): QFException: CCL_RETHROW: QESource/QE_RsApi.cpp(3604): QFException: CCL_RETHROW: QESource/QE_RsApi.cpp(3552): QFException: CCL_RETHROW: QESource/QEI_ConnectionFault.cpp(814): QFException: CCL_THROW: QE

 

Cause:

Have only installed the JAVA SQL driver (sqljdbc4.jar) on the Cognos BI servers.

Solution:

Install the Microsoft SQL native client on the Cognos BI servers.

Run sqlncli_x64.msi as administrator on the Cognos BI server.

Download the driver from Microsoft

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17943

Product:

Cognos BI 10.1.1

Cognos Tm1 9.5.2

 

Symptom:

When starting TM1 architect , or when surf to Cognos Connection, they are not allowed to login,

 

Error message:

Exception occurred: java.lang.IncompatibleClassChangeError

Error in cogserver.log file:

10.240.17.54:9300      980      2012-01-09 09:47:41.171       +1        na        na                                Thread-93       DISP    6235    1          Audit.Other.dispatcher.DISP.pogo            pogo    com.cognos.pogo.contentmanager.coordinator.ActiveCMControl               Failure <messages><message><messageString>DPR-DPR-1035 Dispatcher detected an error.</messageString></message><message><messageString>DPR-DPR-1004 Expecting a BI Bus XML response but got:   &lt;html&gt;&lt;head&gt;&lt;title&gt;Apache Tomcat/6.0-snapshot – Error report&lt;/title&gt;&lt;style&gt;&lt;!–H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}–&gt;&lt;/style&gt; &lt;/head&gt;&lt;body&gt;&lt;h1&gt;HTTP Status 500 – &lt;/h1&gt;&lt;HR size=&quot;1&quot; noshade=&quot;noshade&quot;&gt;&lt;p&gt;&lt;b&gt;type&lt;/b&gt; Exception report&lt;/p&gt;&lt;p&gt;&lt;b&gt;message&lt;/b&gt; &lt;u&gt;&lt;/u&gt;&lt;/p&gt;&lt;p&gt;&lt;b&gt;description&lt;/b&gt; &lt;u&gt;The server encountered an internal error () that prevented it from fulfilling this request.&lt;/u&gt;&lt;/p&gt;&lt;p&gt;&lt;b&gt;exception&lt;/b&gt; &lt;pre&gt;javax.servlet.ServletException: Content Manager has not been started. com.cognos.cm.server.ContentManager.notStartedResponse(ContentManager.java:569)             com.cognos.cm.server.ContentManager.doPost(ContentManager.java:137)             javax.servlet.http.HttpServlet.service(HttpServlet.java:637)             javax.servlet.http.HttpServlet.service(HttpServlet.java:717)             com.cognos.pogo.isolation.ServletWrapper.service(ServletWrapper.java:258) &lt;/pre&gt;&lt;/p&gt;&lt;p&gt;&lt;b&gt;note&lt;/b&gt; &lt;u&gt;The full stack trace of the root cause is available in the Apache Tomcat/6.0-snapshot logs.&lt;/u&gt;&lt;/p&gt;&lt;HR size=&quot;1&quot; noshade=&quot;noshade&quot;&gt;&lt;h3&gt;Apache Tomcat/6.0-snapshot&lt;/h3&gt;&lt;/body&gt;&lt;/html&gt;</messageString></message></messages>            DPR-CMI-4007 Unable to perform an active Content Manager election on the local IP node. For more information, see the dispatcher and Content Manager detailed logs. Ensure that the local Content Manager service is started.DPR-DPR-1004 Expecting a BI Bus XML response but got: <html><head><title>Apache Tomcat/6.0-snapshot – Error report</title><style><!–H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}–></style> </head><body><h1>HTTP Status 500 – </h1><HR size=”1″ noshade=”noshade”><p><b>type</b> Exception report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>The server encountered an internal error () that prevented it from fulfilling this request.</u></p><p><b>exception</b> <pre>javax.servlet.ServletException: Content Manager has not been started. com.cognos.cm.server.ContentManager.notStartedResponse(ContentManager.java:569)            com.cognos.cm.server.ContentManager.doPost(ContentManager.java:137)            javax.servlet.http.HttpServlet.service(HttpServlet.java:637)            javax.servlet.http.HttpServlet.service(HttpServlet.java:717) com.cognos.pogo.isolation.ServletWrapper.service(ServletWrapper.java:258)</pre></p><p><b>note</b> <u>The full stack trace of the root cause is available in the Apache Tomcat/6.0-snapshot logs.</u></p><HR size=”1″ noshade=”noshade”><h3>Apache Tomcat/6.0-snapshot</h3></body></html> com.cognos.pogo.bibus.CommandExecutionException: DPR-DPR-1004 Expecting a BI Bus XML response but got: <html><head><title>Apache Tomcat/6.0-snapshot – Error report</title><style><!–H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}–></style> </head><body><h1>HTTP Status 500 – </h1><HR size=”1″ noshade=”noshade”><p><b>type</b> Exception report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>The server encountered an internal error () that prevented it from fulfilling this request.</u></p><p><b>exception</b> <pre>javax.servlet.ServletException: Content Manager has not been started. com.cognos.cm.server.ContentManager.notStartedResponse(ContentManager.java:569)            com.cognos.cm.server.ContentManager.doPost(ContentManager.java:137)            javax.servlet.http.HttpServlet.service(HttpServlet.java:637)            javax.servlet.http.HttpServlet.service(HttpServlet.java:717) com.cognos.pogo.isolation.ServletWrapper.service(ServletWrapper.java:258)</pre></p><p><b>note</b> <u>The full stack trace of the root cause is available in the Apache Tomcat/6.0-snapshot logs.</u></p><HR size=”1″ noshade=”noshade”><h3>Apache Tomcat/6.0-snapshot</h3></body></html>          at java.lang.Throwable.<init>(Throwable.java:80)             at java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:77)             at com.cognos.pogo.bibus.CommandExecutionException.<init>(CommandExecutionException.java:32)             at com.cognos.pogo.bibus.BIBusCommand.handleDefaultException(BIBusCommand.java:292)             at com.cognos.pogo.bibus.BIBusCommand.execute(BIBusCommand.java:194)             at com.cognos.pogo.contentmanager.StandbyContentManagerElectionCommand.executeIfLocal(StandbyContentManagerElectionCommand.java:53)             at com.cognos.pogo.contentmanager.coordinator.ActiveCMControl.sendElectCommand(ActiveCMControl.java:239)             at com.cognos.pogo.contentmanager.coordinator.ActiveCMControl.access$100(ActiveCMControl.java:31)             at com.cognos.pogo.contentmanager.coordinator.ActiveCMControl$ElectTask.safeRun(ActiveCMControl.java:250)             at com.cognos.pogo.util.threads.SafeTimerTask.run(SafeTimerTask.java:32)             at java.util.Timer$TimerImpl.run(Timer.java:293) Caused by: com.cognos.pogo.bibus.CommandExecutionException: DPR-DPR-1004 Expecting a BI Bus XML response but got: <html><head><title>Apache Tomcat/6.0-snapshot – Error report</title><style><!–H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}–></style> </head><body><h1>HTTP Status 500 – </h1><HR size=”1″ noshade=”noshade”><p><b>type</b> Exception report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>The server encountered an internal error () that prevented it from fulfilling this request.</u></p><p><b>exception</b> <pre>javax.servlet.ServletException: Content Manager has not been started. com.cognos.cm.server.ContentManager.notStartedResponse(ContentManager.java:569)            com.cognos.cm.server.ContentManager.doPost(ContentManager.java:137)            javax.servlet.http.HttpServlet.service(HttpServlet.java:637)            javax.servlet.http.HttpServlet.service(HttpServlet.java:717) com.cognos.pogo.isolation.ServletWrapper.service(ServletWrapper.java:258)</pre></p><p><b>note</b> <u>The full stack trace of the root cause is available in the Apache Tomcat/6.0-snapshot logs.</u></p><HR size=”1″ noshade=”noshade”><h3>Apache Tomcat/6.0-snapshot</h3></body></html>          at java.lang.Throwable.<init>(Throwable.java:80)             at java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:77)             at com.cognos.pogo.bibus.CommandExecutionException.<init>(CommandExecutionException.java:28)             at com.cognos.pogo.bibus.BIBusCommand.checkResponseContentType(BIBusCommand.java:314)             at com.cognos.pogo.bibus.BIBusCommand.getSinglePartInputStream(BIBusCommand.java:273)             at com.cognos.pogo.bibus.BIBusCommand.getInputStream(BIBusCommand.java:259)             at com.cognos.pogo.bibus.BIBusCommand.parseResponse(BIBusCommand.java:249)             at com.cognos.pogo.bibus.BIBusCommand.processResponse(BIBusCommand.java:242)             at com.cognos.pogo.bibus.BIBusCommand.executeCommand(BIBusCommand.java:204)             at com.cognos.pogo.bibus.BIBusCommand.execute(BIBusCommand.java:190)             … 6 more

 

Fast workaround:

Restart the Cognos BI server or service.

Go to administrative tools on the Windows 2008 server.

Go to services

Find IBM Cognos in the list

Right click and select Restart

Wait 5 minutes and try again

 

Possible Solution:

In a multi server installation of Cognos BI

Ensure that Content Manager is active on all servers where it is installed.

Go into Cognos Configuration

Go to IBM Cognos Services

Set TRUE after Content Manager Service enabled?

Save

Exit and restart the Cognos Bi service.

Repeat on all servers.

 

The primary dispatcher used in a Cognos BI multi server solution must be on a Cognos BI server where the application layer is installed.