Product:
Cognos Controller 10.3.1
Microsoft Windows 2016 Server
Cognos Analytics 11.0.9

Issue:
Standard reports in Cognos Controller does not work.

Possible solution:
You have to manually change the database connection string from SQLOLEDB to Native SQL.

Surf to Cognos Connection.
Go to old Administration page.
Go to Data Source.
Go to Set Properties for the connection.
Change the value and save it.

The Cognos Datasource connection string that is automatic created from Cognos Controller Configuration repair button creates non-supported data connections in CA11.
ca11 databas kopplingar

Above is the supported data sources in Cognos Analytics 11.

Product:
Cognos Controller 10.3.1
Microsoft Windows 2008 R2 server
Microsoft SQL database
Cognos Analytics 11.0.8

Issue:
When logging in to Cognos Controller 10.3.1 after a new setup some users get a error.
This setup is with 3 citrix servers and 3 controller application servers, where the controller functions is scaled out over the different controller application servers. On each citrix server the ccr.exe.config file point one of the controller application servers – to allow some kind of load balance to the controller applications server layer.
This is setup from this instructions:
http://www-01.ibm.com/support/docview.wss?uid=swg21677206

Error message:
Error occured at 3/22/2018 8:18:10 AM in IBM Cognos Controller, Error No=5, Source=FrangoDirect.ConnectionDirect.SetSelectDb#System.Web.Services, Description=System.Web.Services.Protocols.SoapException: Server was unable to process request. —> System.Net.WebException: The request failed with HTTP status 404: Not Found.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at CCRRemoteServerProxy.Proxy.FrServerB.WSFrServerB.ConnectionBusiness_SetSelectDb(String sGuid, String sUser, Boolean bSelectDb)
at FrServerB.RemoteConnectionBusiness.SetSelectDb(String sGuid, String sUser, Boolean bSelectDb)
at FrServerB.ConnectionBusiness.SetSelectDb(String sGuid, String sUser, Boolean bSelectDb)

Possible solution:
The web.config file have not a correct servername for the ccrRemoteServer value, it can be a extra special character or something that make the “http” string not work. Test the string in Internet Explorer from the slave server – can it surf to the master server?

Enter this to get a response:
http://masterserver/ibmcognos/controllerserver/ccrws.asmx

If above does not solve it – check that you can from the client and server surf to;
http://masterserver/ibmcognos
http://caservername/ibmcognos

If you have CA11 on the same server as your cognos controller installation, then the caservername and masterserver is the same address.

The key setup point for more controller application servers is this;

On the Slave server:

  • Browse to the ‘ControllerProxyServer’ folder (by default, this is located here: C:\Program Files\ibm\cognos\ccr_64\ControllerProxyServer)
  • Open the file ‘web.config’ inside Notepad.exe
  • Locate the section ‘<appSettings>’
  • Add the following entry, inside that section:
        <add key=”ccrRemoteServer” value=”

http://MASTERSERVER/ibmcognos/controllerserver

      ” />

Naturally, modify the value ‘MASTERSERVER’ with the name of your ‘master’ application server.

https://www.ibm.com/support/knowledgecenter/SS9S6B_10.3.1/com.ibm.swg.ba.cognos.ctrl_inst.10.3.1.doc/t_ctrl_loadballacing.html

Product:
Cognos Controller 10.3.1
Microsoft Windows 2008 R2 Server
Cognos Analytics 11.0.8

Issue:
After installation of a interim fix on top of a Cognos Controller 10.3 installation, some of the Cognos Controller windows services are missing.

Solution:
Here instructions on how to install a upgrade, on top of Cognos Controller.
http://www-01.ibm.com/support/docview.wss?uid=swg22001683

After the installation check that all Cognos windows services are in place.
ctrl1

If your are missing IBM Cognos Controller Java Proxy you should run this line from cmd:
sc create “IBM Cognos Controller Java Proxy” binpath= “d:\Program Files\ibm\cognos\ccr_64\server\CCRProxy.exe” DisplayName= “IBM Cognos Controller Java Proxy” depend= RpcSs start= demand

if you are missing IBM Cognos Controller User Manager you should run this line from cmd:
sc create frLicServer binpath= “d:\Program Files\ibm\cognos\ccr_64\server\FrLicServer.exe” DisplayName= “IBM Cognos Controller User Manager” depend= RpcSs start= auto

More Information:
http://www-01.ibm.com/support/docview.wss?uid=swg21680801
http://www-01.ibm.com/support/docview.wss?uid=swg21680788

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

