CogKnowHow.com - Cognos Knowledge Place | Links Documenation Forum Tips and Tricks

Home

Main Menu

first

last

start

stop

Countries

49.3%		United States
7.4%		India
6.9%		United Kingdom
5.2%		Australia
5.1%		Canada

Visitors

Today:	258
Yesterday:	589
This Week:	1379
Last Week:	2850
This Month:	8992
Last Month:	12457
Total:	543223

Recently Added Articles

How to apply fix packs for Cognos

Problem:

which steps are required to install fix packs on an existing IBM Cognos installation.

Solution:
Since fix packs involves modified binaries, they need to be linked and working all in conjunction with each other. You cannot have a different versions of binaries working together perfectly.
That's why cmplst.txt file is there in every IBM Cognos installation to make everything work in sync with version.

NOTE: Before you start applying any fix pack make a backup of the repository database (content store) first!

If you have a IBM Cognos deployment working on (default) servlet container like apache tomcat, all you need to do is:

1. Stop IBM Cognos service.
2. Apply fix pack installables.
3. Start IBM Cognos service and you'll be done.

If you are running IBM Cognos on an application server like IBM Websphere or JBoss etc, the steps are little different:

1. Stop IBM Cognos service.
2. Apply fix pack installables.
3. Rebuild the ear/war files.
4. Redeploy the ear/war file.
5. Start IBM Cognos service.

www.cogknowhow.com

Cannot send mail from inside Cognos Controller client

(1 vote, average 5.00 out of 5)

Written by Roger

Product:

Cognos Controller 10.1.1
Windows 2008 server

Symptom:
Can not send mail from inside Cognos Controller client

Error message:
Email server reported an error, some or all messages could not be sent. Please check with your local administrator that the email server is operational and that the system configuration is correct (connection details can be found in details and or log file).

java.lang.NullPointerException
com.ibm.cognos.ccr.configproperty.EmailSettings.fromURI(EmailSettings.java:70)
...

Cause:
The value for General Configuration - Server Preferences are not filled in for
variable name: C4_EMAIL_SERVER
variable value: mailrelay.domain.se:25

http://pic.dhe.ibm.com/infocenter/cfpm/v10r1m0/index.jsp?topic=%2Fcom.ibm.swg.ba.cognos.ctrl_ug.10.1.1.doc%2Fc_syparlist.html

Solution:
Start Cognos Controller client
Log in as administrator
Go to Maintain - General Configuration - Server Preferences
Add new variable name C4_EMAIL_SERVER
Add new variable value to your mail server name (FQDN) and include the port number (:25)
Click Save.
All users need to log off Cognos controller to make the change take affect.

Above is for the new dialog boxes in Cognos controller like Group - Command Center.
Where after you have listed the status for a group/company's on the right side have a icon to send notification email.
To get this to work, the user you logged in with to Cognos Controller must have a valid email address added to its user account information in Cognos controller.

To add email address to user in Cognos Controller client, go to
Maintain - Rights - Users dialog
Click on the user in the list on left side, and add a email address on the right side for the user.
The email address must be allowed by the company email server to send email, often a address that exist inside the company.

If the sending users email address is wrong, you get a error message like this:
Unable to proceed, please address errors listed below.
Cannot send without email address for sender (ADM). Please check system configuration.
...

The mail setting inside Maintain - Configuration - General Configuration
tab general 3 is for all the old mail functions in old controller dialogs.
Here you should also specify the mail server at SMTP server line:
mailrelay.company.se
and select the email format you want to use, recommend CSV.

To test this you can go to Transfer - Export Structures.
Mark E-mail and enter an email address to receive the mail on the line at the right.
Mark what to send, for example Country Structure.
Click RUN icon.
Click CLOSE on message that temp file is created.
Enter the message text and click OK to send the email.

You need to logout from Cognos Controller client, to make any changes take affect from the General Configuration dialog.

www.cogknowhow.com

When install FAP manager on citrix server, the values are empty when the user starts the program

(1 vote, average 4.00 out of 5)

Written by Roger

Product:

Cognos Controller 10.1.1 CCR-AW32-ML-RTM-10.1.6235.57-0

FAP 1.0.13.0 CCRFAPCLIENT-AW32-ML-RTM-10.1.6235.57-0

Microsoft Windows 2008 R2 server

Symptom:

When install FAP manager on citrix server, the values are empty when the user starts the program.

Cause:

Default values for IBM Cognos Controller Financial Analytics Publisher are stored in a user.config file for each user in folder C:\Users\Administrator\AppData\Local\IBM_Corp\FAPClient.exe_Url_hizg5pd121eg2yxnq50fgzjzluvgy4wb\1.0.13.0 on the server.

Solution:

Create a batch file, that look something like this:

===================================

@echo off

mkdir %userprofile%\AppData\Local\IBM_Corp\FAPClient.exe_Url_hizg5pd121eg2yxnq50fgzjzluvgy4wb\1.0.13.0

copy user.config %userprofile%\AppData\Local\IBM_Corp\FAPClient.exe_Url_hizg5pd121eg2yxnq50fgzjzluvgy4wb\ 1.0.13.0\user.config

