Product:

IBM Cognos Controller 10.1

Windows 2008 server/Citrix Server for Controller Client

Microsoft Excel 2007

 

Symptom:

When user inside Cognos Controller click on Reports – Run, Microsoft Excel pop’s up and placed Excel spreadsheet in front of Cognos Controller.

This is irritating in a Citrix session, because it is difficult to switch back to Controller window.

 

Solution:

On the Citrix Server (Windows 2008 server) for the Cognos Controller client, you need to look into registry value below and change values for Excel to change this behavior.

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Microsoft\Office\12.0\Excel

 

If possible copy the registry values from a working Citrix server to yours server.

Product:

Cognos Controller 10.1

Windows 2008 R2

 

Symptom:

Get error when select maintain – manage active users from inside Cognos Controller client.

After we have changed the controller database.

 

Error message:

System.Web.service.Protocols.SoapException: Server was unable to process request. –>

System.Runtime.InteropService.COMException (0x80070070):

Method ‘~’ of object ‘~’ failed

at FrUserValidator.ValidatorClass.IsMenuItemAllowed(String sMenuIDs, String sMode, String sWebServiceAction)

at….

 

Possible Solution (workaround):

Restart the physical server.

Restart of the Cognos Controller services in Windows 2008 Server did not help.

This error is from the Component Services COM+ Applications.

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 TM1 9.5.2

Windows 2008 R2 Server

 

Symptom:

User can not access the TM1 Contributor web site and user can not run Cognos BI reports against TM1 data. But Architect can access the TM1 applications. The Apache TOMCAT service have stopped working.

IT department can not access the Windows 2008, server that run TM1, with Remote Desktop tools, they believe only solution is to reboot physical server.

 

Task Manager report that the Windows server have free memory and free cpu power.

Error message on TM1 server when you try to start notepad:

There is not enough free memory to run this program. Exit one or more programs, and then try again.

 

Possible Solution:

If you have tuned your TM1 application, it may be using features that is using windows system recourses more during heavy use than needed.

Remove the following parameter in your tm1s.cfg file:

LockPagesInMemory=T

or set it to

LockPagesInMemory=F

Then save the tm1s.cfg file

Update all tm1s.cfg file you have on your TM1 server.

Execute SaveAllData from inside TM1 Architect (to ensure no data is lost).

Restart the TM1 services from Windows services (to pickup the change in the tm1s.cfg file).

Monitor the TM1 server during heavy load to see if issue is solved.

 

More Information:

LockPagesInMemory=T locks the TM1 data in memory and take away system resources from the windows system to increase performance of TM1. But the Windows system will get lack of resources on a heavy used TM1 server, and therefore gradual stop the system from working.