Product:
Planning Analytics 2.0.3
IBM Cognos TM1 Applications
Microsoft Windows 2016 server

Issue:
When publishing a updated TM1 application in Performance Modeler to the TM1 Applications web (contributor web portal), the application is deleted.

Error can be:
[DeployApplicationThread:9b649fa9-1cf1-46f7-9bae-5f2fde393121] ERROR () com.ibm.cognos.pmpsvc.PMPService – deployApplication Throwable
com.ibm.cognos.pmpsvc.PMPSVCException: An exception occurred on the server. Please contact your system administrator. :com.ibm.cognos.pmpsvc.handler.PMPTM1Exception: TI_NODE_NOT_EXIST[CAMID(“CDS:u:uid=roger,ou=people,ou=eu”) | }tp_modify_application_attribute | }ElementAttributes_}tp_applications, BounceMode ] :EXCEPTION

Solution:
There is a chance that there are “left-overs” from a old application with similar name in the portal, therefor the application is deleted before a new is created. The first time you publish a TM1 application to a new PMPSVC (contributor) web server, you need to ensure there is not a old application there since a previous crash.

Before republishing a old TM1 10.2.2 application to a new PA 2.0.3 server do this;
— stop the TM1 instance windows service.
— erase the log folder for the tm1 instance.
— copy a new fresh data folder from the TM1 10.2.2 application.
— surf to http://paservername.domain.com:9510/pmpsvc and remove the old application with the same name from the list of applications. You do this from the TM1 applications configuration page. You must be ADMIN in the TM1 instance you try to remove.
Check in the file TM1InstallRoot\webapps\pmpsvc\WEB-INF\configuration\fpmsvc_config.xml that the application is not listed any more.
— stop the IBM Cognos TM1 windows service (tm1web and pmpsvc service).
— surf to Cognos Analytics http://caservername.domain.com/ibmcognos and go to Team Content – IBM Cognos TM1 Applications – My Applications. Remove the link to your published application. PM can not publish a application if there already exist on with the same name.
— start the IBM Cognos TM1 Windows service (pmpsvc service).
— start the TM1 instance, that you had issues with.
— Surf to http://paservername.domain.com:9510/pmpsvc and add the TM1 instance to the portal, and make it a application you can work with from PM tool.
— Log into Performance Modeler as a ADMIN in your TM1 application. Open up and see the application you have built before, validate the application first. Then try to publish it again.

If you have a working TM1 instance, then above should solve the issue, because you start from a fresh working data folder. There should not be any corrupt files you need to delete. Surf to http://paservername.domain.com:9510/pmpsvc to see if it worked.

More Information:
https://www.ibm.com/support/knowledgecenter/en/SS9RXT_10.2.2/com.ibm.swg.ba.cognos.tm1_inst.10.2.2.doc/c_tm1_inst_contrib_strtlnk.html

If you Run the }tp_admin_delete_all process from Architect, then all applications can be erased, and you may have to recreate them.

Product:
Planning Analytics 2.0.3
IBM Cognos TM1 Applications
Microsoft Windows 2016 server

Issue:
When user inside Cognos TM1 Applications (contributor) are reporting there numbers. Then they click on X to close the window, they get a error message: 54: ObjectNameInvalid, when they press OK the application exits as it should.

Solution:
You are using Internet Explorer in wrong emulation mode.

Press F12.
Select Emulation.
Change Document mode to Edge or 10, from 11.
Go into the node again and test.

To get to TM1 Applications you surf to http://paservername.domain.com:9510/pmpsvc

 

Product:
Cognos Controller 10.3.1
Microsoft Windows 2012 R2 Server

Issue:
Error when you try to login to Cognos Controller client, after you have selected the database to use, and you have been logged in as a CAM user.

Error message:
System.Web.Services.Protocols.SoapException: Server was unable to process request. —> System.Exception: invalid_user

at Cognos.Controller.Proxy.SoapExtension.ServerExtension.ValidateCAMUser(SoapMessage& message)

at Cognos.Controller.Proxy.SoapExtension.ServerExtension.ProcessMessage(SoapMessage message)

at System.Web.Services.Protocols.SoapMessage.RunExtensions(SoapExtension[] extensions, Boolean throwOnException)

at System.Web.Services.Protocols.SoapServerProtocol.CreateServerInstance()

at System.Web.Services.Protocols.WebServiceHandler.Invoke()

at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()

