Product:
Cognos Controller 10.3 fix pack 1 =
(IBM Cognos Controller Version 10.3.1.43
Integration Version 10.3.1.19
Install/Updater Kit Version 10.3.1.29)
Microsoft Windows 2012 R2 server
Microsoft SQL 2014 database
Problem:
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 **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.36366 built by: FX452RTMLDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
—————————————-
FAPClient
Assembly Version: 10.3.1.19
Win32 Version: 10.3.1.19
CodeBase: file:///E:/Program%20Files/ibm/cognos/ccr_64/webcontent/ccr/FAPClient.exe
—————————————-
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
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
—————————————-
System
Assembly Version: 4.0.0.0
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
—————————————-
System.Core
Assembly Version: 4.0.0.0
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
—————————————-
System.Windows.Forms
Assembly Version: 4.0.0.0
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
—————————————-
System.Drawing
Assembly Version: 4.0.0.0
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
—————————————-
System.Runtime.Remoting
Assembly Version: 4.0.0.0
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
—————————————-
C1.Win.C1FlexGrid.4
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
—————————————-
System.Xml
Assembly Version: 4.0.0.0
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
—————————————-
System.Configuration
Assembly Version: 4.0.0.0
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
—————————————-
System.Data
Assembly Version: 4.0.0.0
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
—————————————-
System.Numerics
Assembly Version: 4.0.0.0
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
—————————————-
System.Transactions
Assembly Version: 4.0.0.0
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
—————————————-
System.EnterpriseServices
Assembly Version: 4.0.0.0
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
—————————————-
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
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 system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging=”true” />
</configuration>
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]
,[Status]
,[Type]
,[UserName]
,[Password]
,[NRTRPurgeDate]
,[NRTRPurgeSecNum]
,[NRTRPurgeTextSecNum]
,[CCRMoveIndex]
,[CCRTextMoveIndex]
,[CCRDBUrl]
,[LogLevel]
,[Info]
,[Interval]
,[IntervalCounter]
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.