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.

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.

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:
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:
Cognos Controller 10.3
Microsoft Windows 2012 R2 server
Microsoft Excel 2010

Problem:
Some excel reports show 0 when updated with F9 or F10. No errors, but the numbers are not shown.

Possible workaround:
Change the xls filename to not contain any Swedish Characters (åäö) or turn off the use of Optimise2 (ERO).
Previous it have been known that space or apostrophe in the excel workbook name or worksheet name can give issues when using ERO reports.

To turn off ERO go to cell A1 in Excel;
Click the tab ‘Formulas’
Click ‘Name Manager’
Highlight the entry ‘ Optimise2’ (which refers to Sheet1, cell A1)
Click ‘Delete’
Save the worksheet and try again.

Create a support ticket with IBM Cognos Support to get a better solution to this issue.

More information:
http://www.ibm.com/support/docview.wss?uid=swg21966485
http://www-01.ibm.com/support/docview.wss?rs=0&uid=swg21365263
http://www-01.ibm.com/support/docview.wss?uid=swg21607230

Product:
Cognos Controller 10.3 (10.3.1.34-0)
Microsoft Windows 2012 R2 server
Microsoft SQL server 2014
Microsoft Excel 2010 or newer

Problem:
When start Excel from inside Cognos Controller client by press on the Excel icon or open data entry, you get a error message.

Error:
Cannot run the macro ‘cc.CompareDb’. The macro may not be available in this workbook or all macros may be disabled.
at Microsoft VisualBasic.CompilerServices.LateBinding.LateGet (Object o, Type objType, String name, Object[] args, String[] paramnames, Boolean [] CopyBack) at Cognos Controller.Forms.Common. fFmFrangoFunc.RunExcelMacro…

Solution:
Start Excel
Go to options in File menu
Go to add-ins
Click on Go at Excel Add-ins
UnMark a Adxloader.Controller.Excellink if it exists.
Click OK.
Exit Excel and Cognos Controller and try again.