— End of inner exception stack trace —

at Microsoft.VisualBasic.ErrObject.Raise(Int32 Number, Object Source, Object Description, Object HelpFile, Object HelpContext)

at Cognos.Controller.Common.RaiseErrCli.RaiseError(Int32 lErrNo, String sErrSource, String sErrDesc, String sErrHelpFile, Int32 lErrHelpContext)

at Cognos.Controller.Direct.ServerInfoD.GetServerInfo()

at CCR.AppContext.InitServerInfo()

at CCR.AppContext.Login()

Solution:
Login to your windows computer as a user who have rights to use Cognos Controller.
Then it will work. This user is not added inside Cognos controller, and therefor can not login.

Other solutions:
http://www-01.ibm.com/support/docview.wss?uid=swg21692450

Product:
Cognos Controller 10.3.1
Microsoft Windows 2012 R2 Server

Issue:
An error occurred while trying to access the server when you start the Cognos Controller client and try to login.

Error message:
System.Web.Services.Protocols.SoapException: Server was unable to process request. —> System.ArgumentException: Requested registry access is not allowed.

at Microsoft.VisualBasic.ErrObject.Raise(Int32 Number, Object Source, Object Description, Object HelpFile, Object HelpContext)

at ControllerServerCommon.RaiseErrSrv.RaiseError(String sUser, Int32 lErrNo, String sErrSource, String sErrDesc, String sErrHelpFile, Int32 lErrHelpContext)

at FrServerB.LocalConnectionBusiness.SetSelectDb(String sGuid, String sUser, Boolean bSelectDb)

at FrServerB.ConnectionBusiness.SetSelectDb(String sGuid, String sUser, Boolean bSelectDb)

— End of inner exception stack trace —

at Microsoft.VisualBasic.ErrObject.Raise(Int32 Number, Object Source, Object Description, Object HelpFile, Object HelpContext)

at Cognos.Controller.Common.RaiseErrCli.RaiseError(Int32 lErrNo, String sErrSource, String sErrDesc, String sErrHelpFile, Int32 lErrHelpContext)

at Cognos.Controller.Direct.ConnectionDirect.SetSelectDb(Boolean bSelectDb)

at CCR.AppContext.SelectDb()

at CCR.AppContext.Login()

Solution:
In the IIS manager change the user account used by the Application pool that Controllerserver is using.

Start Internet Information Servers Manager
Go to Application pools
Select NET v4.5
Click on Advance Settings
Change Application pool identity to LocalSystem from ApplicationPoolIdentity
Click OK
Restart IIS services.

More information:
http://www-01.ibm.com/support/docview.wss?uid=swg21691747

Product:
Planning Analytics 2.0.3
Planning Analytics Workspace  (ipa_workspace_local_2.0.29.1080.2.zip)
Microsoft Windows 2016 server
Red Hat Linux server

Problem:
When inside PAW, and you try to expand a node of a TM1 instance, you get a error message.

Error:
Session can not be established for server proven_techniques 500 (internal server error) “code” “explorer” “refID” “message” .”Failed to get children for server cubes”. “cause”.”java.net.NoRouteToHostException: No route to host”.

paw39
Solution:
In one case this is because of DNS and routing problems in network. The PAW server and PA server have both two network cards, and can only communication on one of them.
You must in TM1S.CFG tell Tm1 instance what network card it should use.

Add the line
IPAddressV4=”10.200.30.40″
in TM1S.CFG and restart the TM1 instance.

Replace the ip number with the correct ip address of your Planning Analytics server.
Important that the IP address are inside ” double quotation mark.

Product:
Planning Analytics Workspace
Planning Analytics 2.0.3
Microsoft Windows 2016 Server

Problem:
When user surf to the PAW, they are not administrator and can not add other users.
Surf to http://pawservername.domain.com
Click on the user — and see there is not a option for Administration.
This is a new PAW setup with CAM authentications.

Solution:
The first users that you add in a TM1 instance as ADMIN will be admin in paw when you login to paw. Therefor you must add CAM users to a native TM1 instance first.

Open up a Tm1 application in Native mode. Like Proven_Techniques.
Open C:\Program Files\ibm\cognos\tm1_64\samples\tm1\Proven_Techniques\tm1s.cfg in notepad++.
Add the lines;
IntegratedSecurityMode=2
ServerCAMURI=http://caservername.domain.com:9300/p2pd/servlet/dispatch
ClientCAMURI=http://caservername.domain.com:80/ibmcognos/bi/v1/disp
Close TM1 architect.
Update the C:\Users\%username%\AppData\Roaming\Applix\tm1\tm1p.ini file with
AllowImportCAMClients = T
CognosGatewayURI = http://caservername.domain.com:80/ibmcognos/bi/v1/disp

