Cognos Controller 10.3 (
Microsoft Windows 2012 R2 server
Microsoft SQL server 2014
Microsoft Excel 2010 or newer

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

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…

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.

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

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.

Cognos Controller 10.3 version (Integration Version Install/Udater Kit Version
Microsoft Windows 2012 R2 server
Microsoft SQL 2014 database server

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—

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:

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

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.

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))
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.
This upgrade instructions affect IBM Cognos Controller 10.2.1, check IBM web site for instructions for other versions.

The recommended solution is to apply the fix for versions listed as soon as practical:

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

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?…

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
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.

Cognos Controller 10.3
Microsoft Windows 2012 R2
Microsoft SQL 2016 database server

You have two environment, PROD and TEST, and want from same computer client be able to connect with same Cognos Controller 10.3 client to these environments. You can not have two different versions on Cognos Controller client installed at the same time on your laptop, because it is risk that it will not work with the Cognos Controller Excel add-in. Here it is same version of Cognos Controller client that should talk to two different Controller Application servers.

Possible solution:
Please take care and ensure that the client works with the correct database, and that you always clear the local cache inside Cognos Controller 10.3 when you start the program. This to ensure you do not have data from the other database inside the client.

Install the Cognos Controller client from the CCRLOCALCLIENT64.MSI file (that you find on the controller server in folder
C:\Program Files\ibm\cognos\ccr_64\webcontent\ccr ).
Here you have instructions on how to install Cognos Controller 10.3 client

After the installation, then you on the client create this files.
Go to folder C:\Program Files\ibm\IBM Cognos Controller Local Client\
Copy the file ccr.exe to ccrtest.exe and ccrprod.exe, so you have 3 exe files in the folder.
Copy the file ccr.exe.config to ccrtest.exe.config and ccrprod.exe.config, important the names match the previous names.
Then open ccrprod.exe.config in notepad.
It is only the row WSSUrl you need to change – so it point to the TEST or the PROD server.

<add key=”WSSUrl” value=””/>

update the ccrprod.exe.config text file and then save it.

update then ccrtest.exe.config text file with the TEST server name and save it. Also only on this row  <add key=”WSSUrl” value=”http://controllerTESTserver/ibmcognos/controllerserver”/>

Now you have a CCRPROD.EXE that will use the CCRPROD.EXE.CONFIG file to find the server when you start the program.

Now right click on CCRPROD.EXE and select “create shortcut” – place the shortcut on the desktop.
Now right click on CCRTEST.EXE and select “create shortcut” – place the shortcut on the desktop.

There should now be TWO icons for Cognos Controller 10.3 on the desktop of this user.
(if you want to install this on several users, then you should copy the 2 *.exe and the 2 *.config files you created and the 2 ccr – shortcut files to each users hard-disk, keeping them in the same folders as now.).

To start Cognos Controller 10.3 for the test environment, then you click on the CCRTEST.EXE icon.
After you have logged in, you go to menu Maintain – Special Utilities – Clear Local Cache.
Then you can start working in your Cognos Controller 10.3 Client session.

To see what database you are using in the program toolbar – go to Maintain – User – Personal Defaults
On the Layout tab, mark windows setting “Display Data Source and User ID”.
Click OK.

Restart your Cognos Controller 10.3 client program.

============== This is how the ccr.exe.config file can look like===================

<?xml version=”1.0″ encoding=”utf-8″?>
# =====================================================================
# IBM Confidential
# OCO Source Materials
# IBM Cognos Products: ccr
# (C) Copyright IBM Corp. 2004, 2014
# The source code for this program is not published or otherwise
# divested of its trade secrets, irrespective of what has been
# deposited with the U.S. Copyright Office.
# =====================================================================

<sectionGroup name=”profile”>
<section name=”Settings” type=”System.Configuration.NameValueSectionHandler, System, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, Custom=null”/>
<section name=”log4net” type=”log4net.Config.Log4NetConfigurationSectionHandler, log4net” requirePermission=”false”/>
<add key=”SelectDb” value=”true”/>
<add key=”Language” value=”2057″/>
<add key=”CASUrl” value=”C:\Program Files\IBM\IBM Cognos Controller Local Client\”/>
<add key=”WSSUrl” value=””/>
<add key=”HelpUrl” value=””/>
<add key=”InstallExcelLink” value=”false”/>
<add key=”CacheDir” value=””/>
<add type=”ClientExtension, ControllerExtension” priority=”0″ group=”0″/>

