IBM Support

** Troubleshooting ** unable to log in to Controller due to error '--Exception has been thrown by the target of an invocation'

Troubleshooting


Problem

User launches Controller. User selects database. User enters username/password. User receives error message, and Controller closes.

Symptom

Screen message for all Scenarios:

--Exception has been thrown by the target of an invocation.
OK

Scenario #3
On the SQL server, there may be many occurrences of the following error:

    Event Type: Failure Audit
    Event Source: MSSQLSERVER
    Event Category: (4)
    Event ID: 18456
    Date: 14/02/2008
    Time: 15:47:11
    User: N/A
    Computer: WBRAMOSSMM5
    Description:
    Login failed for user 'fastnet'. [CLIENT: 192.168.1.3]
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 18 48 00 00 0e 00 00 00 .H......
    0008: 0c 00 00 00 57 00 42 00 ....W.B.
    0010: 52 00 41 00 4d 00 4f 00 R.A.M.O.
    0018: 53 00 53 00 4d 00 4d 00 S.S.M.M.
    0020: 35 00 00 00 07 00 00 00 5.......
    0028: 6d 00 61 00 73 00 74 00 m.a.s.t.
    0030: 65 00 72 00 00 00 e.r...

Cause

There are many different potential causes for the '--Exception has been thrown by the target of an invocation' error. This Technote shall only deal with the scenarios where the error is seen during the logon-to-Controller process.

In this case, the error is caused by a problem when reading/writing to the TEMPDB database. During logon, Controller will read/write to/from tables inside the temporary storage area of its database server. For example, if using Microsoft SQL, it will be reading/writing to/from the TEMPDB database.

There are several reasons why this process may fail:

  • Scenario #1 - Database Server is out of memory or storage space (e.g. temp storage space)
    • Often this is caused by the transaction log being full
  • Scenario #2 - The temporary database (e.g. TEMPDB) has a different collation from the database which holds the application data (the application repository database)
    • For more information, see separate IBM Technote #1345692
  • Scenario #3 - Security/network connection issue, causing SQL database logins to fail.
  • Scenario #4 - End user's Windows account has a problem (for example is locked out)
    • For more information, see separate IBM Technote #1347252
  • Scenario #5 - Invalid Oracle database due to missing stored procedures
    • For more information, see separate IBM Technote #1420562

Resolving The Problem

Scenario #1
## Microsoft SQL Server:

  • Ensure SQL server's hard drives are not full
  • Ensure that the Controller application repository database (e.g. 'ControllerLive') is set to 'unrestricted growth' for both its data (MDF) and log (LDF) files
  • Ensure that the TEMPDB database is set to 'unrestricted growth' for both its data (MDF) and log (LDF) files
  • If necessary, obtain a short period of downtime, and reboot the SQL server in order to free up RAM memory.
TIP: You may find that shrinking the LDF (log) files and/or moving the LDF files to new hard disk(s) helps.

## Oracle:
  • Ensure Oracle server's hard drives are not full
  • Ensure that the Controller application repository database's 'default' tablespace(s) are configured to grow automatically
  • Ensure that the Controller application repository database's TEMP tablespace(s) are configured to grow automatically
  • If necessary, obtain a short period of downtime, and reboot the Oracle server in order to free up RAM memory.
TIP: Check your error logs for entries such as 'ORA-04031'. This would suggest that the 'SGA private memory' has been exhausted. Fragmentation of shared pool memory is a common problem and ORA-04031 is commonly a result of such fragmentation. Application programmers usually get this error while attempting to load a big package or while executing a very large procedure and there is not sufficient contiguous free memory available in the shared pool. This may be due to fragmentation of the shared pool memory or insufficient memory in the shared pool. Possible remedies: Use the dbms_shared_pool package to pin large packages. Attempt to reduce the use of shared memory. Increase the initialisation parameter 'SHARED_POOL_SIZE'.

[{"Product":{"code":"SS9S6B","label":"IBM Cognos Controller"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Controller","Platform":[{"code":"PF033","label":"Windows"}],"Version":"8.5.1;8.5;8.4;8.3;8.2;8.1MR1;8.1","Edition":"Edition Independent","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Historical Number

1033964

Document Information

Modified date:
15 June 2018

UID

swg21347234

Page Feedback