Product:

Cognos Controller 10.1

Windows 2008 R2

Symptom:

When going into Cognos Controller Configuration and select Report server tab then the Controller Configuration program hang.

Cause:

During the upgrade with a interim fix for Cognos controller the web.config file in c:\Program Files (x86)\ibm\cognos\c10\ControllerProxyServer have been changed. The server name have been changed with local host values.

 

The report server value is stored in both web.config and registry on HKLM\Software\Wow6432Node\VB and VBA Program Settings\FrangoController\Shares\CRNPath

Problem arise when the values does not match.

 

Solution:

Open c:\Program Files (x86)\ibm\cognos\c10\ControllerProxyServer web.config in notepad

 

Change lines

<add key=”crnServer” value=”http://localhost/ibmcognos/cgi-bin/cognos.cgi”/>

<add key=”crnDisp” value=”http://localhost:9300/p2pd/servlet/dispatch”/>

 

to lines with correct server name

<add key=”crnServer” value=”http://servername.domain.com/ibmcognos/cgi-bin/cognosisapi.dll”/>

<add key=”crnDisp” value=”http:// servername.domain.com:9300/p2pd/servlet/dispatch”/>

 

Save the file

Open Windows task manager

Mark IBM Cognos Controller Configuration in Applications tab

Right click and select End Task

Start Cognos Controller Configuration program again.

Product:

Cognos Controller 10.1 RTM

Windows 2008 R2 server

Symptom:

When start Cognos Controller client for the first time, it stop at the WSSurl value.

To try to troubleshoot you surf to http://servername/ibmcognos/controllerserver/ccrws.asmx.

 

Error Message:

Server Error in ‘/ibmcognos/controllerserver’ Application.

 

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

 

Parser Error Message: Could not load file or assembly ‘stdole, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. The system cannot find the file specified.

 

Source Error:

Line 36:         <add assembly=”ADODB, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A” />

Line 37:         <add assembly=”MSDATASRC, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A” />

Line 38:         <add assembly=”stdole, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A” />

Line 39:         <add assembly=”Microsoft.StdFormat, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A” />

Line 40:       </assemblies>

 

Source File: E:\Program Files (x86)\ibm\cognos\c10\ControllerProxyServer\web.config Line: 38

 

Assembly Load Trace: The following information can be helpful to determine why the assembly ‘stdole, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ could not be loaded.

 

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure logging.

To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

 

Version Information: Microsoft .NET Framework Version:2.0.50727.5448; ASP.NET Version:2.0.50727.5456

 

Cause:

Missing file “stdole.dll” on application server

 

Solution:

Install SQL 2005 32 client on Controller Applications server, including Workstation components, Books Online and development tools.

 

Or upgrade to latest version of Cognos Controller

 

More Information:

https://www-304.ibm.com/support/docview.wss?uid=swg21509303

Product:

IBM Cognos Controller 10.1

Windows 7

Symptom:

When you start Cognos Controller Client (ccr.exe) you get a error message.

Error Message:

Invalid database version

This version of Controller requires database version: 851

 

Cause:

You have upgrade the Cognos Controller software on the server to a later version of Cognos Controller but have not upgrade the local ccr.exe client

 

Cognos Controller client software can work with different versions of Cognos Controller server software as long as they use the same database version.

 

Solution:

Uninstall the local Cognos Controller Client

Install the new Cognos Controller Client from the ccrlocalclient.msi file found on the Cognos Controller server in folder c:\Program Files (x86)\ibm\cognos\c10\webcontent\ccr

 

More Information:

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

Product:

Cognos Controller 10.1

Adobe Reader 10

Symptom:

When Cognos Controller user run a standard report, and it show fine in HTML.

Then user change to view it in Adobe Reader PDF format, then they only get a progress bar and the PDF does not show.

Problem:

PDF report does not show – user see a progress bar instead.

 

Cause:

Adobe Reader 10 is not supported by Cognos Controller 10.1

More information here

http://www-01.ibm.com/support/docview.wss?uid=swg27020782#eft

 

Solution:

Start Adobe Reader X on the client computer and under menu

edit – preferences

select general dialog

uncheck “Enable Protected Mode at startup”

click OK

Then start Cognos Controller Client, and test a standard report again.

 

This change is saved per user on the client, so the best is if the IT department can roll out this change of Adobe Reader with a GPO.

Product:

Cognos Controller 10.1

Symptom:

All users have access to all in Cognos Controller even due they should not because the users are entered and the security groups are created and applied inside Cognos Controller.

 

Problem:

Only the ADM user can inside Cognos Controller active or deactivate the Security System, from inside the dialog Maintain -Rights -users.

 

Cause:

When Cognos Controller is using Cognos BI authentication, the CAM users, then the first person to login to Cognos Controller at a new installation become the internal ADM user in Cognos Controller.

Other persons you add to Cognos Controller as Group Administrators can change users rights in the system, but not active Cognos Controller to use the Security settings.

 

Solution:

Log in to Cognos Controller as the ADM user.

This is the person that is shown as ADM user in MAINTAIN – RIGHTS -USERS dialog.

Go to MAINTAIN – RIGHTS -USERS dialog