Start PAW administration console and surf to http://pawservername.domain.com:8888
Setup like this (change to your servers name);
TM1 Admin Server URI: https://paservername.domain.com:5898
TM1 Application Server Gateway URI: http://paservername.domain.com:9510
Authentication Mode: TM1
TM1 Login Server URI: https://paservername.domain.com:5011
Click validate and update.

(This TM1 instance you point out with the HTTPport number is the instance that will define the first ADMIN in paw, even if you use security mode 5).

Start TM1 Architect and login to Proven_Techniques as Admin.
Go to Security – Client/Groups. From menu Clients select Add New Client.
Add your CAM user from your AD domain, that you want to be ADMIN in paw.
Mark the user to be ADMIN in TM1 Architect. Click OK.
Exit Tm1 Architect.

Open C:\Program Files\ibm\cognos\tm1_64\samples\tm1\Proven_Techniques\tm1s.cfg in notepad++.
Change; IntegratedSecurityMode=5
Save the file and restart the TM1 instance.
Now TM1 instance is using CAM authentication.

Update PAW admin console by surf to http://pawservername.domain.com:8888
TM1 Admin Server URI: https://paservername.domain.com:5898
TM1 Application Server Gateway URI: http://paservername.domain.com:9510
Change to Authentication Mode: CAM
Set IBM Cognos BI Gateway URI: http://caservername.domain.com:80/ibmcognos
Set IBM Cognos BI Dispatcher URI: http://caservername.domain.com:9300/p2pd/servlet/dispatch
Set IBM Cognos BI Authentication Namespace ID: AD
Click Validate and update.
Click on status tab – wait until CPU usage is below 1%.

Surf to http://pawservername.domain.com
Login as the CAM user you have given ADMIN rights in Proven_Techniques.
This user should now have a ADMINISTRATOR option under its name.

The list will only show name for people who have already try to login.

More Information:
https://www.ibm.com/support/knowledgecenter/en/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_prism_gs.2.0.0.doc/c_paw_administration_top_level.html

Product:
Planning Analytics 2.0.3 (Tm1)
Cognos Analytics 11.0.9 (Cognos BI)
Microsoft Windows 2012 R2 Server

Issue:
When a user is added to a AD group, that then is added to Cognos group, and the Cognos Group is added in the TM1 application as a group. And that group is given access to cubes and dimensions inside TM1. When user login to TM1WEB, he can not see the cubes.
If you look inside TM1 Architect, there is no X for him under the Cognos\group. So Cognos have not understand that he belongs to a AD group.

Solution:
IBM Cognos service run as local system in Windows server.
The Active Directory is setup to allow user to login but not to see other users details, like groups.

ad1

You need to at Namespace – Resource Properties – Binding credentials enter the name and password of a user that have the rights to READ the Active Directory and see what groups a user belongs to.

ad2

When you right click on namespace in cognos configuration and select test, you will first validate the user and there after try to get a list of the groups the user belongs to.

ad3

You need the binding credentials if AD is not configured to allow anonymous bind.

ad4

In TM1 you can add the Cognos group or the AD group direct into TM1 Architect under security – client/groups. Click on Groups and Add New Group. Click on your namespace and search for the group you want to add. When it is added it will look similar, as in the picture above.
If a user is successful to login and belongs to a group, there will be a X under that group for that user. User AD/roger can we see belongs to the Cognos group “TM1 users”.

ad5

Then you have to, inside your TM1 application, give the groups the access they need to the different cubes and dimensions.

More Information:
https://www.ibm.com/support/knowledgecenter/SSEP7J_10.2.2/com.ibm.swg.ba.cognos.inst_cr_winux.10.2.2.doc/t_inst_activedirectoryserver_process.html

https://www.ibm.com/support/knowledgecenter/en/SS9RXT_10.2.2/com.ibm.swg.ba.cognos.tm1_dg_dvlpr.10.2.2.doc/c_controllingaccesstotm1objects_n60007.html

https://www.ibm.com/support/knowledgecenter/en/SS9RXT_10.3.0/com.ibm.swg.ba.cognos.prfmdl_ug.10.3.0.doc/c_prfmdl_setting_up_security.html