cmd.exe /C start "FAP Manager" "C:\Program Files (x86)\ibm\cognos\c10\webcontent\ccr\FAPClient.exe"

=============================================

Copy a working user.config file and place it in same folder as above batch file.

Add the batch file to the publish FAP manager icon, to be run before the start of the application.

Now the file is in place before the FAP manager starts, and the default values are there.

Then the user only need to type in the SQL login password to the FAP database to work.

The user.config should look like this:

<?xml version="1.0" encoding="utf-8"?>

<FAPClient.My.MySettings>

<value>MSSqlServer2008</value>

</setting>

<value>localhost</value>

</setting>

</setting>

<value>bertil</value>

</setting>

</FAPClient.My.MySettings>

</userSettings>

</configuration>

........................................................................................

NOTE:

localhost should be replace with the SQL server name

adam should be replaced with the FAP controller database name

bertil should be replaced with the SQL server login username

www.cogknowhow.com

Get a log in dialog when you surf to Cognos connection after you setup SSO

(2 votes, average 5.00 out of 5)

Written by Roger

Product:

Cognos BI 10.1.1

Windows 2008 R2 server

Active Directory

Microsoft SASS MSAS server

Symptom:

Get a log in dialog when you surf to Cognos connection after you setup SSO.

You need to ensure that you have done all the steps needed to get Kerberos to work with Cognos Bi and Windows 2008 servers. Here is a list of the steps needed, it can be that in your environment you need to do add additional steps.

Steps to activate Kerberos on a Windows 2008 R2 server:

Remove the use of "RemoteUser" from Cognos Configuration on the Cognos BI server.

Start Cognos Configuration

Go to security - authentication - your AD connection

Click on Advanced Properties

Mark the line singleSignOnOption = IdentityMapping

Click on remove

Click OK

Save and exit Cognos configuration

Restart the Cognos Bi service.

Set the Cognos Gateway server to be trusted for delegation in Active Directory

Start Active Directory Users and Computers on a server (ADSIEdit)

Search for the Cognos Gateway server

On view menu mark "Advanced Features"

Right click on server and select properties.

Go to Delegation tab

Mark " Trust this computer for delegation to any service "

Click OK

Set the windows service account used by Cognos service to be trusted for delegation in Active Directory

(to active delegation tab you must use SETSPN command:

SETSPN HTTP/Gatewayservername yourdomainname/servicename )

Start Active Directory Users and Computers on a server (ADSIEdit)

Search for the Cognos service account.

Right click on user account and select properties.

Go to Delegation tab

Mark " Trust this user for delegation to any service "

Click OK

Ensure all the Cognos servers and MSAS SSAS server are in the same domain, and that that the Microsoft Windows domain is set to native mode.

Check this in Active Directory Users and Computers on a server (ADSIEdit)

Select the domain and right click properties

In the General tab

Domain function level should be Microsoft Windows 2003 or 2008.

Ensure the end user is not set to be sensitive and not trusted for delegation in Active Directory

Start Active Directory Users and Computers on a server (ADSIEdit)

Search for the user account (that will run the reports)

On view menu mark "Advanced Features"

Right click on user account and select properties.

Go to Account tab

UnMark " Account is sensitive and cannot be delegated "

Click OK

On the client computer, start Internet Explorer and go to Internet Options under Tools menu.

Go to Advanced tab

Scroll down to security

Ensure that " Enable integrated Windows Authentication " is marked.

Click OK

Go to Security tab

Mark Local Intranet icon

Click on Sites

Click on Advanced

Enter the Cognos BI gateway server name at " add this website to the zone"

Click Add

Click Close

Click OK

Click on Custom Level

Go to bottom under User Authentication

Under Logon select "automatic logon with current user name and password"

Click OK

Ensure that you have installed the Microsoft SQL 2008 native client drivers on the Windows 2008 R2 server where Cognos BI are. You download it from http://www.microsoft.com/en-us/download/details.aspx?id=16978 and should have installed version 9.00.1399.6 of Microsoft SQL Server Native Client. (sqlncli.msi)

Set the windows service account used by Cognos service to be local administrator on the SSAS server and administrator in the SSAS server and cubes. Ensure the Cognos Windows service account is member of the local administrator group on the SSAS server.

For SSAS 2005 and SSAS 2008, Windows accounts for all users must be a part of the local OLAP users group on the computer where Analysis Services is running. This group, which is created when Analysis Services is installed, is called SQLServerMSASUser$<SERVERNAME>$MSSQLSERVER.

To be able to use Cognos Framework manager to access a MSAS SSAS 2008 server and cube, the user starting framework manager must have the Active Directory setting "trust for delegation" set. To active the delegation tab inside user and computers properties, you must set a SETSPN.

Run command like this for all users that should be using Frame work manager to MSAS cubes.

SETSPN -A HTTP/dummy domain\username

where you replace domain\username with the real domain name and the username of each user.

Then you can search for the user in Active Directory and on the Delegation tab set "trust this user for delegation to any service".

See more at:

http://blogs.msdn.com/b/mattlind/archive/2010/01/14/delegation-tab-in-aduc-not-available-until-a-spn-is-set.aspx

Ensure that you use FQDN server names in Cognos Configuration on the Cognos BI servers

Start Cognos Configuration

Go to Environment tab

Change all servernames (e.g. Gateway URI) to be servername.domain.com from servername.

(change to your domain name)

Save and restart the Cognos BI service.

Run SETSPN -L servername for the Cognos BI server and the MSAS SSAS server.

It should list the FQDN name similar to below for the Cognos BI server.

Registered ServicePrincipalNames for CN=servername,CN=Computers,DC=corp,DC= company,DC=lan:

WSMAN/servername.corp.company.lan

WSMAN/servername

TERMSRV/servername.corp.company.lan

TERMSRV/servername

RestrictedKrbHost/servername

HOST/servername

RestrictedKrbHost/servername.corp.company.lan

HOST/servername.corp.company.lan

To check SETSPN on the SSAS server:

Enter the following at the command prompt:

SETSPN -L domain1\stomssqlserviceaccountname

You should have spn similar to this

MSOLAPSvc.3/sqlservername.corp.company.lan

MSOLAPSvc.3/sqlservername

MSSQLSvc/sqlservername.corp.company.lan:1433

MSSQLSvc/sqlservername:1433

To set value for the MSAS SQL server:

setspn -A MSOLAPSvc.3/sqlservername.corp.company.lan domain1\stomssqlserviceaccountname

The windows service account that run the cognos service must be activated on the Cognos BI windows 2008 server to have this functions:

”replace a process level token”.

”Act as part of the operating system”

Log on to BISERVER (Cognos server) with the service account (that run Cognos services)

Run the following command to reach local security settings: secpol.msc or gpedit.msc

Go to Local Policies (or Computer configuration - Windows settings - Security settings - local policies - User Rights Assignment).

Under User Rights Assignment, click on "Replace a process level token"

Add the service account

Under User Rights Assignment, click on "Act as part of the operating system"

Add the service account

Exit the tool

Reboot the server

Don't get fooled by the "test data source", it will always fail for external namespace as the Kerberos delegation is NOT run for testing the data source.

You must create a report to test the SSAS MSAS 2008 data, save the report in public folders samples and let different users test to run it.

To be able to create a framework manager package, you can create a data source SSAS that uses the Cognos service account credentials to connect. This package often works better.

After the framework manager package is created and working, change the data source connection to use the AD external namespace.

Go to Cognos connection

Go to Cognos Administration

Click on configuration tab

Click on the data source you want to change, so you get one level down

Click on more for the data source you want to change

Click set properties

Click connection

Click "edit the connection string" icon

Here you can change authentication between

IBM Cognos software service credentials

and

An external namespace:

Select An external namespace:

and the AD you are using.

Click OK

and go back and test your report again.

To troubleshoot Kerberos issues, you can download and install DelegConfig.v2.beta.zip, to get more help about the Windows setup off Kerberos.

http://blogs.iis.net/brian-murphy-booth/archive/2009/04/22/delegconfig-v2-beta.aspx

www.cogknowhow.com

Cognos Controller client give an error when running a standard report

Written by Roger

Product:

IBM Cognos Controller 10.1.1

Windows 2008 R2

Symptom:

When you run a standard report in Cognos Controller client program you get a error.

User Rights and Security Group Reports:

Details

RSV-SRV-0042 Spåra bakåt:RSReportService.cpp(722): QFException: CCL_CAUGHT: RSReportService::process()RSReportServiceMethod.cpp(263): QFException: CCL_RETHROW: RSReportServiceMethod::process(): asynchWait_RequestRSASyncExecutionThread.cpp(808): QFException: RSASyncExecutionThread::checkExceptionRSASyncExecutionThread.cpp(260): QFException: CCL_CAUGHT: RSASyncExecutionThread::runImpl(): asynchRunSpecification_RequestRSASyncExecutionThread.cpp(864): QFException: CCL_RETHROW: RSASyncExecutionThread::processCommand(): asynchRunSpecification_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/RSPageSetAssembly.cpp(462): QFException: CCL_RETHROW: RSPageSetAssembly::assembleAssembly/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/AQEX_TabularQueryVisitor.cpp(333): QFException: CCL_RETHROW: QESource/QEI_ConnectionFault.cpp(985): QFException: CCL_THROW: QE

Cause:

You have not a data source connection inside Cognos Connection to your Cognos Controller database.

Solution:

Start Cognos Controller Configuration.

Go to Report Server dialog.

Click OK on any information messages.

Click on the green Check icon.

Click on the Repair button to update the Cognos Connection.

Start the Controller Client and test the report again.

You must be logged in to the Windows server with a user account that is System Administrator in Cognos Connection to make the Repair button work.

www.cogknowhow.com

More Articles...

«StartPrev123Next End»

CogKnowHow Newsletter

Polls

How many users are working on your Cognos environment?

	1 - 100 users
	101 - 250 users
	251 - 500 users
	501 - 1000 users
	1000 or more users