In the lower left corner mark “Security Systems Enabled”

Click on SAVE icon

Exit Cognos Controller Client.

 

Recommended to do this the first time you login to Cognos Controller as ADM.

A person in Cognos Controller that is Group Administrator ( and part of the Cognos connection group controller administrators) can do all changes and security changes in the Cognos Controller application except only this on ( mark the “Security Systems Enabled”).

Product:

Cognos Controller 10.1

Windows 2008 server

Symptom:

After change of the database in Cognos Controller solution, the users are not able to run standard reports. They get a error message when the HTML page should show.

 

Error message:

AAA-AUT-0011

Invalid namespace was selected

(ogiltigt namnutrymme har valts)

 

Possible Solution:

Restart the Cognos Controller server including the Cognos BI services.

Note: that if you change the name of the database you need to update the Controller Configuration database connections of that change.

Also you must press the REPAIR button in controller configuration at the Report Server tab.

Product:

Cognos Controller 10.1.4801.127

Windows 2008 R2 Server

 

Symptom:

Error when you surf to cognos controller (cognos connection) website after you have applied Cognos Controller fix pack.

 

Error message:

HTTP Error 404.0 – Not Found

The resource you are looking for has been removed, had its name changed, or is temporarily unavailable. Detailed Error InformationModule IIS Web Core

Notification MapRequestHandler

Handler StaticFile

Error Code 0x80070002

Requested URL http://servername:80/cgi-bin/cognosisapi.dll?b_action=xts.run&m=portal/main.xts&startwel=yes

Physical Path C:\inetpub\wwwroot\cgi-bin\cognosisapi.dll

Logon Method Anonymous

Logon User Anonymous

 

Cause:

The content of the file default.htm and index.html in folder D:\Program Files (x86)\ibm\cognos\c10\webcontent are wrong.

 

Solution:

Open file default.html in notepad

Find section that contains:

 

function genMainContent()

                                    {

document.body.innerHTML = ‘<div align=”center”><img src=”‘ + splashImg.src + ‘” style=”position:relative; top:80px”></div>’;

window.setTimeout(“window.location.replace(‘../cgi-bin/cognosisapi.dll?b_action=xts.run&m=portal/main.xts&startwel=yes’)”,5);

                                    }

                        </script>

 

Remove the ../ part in front of cgi-bin so the section looks like this:

 

function genMainContent()

                                    {

document.body.innerHTML = ‘<div align=”center”><img src=”‘ + splashImg.src + ‘” style=”position:relative; top:80px”></div>’;

window.setTimeout(“window.location.replace(‘cgi-bin/cognosisapi.dll?b_action=xts.run&m=portal/main.xts&startwel=yes’)”,5);

                                    }

                        </script>

 

Save the file and exit notepad.

Do the same change in file index.html

Restart iis with the dos command iisreset.

 

Try to surf to the page again.

Product:

Cognos Controller 10.1.405

Windows 2008 R2 server

 

Symptom:

Consolidation in Cognos controller does not work after update.

If you look in the help – system info dialog inside Cognos controller client you see version number:

 

IBM Cognos Controller version: 10.1.405

Integration version: 0.0.0

 

Cause:

When integration version is showing zeros, then some part of the Cognos Controller has not been installed correct.

Correct value for integration version should be: 10.1.416.

 

Possible Solution:

On the Cognos Controller Windows server:

Launch a command prompt by clicking “Start” – “Run” and then typing in “CMD” <Enter>
Change directory using: cd C:\Windows\SysWOW64\common

Here is the file xceedzip, that maybe is not correct installed.

Register the file using: regsvr32.exe xceedzip.dll

 

Restart then the server.

 

Cognos Controller client version must be the same as the Cognos Controller version installed on the Application server.

 

More Information:

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

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

If you still have problems, remove the frangovfp com+ components and add them again.

Product:

Cognos Controller 10.1.405

Tm1 9.5.2

Windows 2008 R2 server

 

Symptom:

When doing a initial publish in Financial Analytics Publisher you get a error message that it can not login to the TM1 server cube.

This happen after you have upgrade Cognos Controller with a Fix Pack.

 

Error Message:

FAP Service Scheduler CRITICAL

Could not login to TM1, host: sr01639, server name: tm1fap, user name:  AD\username

If you keep the mouse over the error message you will see this message:

com/cognos/ccf/c8itk/ITKProxyJNI.jnIsLoggedOn(J)Z

Cause:

When using Cognos Controller with Cognos BI CAM security to TM1 version 9.5.2 you need to use the correct c8itk4j.jar file.

 

Solution:

Stop the Cognos FAP service.

Go to folder D:\Program Files (x86)\ibm\cognos\c10\server\FAP\lib

Rename the file c8itk4j.jar to c8itk4j.jar.old

Copy the c8itk4j.jar file from folder D:\Program Files (x86)\ibm\cognos\c10\server\FAP\lib\TM1_9.5_CAM_compatibility

You should now have c8itk4j.jar filesize to be 22 KB.

Start the Cognos FAP service.

Go the the datamarts tab in Financial Analytics Publisher and click start to test again.

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.