Error:
Could not find c:\frangow\frangos.exe /automation. Check the file name is correct spelled and the path is correct…
at microsoft.office.interop.excel.workbooks.open(String filename Object UpdateLinks, object ReadOnly, Object Format, Object Password…
at Cognos.Controller.Forms.Common.fFrmFrangoFunc.InitExcelLink at Cognos.Controller:Forms.ControllerMDI.DoAction…

Solution:
Start Excel
Go to options in File menu
Go to add-ins
Click on Go at Excel Add-ins
UnMark a ControllerXL… line if it exists.
Click OK.
Should only be one line “Cognos Controller Link for Microsoft Excel”
Exit Excel and Cognos Controller and try again.

Product:
Cognos Controller 10.3 version 10.3.1.45 (Integration Version 10.3.1.19 Install/Udater Kit Version 10.3.1.36)
Microsoft Windows 2012 R2 server
Microsoft SQL 2014 database server

Problem:
When running a excel report or updating a excel form you get a error message. If you turn off ERO by remove the “Optimise2” name on cell A1 in the spreadsheet then it works. This is a upgrade installation from Cognos Controller 10.2.1 where it was no problem to run a ERO report in old version of Cognos Controller.

Error message:
System.Web.Services.Protocols.SoapException: Server was unable to process request. — System.Exception: Cannot bulk load because the file “xxx\xxx.tbl” could not be opened. Operating system error code 3(The system cannot find the path specified.). at Cognos.Controller.Proxy.CCRWS.ExcelLinkB_FetchValuesBulk(String sGuid, String sKeys, String sMcurr, Boolean bLocLang, string sUser, String sRep, Boolean bIsLnk, String sSortOrd, String sParams)
—End of inner exception stack trace—

Solution:
Ensure you leave the “server directory” field blank at Enhanced Reporting Optimizations tab in Controller Configuration.
With SQL databases the use of a directory folder in ERO, is not longer supported.

For Cognos Controller 10.3, there is less need to use ERO with SQL databases. But you still need to set it up for upgrading customers, so they can run there old Excel reports.

How setup ERO for SQL database:
Ensure that the SQL account used to access the Cognos Controller databases have Server Roles “bulkadmin” and “public”.
Ensure the SQL services is run by a windows domain account and not as LocalSystem.
Create a folder on your controller Windows server called d:\ero
Right click on the ERO folder and select Properties.
Click on Sharing tab.
Click on Advanced Sharing button.
Mark “Share this folder”
Enter the share name to be: ERO$
(The dollar sign make the share invisible for browsing users)
Click on Permissions button.
Click “Allow” at Full Control for user “Everyone” (or add the service account that should have access here).
Click Apply and OK.
Click Apply and OK.
Click on Security tab.
Click on Edit button.
Click Add button.
Enter the name of the service account and press Check Names button.
Click OK.
Click “Allow” at Full Control for the service account you just added.
Click Apply and OK.
By default members of the servers local Administrator group have full control to a folder. You can remove the users group to ensure other have no access.
Click Apply and OK.
Click Close. The share is created.

Open Controller Configuration.
Go to the Enhanced Reporting Optimizations tab.
Select the controller database from the connection drop down list.
Fill in for each database;
File Mode: File Copy
Server: the name of the server where the ERO share is — normally the controller server or the SQL server.
Share: the name of your share (e.g. “ERO$”)
Server Directory: Must be blank (empty). (if using Oracle you need to fill this in).
User ID: AD\service_account (the windows account that you have given read/write permission to the ERO network share)
Password: password for the above user — it is encrypted when you press enter.
Click on Save icon in Controller Configuration.

Ensure that the EXCEL spreadsheet that will use ERO does not have a space in there spreadsheets tab-name.
In the excel report that should use ERO , go to cell A1.
Click on Name Manager icon.
Enter the name to be Optimise2.
Save the change and spreadsheet.

Update the Controller values by pressing F9 in Excel, when you are logged in to the Controller database through the Controller Excel Link.

Other error messages:
Server was unable to process request. —- System.IO.IOException: The network name cannot be found.
Possible cause:
The ERO share does not exist, check that the folder is shared out and not misspelled in controller configuration.
Other error messages:
Server was unable to process request. —- System.ArgumentException: Access to the path “xxx\xxx\xxx.tbl” is denied.
Possible cause:
The user have only READ access to the share, make sure you have full access for the user doing the request.
Other error messages:
Operating system error code 5(Access is denied.)
Possible cause:
The user account doing the request have not the full access to the folder on hard disk. Check the NTFS rights on the ERO folder.

You define the Active Directory user to access the Windows file share in Cognos Controller Configuration. If this is left blank, the user running the COM object is used – in most cases it is “Local System” account on Windows server.

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

Product:
Cognos Controller 10.2.1
Microsoft Windows 2008 R2 Server
Microsoft SQL 2012 database

Problem:
How to upgrade Controller 10.2.1.x to a later Fix Pack ?

This is a very good article – so i copy the text, to have it here as well.
http://www-01.ibm.com/support/docview.wss?uid=swg21701948

Solution:
It is possible to patch an existing 10.2.1 Controller application server *without* having to perform a full uninstall/re-install of the Controller application server software. However, care needs to be taken (during the patching process) to ensure that all Controller-related services/systems/components are stopped.

To check which version of Controller you are currently using, click “Help – System Info” (inside the Controller client) and check the value of the first/top line.

To upgrade the Controller application server, perform the following tasks:
1. Download a copy of the patch (either a Fix Pack or Interim Fix).
2. Obtain downtime (no users on system)
3. As a precaution, perform the following tasks:
(a) Backup all Controller-related databases (application repositories, ContentStore and FAP)
(b) Launch ” Cognos Configuration” and create a backup of all the settings.
Typically this means click “File – Export As” and save the settings as an XML file (in a safe place)
(c) Launch ” Controller Configuration” and create a backup of all the settings
e.g. create a Word document with printscreens of all the current settings
(d) If using virtual servers (for example ESX) then create a backup image of the virtual server(s)
In other words, ask your ESX administrator to create a virtual snapshot backup of any server (for example Controller application server) before you make any changes.
4. VITAL: Shut down all Controller-related Windows services (running on the application server(s))
Specifically, stop the following Windows services:
IBM Cognos
IBM Cognos Controller Batch Service
IBM Cognos Controller Consolidation
IBM Cognos Controller Java Proxy
IBM Cognos Controller User Manager
IBM Cognos FAP Service

5. VITAL: Shut down other Controller-related subsystems (running on the application server(s))
Specifically,
Launch the “Internet Information Services (IIS) Manager” tool
Highlight the Default Web Site.
Click “Stop”:

Launch the “Components Services” tool
Right-click the “IBM Cognos Controller Consolidation” COM+ application and choose “Shut down”:
6. As a precaution, now take a backup copy of the entire ccr_64 folder (e.g. compress inside a backup ZIP file):
[This process helps make it easier to revert back to the older version of Controller if necessary later].

7. If the Controller application server has a Controller client installed, then uninstall the Controller client first before proceeding:
Important to uninstall the client before you upgrade the server. The uninstall program may use some of the previous versions files.
8. Install patch onto the application server(s) by doing the following:
Extract the compressed patch file
Double-click on installer file issetup.exe (inside subfolder winx64h)
Navigate through the installation wizard (in general by accepting all the default options).
TIP: Ensure that you choose the installation folder to be the same folder as the current installed version
If you have multiple Controller application servers, apply the patch for all remaining Controller application servers.

9. After the patch has finished installing, launch “IBM Cognos Configuration”. Click the buttons (near the top-left corner of the screen) to:
Save the current configuration
Start the IBM Cognos service:
10. Afterwards, launch ” Controller Configuration” and open the section ‘Database Connections’. Click on each database connection, and click on the green ‘play’ button.
Check to see if the ‘Current Version’ is set to be the same as the ‘Upgrade to’ version:
Sometimes (depending on the old/new versions of Controller) the ” Upgrade to” will have increased (because of the patch). If so, then you must press ‘ Upgrade’ to upgrade your Controller application databases (to the latest version).

11. Inside Controller Configuration, check that all the other settings look *exactly* the same as before the upgrade. Most importantly (in particular) check the following two sections:
Report Server:
COM+ Server:
TIP: Refer to the printscreens that you took earlier (in step 3 – before the upgrade) to make sure that the settings look the same as before.
12. If you used “ISAPI” before the upgrade, then:
change “Report Server” to mention cognosisapi.dll instead of cognos.cgi
modify the files “default.htm” and “index.html” (located in webcontent folder) to refer to cognosisapi.dll instead of cognos.cgi
13. Check the Windows service ” IBM Cognos Controller Java Proxy”. Ensure that it is configured to ‘ Log On As’ using the correct Windows user (typically the Cognos Controller system user e.g. \Controller_system).
14. Inside the IIS Manager, highlight the “Default Web Site” and click ” Start”
15. Afterwards, reboot Controller 10.2.1 application server(s) (to automatically start relevant services and ensure that the registry key change takes effect)

16. Upgrade client software on each-and-every end-user’s client device (see below).

Simplified instructions for how to upgrade *Client* software on each-and-every end-user’s client device:
1. Logon to the client device as the SAME Windows administrator which originally installed the Controller client.
2. Launch “Add/Remove Programs” and remove the Controller client ( for example “IBM Cognos Controller Local Client”):
VITAL that you uninstall the old cognos controller client before you install a new Cognos Controller client.
3. Download the new version of the Controller client from the application server
TIP: You can download it from: http://SERVERNAME/ibmcognos/controllerbin/ ccrlocalclient.msi
There are three different versions of the client – see Technote#1371088. For most customers, CCRLocalClient.MSI is the best version to use.
4. Double-click on the client installation file (for example ” ccrlocalclient.msi”)
5. Follow the installation wizard
TIP: If unsure what values to use (for example WSSUrl) then open the file %APPDATA%\Cognos\CCR\ccr.config inside NOTEPAD and read the values from there.
6. If the client device does not have access to the internet (e.g. most Citrix/Terminal servers) then modify the file “ccr.exe.config” (inside C:\Program Files (x86)\ibm\IBM Cognos Controller) as per separate Technote #1441779.

There are patches coming for Cognos Controller. You decide when you need to apply them, depending on how “secure” your network is and the risk of that the Cognos servers will be affected by unwanted software. Recommendation is to always be on latest fix pack.

http://www-01.ibm.com/support/docview.wss?uid=swg22004648
This upgrade instructions affect IBM Cognos Controller 10.2.1, check IBM web site for instructions for other versions.

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

Remediation/Fixes
The recommended solution is to apply the fix for versions listed as soon as practical:
10.2.0: http://www-01.ibm.com/support/docview.wss?uid=swg24043783
10.2.1: http://www-01.ibm.com/support/docview.wss?uid=swg24043783
10.3.0: http://www-01.ibm.com/support/docview.wss?uid=swg24043784

Product:
Cognos Controller 10.3
Windows Server 2012 R2
Microsoft Excel Professional Plus 2013 (32 bit version)

Problem:
When starting Excel 2013 from icon in Cognos Controller or when open the data entry form I get a error.

Error message:
Error launching menu item “controller link”
Error Details
… macro cc.CompareDb . Macro is maybe not in this workbook…
… could not find c:\program files(x86)\IBM\IBM Cognos Controller\adxloader.Controller.ExcelLink.dll. Can it have been moved, change name or been removed?…

Solution:
There may be old references to old Cognos Controller versions in the registry for this user.

Start Excel 2013
On file – options – add-ins
Click on GO button for manage Excel Add-ins
if there is a line for
Adxloader.controller.excellink
mark it and you will get a message that say it can not find the add-in, should it be removed from the list?
Click Yes.
Close excel.

Please try again to see if excel is working now.

Fun fact:
To see what AD groups you belong to and other information,
start a Command prompt as admin on the computer
Enter gpresult /v > c:\temp\YOURINFO.TXT

This will list both groups for you and the computer and other information.

In case above does not work for one user, but the other users have less problem with Cognos Controller and Excel. Run above command on the two users computers, and compare the TXT files for them to find out if the user that Cognos Controller is working for have more RIGHTS on his computer than the person who have issues.

Check the section “The user is part of the following security groups” last in the list.