IBM Support

"Could not create the view" when opening "Company - Command Center" caused by invalid financial structure (for example loop in Extended Dimension)



User clicks "Company - Command Center". User receives an error.


The error will vary depending on circumstances. Below are two real-life examples:

Example #1 (Controller 10.2.0)

    Could not create the view: Could not create controller of type com........

    Caused by: ...... Unable to find instance of model of type: userrights[UserRightsModel]
    Caused by: .....
    Caused by: ..... FAIL:!java.lang.StackOverflowError!

ccr.log (By default, this is located here: C:\Program Files\ibm\cognos\ccr_64\log)

    16:10:39,221 ERROR [cognos.ccr.integration.ServerIntegrationFacade] Failed when invoking method,
    at java.util.HashMap$KeySet.iterator(
    at java.util.HashSet.iterator(
    at java.util.AbstractCollection.toArray(
    at java.util.ArrayList.<init>(

Example #2 (Controller 10.2.1)
    Could not create the view: Model not found: userrights[UserRightsModel] Model not found: userrights[UserRightsModel]

ccr.log (By default, this is located here: C:\Program Files\IBM\cognos\ccr_64\log)
    08:28:35,830 INFO [cognos.ccr.integration.ServerIntegrationFacade] Executing inUserRightsModelDAO.load...
    08:28:35,830 INFO [cognos.ccr.integration.ServerIntegrationFacade] Model context setup for user USERNAME: 0 ms
    08:28:35,862 ERROR [cognos.ccr.integration.ServerIntegrationFacade] Failed when invoking method, Corrupted data in database: Extended dimension member 14 has a reference to itself
    08:28:35,862 INFO [cognos.ccr.integration.ServerIntegrationFacade] Finished inUserRightsModelDAO.load (135 bytes): 32 ms, memory usage [kb]: max=524 288 | total=166 784 | free=23 395 | total free=380 899


The message "Could not create the view" is generic - there are many possible causes for this.

  • TIP: See separate IBM Technote #1612000 for a list of possible causes.

This Technote specifically relates to the scenario where the cause is an incorrect/invalid financial structure (configuration).

Example #1:
In one real-life customer example, there was an invalid member of Extended Dimension 1.
  • Specifically, one of the Extended Dimension Members (‘XYZ’) had itself as parent (loop).

Example #2:
In one real-life customer example, when the customer ran 'Verify Structures' they found that for Dim1 there was an error.
  • Specifically, there was a non-connected dim-code (at level 0).

Diagnosing The Problem

Check both of the following for clues:

(a) Entries in the section 'Caused by' (in the on-screen error)

(b) Messages in the 'ccr.log' file (on the Controller application server)

  • TIP: By default, this is located here: C:\Program Files\IBM\cognos\ccr_64\log

(c) Run a 'Verify Structures' report, to see if there are any issues.

Resolving The Problem

Fix the incorrect/invalid financial structure (configuration).

Example #1:
In the real-life customer example (where the extended dimension member was looping due to being a parent of itself), the fix was to change the parent to 'total' (i.e. blank) and set level to 1.

  • Alternatively, a different method to fix could be to simply delete the 'bad' member ‘XYZ’ (because perhaps that member was added by mistake). However if there is data referring to this member it may be better to keep it.

Afterwards, it may be necessary for the end user to clear the cache ("Maintain - Special Utilities - Clear local cache"), then close the Controller client and re-launch Controller.

Example #2:
In this real-life customer example, the solution was to:
  • Removing non-connected dim-code from xkod and xkodt
  • Run a Database Optimise.

[{"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":"10.2.1;10.2.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 June 2018