<level value=”ERROR”/>
<appender-ref ref=”CCRClient”/>
<appender name=”CCRClient” type=”log4net.Appender.FileAppender”>
<staticLogFileName value=”false”/>
<file type=”log4net.Util.PatternString”>
<conversionPattern value=”${LOCALAPPDATA}\CCRClientLogs\%date{MM_dd_yyyy}.txt”/>
<appendToFile value=”true”/>
<layout type=”log4net.Layout.PatternLayout”>
<conversionPattern value=”%date %-5level %logger – %message%newline”/>



Here you can download the Cognos Controller 10.3 fix pack 1 version

Cognos Controller 10.3
Microsoft Windows 2012 R2 Server
Microsoft SQL 2014 server

Surf to controller web give blank page. If you try to surf to http://localhost:9080/fcm.web/login instead of http://servername:9080/fcm.web/login it works fine.

Ensure you surf to FQDN and that is in your Trusted Zone in IE. Local intranet zone is not good enough. You must surf to

How to install Controller web:
During installation on your Cognos Controller server select to install the controller web parts.
This will create the folder C:\Program Files\IBM\cognos\ccr_64\fcmweb

Locate the file server.env in the C:\Program Files\IBM\cognos\ccr_64\fcmweb\wlp\etc\ folder.
Open the file server.env and set the JAVA_HOME installation directory to JAVA_HOME=C:/Program Files/IBM/cognos/ccr_64/fcmweb/jre/jre.
To synchronize Controller Web with Uniform Data Language (UDL) files defined for databases used by Controller, run SyncDBConf.bat as an administrator from the command prompt.

SyncDBConf.bat takes two parameters:
The UDL files folder: the path to the folder containing UDL files (specifying database connections) defined for Cognos Controller.
The datasource folder: the output path for the folder that shall contain the data sources generated from the UDL files.
For example:
C:/Program Files/IBM/cognos/ccr_64/fcmweb/SyncDBConf.bat       ..\Data     wlp\usr\shared\config\datasources

Locate the file in the C:\Program Files\IBM\cognos\ccr_64\fcmweb\wlp\usr\servers\fcm.web folder.
Open the file and set the login mode to loginMode=NATIVE.

Optionally you can change the available memory.
Locate the file jvm.options in the C:\Program Files\IBM\cognos\ccr_64\fcmweb\wlp\etc\ folder.
This is part of that file;

# Java Heap size.
# In production, setting min and max to same value can provide the best performance by avoiding heap expansion and contraction.
# But high min value increases startup time, which may be undesired in a dev environment.

Create a Microsoft Windows service by running the file install_service.bat in the folder C:\Program Files\IBM\cognos\ccr_64\fcmweb\install_service.bat.
In the Windows Services console find IBM Cognos Controller Web and start the service.
Log in to Controller Web via your browser using the following url: http://[]:9080/fcm.web/login.

The Controller web server name must be in TRUSTED ZONE in internet explorer.
Go to the Control panel on your workstation – click on internet options.
Click on Security tab
Mark Trusted sites and click on Sites button.
Enter the name of your Controller web server and click add. You may need to untick the “require server verification for all sites in this zone”.

You must surf to

If you surf to you get a message like this

IBM WebSphere Application Server
Context Root Not Found

Close IE and try again with correct address.

If you surf to you get a message like this
Update Available. Click to download WebSphere Application Server Liberty Runtime

Do not update – close IE and try again with correct address.

If you change the Cognos controller databases, after the initial configuration of IBM Controller Web, then you need to stop the Controller Web Windows service, before you run SyncDBConf.bat again to collect the new database definitions.

To make Controller WEB work with CAM (Cognos Access Manager) :

You must configure IBM Cognos BI to not allow for anonymous authentication. You must also specify the Controller Web settings as below.

In the Cognos BI installation folder, /templates/ps/portal/, create a file with the name variables_CCRWeb.xml.
The content of the file variables_CCRWeb.xml must be as follows:

<CRNenv c_cmd=”http://controllerservername:9080/fcm.web/cam_login”>


<param name=”cam_passport”/>



Locate the file in the C:\Program Files\IBM\cognos\ccr_64\fcmweb\wlp\usr\servers\fcm.web folder.
Open the file and set the following properties:

biUrl: the URL that the user must go to when CAM authentication is needed. This property is only valid for CAM login mode.
biDispatchEndpoint: the endpoint to which Controller Web connects to validate CAM users and CAM passports. This property is only valid for CAM login mode.
loginMode: the authentication type. The accepted values are: CAM and NATIVE.

