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.

Only when you use CAM authentication.

Suggested 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

This error can also be found if the name of the TM1 application is to long, so the total length of the temp files BLB is more than 255 characters on the Windows server. During start of the Contributor session a blb file is created with the user name as filename in the datafiles folder, if this file is not created (due to its name is to long), when you exit your Planning Analytics Contributor application you get above error, because TM1 can not find the file and erase it.  All work, but you get a irritating error.

Solution is to have TM1 instances installed with short names like d:\tm1server\112\datafiles or similar.

You can also find in the tm1server.log error like this NAME INVALID error and that causes TM1.Blob FileCreateOpenDelete.