This is how it can be in the file;

# =====================================================================
# OCO Source Materials
# BI and PM: ccr
# (C) Copyright IBM Corp. 2004, 2009. All Rights Reserved
# The source code for this program is not published or
# otherwise divested of its trade secrets, irrespective of
# what has been deposited with the U.S. Copyright Office.
# =====================================================================

# See for current details

# global grace period before revalidating cache (milliseconds). Default: 6000 ms (if not defined)
# cache.validation.graceperiod=6000

# Examples:
# applicationID=fcm.web
# realtime=true
# jms=false


# @TOKEN@ elements below must be transformed during deployment to match actual installation.
# Login mode can be set to NATIVE or CAM.
# Examples:
biUrl= /ibmcognos/cgi-bin/cognosisapi.dll
# loginMode=NATIVE

# eof

More information:

Cognos Controller 10.3
Microsoft Windows 2012 R2 Server Standard
Microsoft SQL 2016 database server

How copy a controller database to test database?

Take a backup of your existing controller prod database in Microsoft SQL.
You can export the backup by use of Microsoft SQL Server Management Studio or from a command line on the SQL Express server with this command:

SqlCmd -U admin -P cognos123 -S .\SQLEXPRESS -Q “BACKUP DATABASE [ControllerLive] TO DISK=’C:\backup\ControllerLive.bak’ “

Above is if you use SQL login admin with password cognos123, and the database name to take backup of is named ControllerLive. Enter the command in Notepad++ and save as a ANSI cmd file – that you then run from an administrative command prompt on the SQL server.

SqlCmd -E -S .\SQLEXPRESS -Q “BACKUP DATABASE [ControllerLive] TO DISK=’C:\backup\databases\ControllerLive.bak’ “

Above is when you use Windows authentication and the logged in Windows user on the SQL server is executing the SQL backup. You need to update the path to reflect your environment.
This BAK file is then copied to the server where you have your test environment.

Best is to restore the BAK file with use of Microsoft SQL Server Management Studio. But if you know the logical name of the database you can use a script like this:
SqlCmd -E -S .\SQLEXPRESS -Q “RESTORE DATABASE [ControllerTEST] FROM DISK=’C:\backup\databases\ControllerLive.bak’ WITH RECOVERY, MOVE ‘ControllerLive’ TO ‘C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\DATA\ControllerTest.mdf’, MOVE ‘ControllerLive_Log’ TO ‘C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\DATA\ControllerTest.ldf’ “

You need to update the path to the correct ones for your environment.

After the Controller Database is restored you in most cases need to connect the SQL login with this SQL query that you run in Microsoft SQL Server Management Studio:
Sp_change_users_login ‘update_one’,’frango’,’frango’
Replace frango with the login name you use for your controller database.

Now the controller database is setup as ControllerTest, you need to go to the Cognos Controller server and add this database to Controller.
Inside IBM Cognos Controller Configuration mark the Database Connections tab and click on the NEW icon.
Enter database type to SQL Server.
Enter name to ControllerTest (or what you find most useful for the user to see)
Enter Provider to SQLNCLI11.1
Enter User ID to frango (or the SQL name to login to the database)
Enter Password to xxxxx (the password you have set on the SQL login)
Enter Initial catalog to ControllerTest (the name of the database in SQL)
Enter Data source to servername of the SQL server (and do not use FQDN)
Click on save.
Click on Check.
Click on Run, to start the DBCONV program.

Click on Connect to see version of the database.
If the Current version and upgrade to version number is not the same for Controller DB, then click on upgrade button.
Click on Close.

Go to Report Server and click on the green Check icon.
Then Controller will check if the new database exists in Cognos Connection.
If not, a REPAIR button will appear inside Cognos Controller Configuration.
Click on the REPAIR button (this will only work if the Windows user that is logged into the controller server is system admin inside Cognos Connection).
Report server connections have been created successfully.

Now you should restart the Windows server where Cognos controller are to ensure that the batch routine recognize the new database.

Then when this is done the super user of Cognos Controller should start their Controller client and login to see that the new database is working.

More information:

Cognos Controller 10.3 fix pack 1 =
(IBM Cognos Controller Version
Integration Version
Install/Updater Kit Version
Microsoft Windows 2012 R2 server
Microsoft SQL 2014 database

After upgrade to new version of Cognos Controller 10.3 when you go into the new IBM Cognos Controller Financial Analytics Publisher client (FAP) and click edit on a Source that have log level “detailed” you get a error message.

Other controller database “sources” that are listed work fine to be open by EDIT button in FAP client.

Error message:

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.


************** Exception Text **************

System.ArgumentOutOfRangeException: InvalidArgument=Value of ‘3’ is not valid for ‘SelectedIndex’.

Parameter name: SelectedIndex

at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)

at FAPClient.frmEditSource.frmEditSource_Load(Object sender, EventArgs e)

at System.Windows.Forms.Form.OnLoad(EventArgs e)

at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)

at System.Windows.Forms.Control.CreateControl()

at System.Windows.Forms.Control.WmShowWindow(Message& m)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.Form.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)



************** Loaded Assemblies **************


Assembly Version:

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll



Assembly Version:

Win32 Version:

CodeBase: file:///E:/Program%20Files/ibm/cognos/ccr_64/webcontent/ccr/FAPClient.exe



Assembly Version:

Win32 Version: 12.0.20806.33440 built by: FX45W81RTMREL

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll



Assembly Version:

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll



Assembly Version:

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll



Assembly Version:

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll



Assembly Version:

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll



Assembly Version:

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll



Assembly Version: 4.0.20153.110

Win32 Version: 4.0.20153.110

CodeBase: file:///E:/Program%20Files/ibm/cognos/ccr_64/webcontent/ccr/C1.Win.C1FlexGrid.4.DLL



Assembly Version:

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll



Assembly Version:

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll



Assembly Version:

Win32 Version: 4.0.30319.36372 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll



Assembly Version:

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll



Assembly Version:

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll



Assembly Version:

Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll



Assembly Version:

Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll



************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the section.

The application must also be compiled with debugging



For example:



< jitDebugging=”true” />



When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

Possible workaround:
Looks like the new version of FAP does not support detail logging.
In old version of Controller FAP this setting would show DEBUG log level. Please ensure you take a backup of the SQL database before you do any changes in it. If this does not work, you can restore the Controller FAP database.
So go into Microsoft SQL Server Management Studio.
Connect to the database server there you have your controllerfap database.
Select you ControllerFap database and on table dbo.NRTR_SOURCE right click and select Edit Top 200 Rows.
Far to the right you have column “LogLevel” – here there is a value of 40, change that to 30, for the source you get the error.
Exit out and check that your update is there with SQL command:

SELECT TOP 100 [Name]
FROM [ControllerFAP].[dbo].[NRTR_SOURCE]

Now go into your FAP client and on the source tab
mark the name of the data source who have detailed loglevel and click on Edit button.
You should now get into the edit dialog without errors.

The loglevel in “edit source..” show High, instead of Detail as listed.
You can update the server value.
The port number is missing do, so you may need to add it 1433.
Click on Test Connection to see that it works.
Click Save.

You have now updated the FAP to work with the new ControllerFAP database on the new SQL server.

Cognos Controller 10.3
Microsoft Windows 2012 R2 server

When starting the Cognos Controller client for the first time in a new installation, you get a error like this:
An error occurred while trying to access the server.
Details give:
The request failed with HTTP status 405: Method Not Allowed.
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 Cognos.Controller.ControllerSoapHttpClientProtocol.Invoke(String methodname, Object[] parameters)
at Cognos.Controller.Proxy.Light.WSLight.CheckServerConnection(String sGuid, String sUser)
at Cognos.Controller.Direct.ServerInfoD.CheckServerConnection()
at CCR.AppContext.CheckConnectionToServer()

If you start Internet explorer and surf to
you get a HTTP error 404

Ensure that on the Cognos Controller server you have installed windows roles for .NET extensibility 4.5 and ASP.NET 3.5 and ASP.NET 4.5 under Application Development for IIS server role.

This show some of what need to be in the Windows server to make Cognos Controller work:

More information:

Cognos Controller 10.3
Oracle 12c database
Microsoft Windows 2008 R2 Server

Standard Error generated when running Multi Period Locking report, and you have not selected a “Use Filter”.

Error message:
“Number: 5
Source: FrangoDirect.PerLockHandler.SelectMultiPerLocks#System.Web.Services
Description: System.Web.Services.Protocols.SoapException:
Server was unable to process request. —> System.InvalidCastException:
Conversion from type ‘DBNull’ to type ‘Date’ is not valid……..”

Possible Solution:
Set a Selected filter when using “Multi Period Locking” and run the report for a specific period.

This is different behavior since Controller version 10.1.1 where this did not give a error.

Other workaround is to enter a date in the column for date in the “Define Submission” dialog in Cognos Controller for all rows.

More Information: